Three Products. One Consistent Experience.

Mobile parity, privacy-first account management, and six QA improvements

Prepared by Hassan  •  Weekly Technical Blog

Executive overview

This week, my work moved across three products with a shared engineering objective: making everyday workflows more reliable and consistent. In IQ POS, I brought changes from the web application into the React Native mobile experience. In Cold Calling Agent, I worked on privacy-policy acceptance during registration and account-management functionality across web and mobile. In HireRosterly, I addressed six QA-reported usability and functional issues affecting profile editing, attendance, leave requests, navigation, and account security.

01  |  IQ POS — translating web updates into mobile

I reviewed the latest web-side changes and implemented their corresponding behavior in the React Native mobile application. The focus was not to reproduce desktop screens pixel for pixel, but to carry the same product expectations into a smaller, touch-first interface. This involved checking navigation, forms, screen organization, and feature behavior against the web reference.

The central challenge was cross-platform parity: a feature can exist on both platforms yet feel inconsistent if its entry point, validation, or interaction differs. I therefore treated the web application as the functional reference while adapting the presentation to mobile constraints. This creates a clearer foundation for future updates and reduces the risk of the two interfaces drifting apart.

02  |  Cold Calling Agent — privacy and account control

Privacy-policy acknowledgement at signup

I added the privacy-policy experience to the registration journey so users can review the policy and explicitly acknowledge it before creating an account. The work included presenting a clear policy link and connecting consent to the registration flow. This makes an important account requirement visible at the moment the user signs up, rather than hiding it in settings after registration.

Account functionality across web and mobile

I also worked on account-management capabilities in both interfaces, including the account-deletion and recovery-oriented flow. The implementation emphasizes clear confirmation, appropriate authentication checks, and consistent account-state handling. A deletion request should not be confused with an immediate, irreversible loss of data; the product flow includes a recovery period and verification through support. Web and mobile should communicate these rules consistently.

A related engineering consideration was backend parity. Mobile and web must target the intended backend and authenticated workspace to show the same account state. An older deployed API or a different environment can produce inconsistent results even when the screens are implemented correctly. This remains an important end-to-end verification concern.

03  |  HireRosterly — six QA issues addressed

01  Date of birth input

Improved date-entry guidance with a calendar-picker or clearly defined date-format experience so users can enter dates consistently.

02  Save Profile placement

Clarified the Save Profile action by positioning it in the context of the complete profile rather than making it appear limited to Emergency Contact.

03  Attendance location validation

Investigated the incorrect out-of-radius response for users at approved office coordinates, focusing on location permissions, latitude/longitude ordering, distance calculation, and radius handling.

04  Past-date leave requests

Addressed validation that allowed leave requests for dates already passed, with attention to both client-side feedback and backend enforcement.

05  Back-navigation consistency

Standardized back-navigation behavior across secondary and detail pages, while keeping primary navigation free of unnecessary back controls.

06  Authenticated password change

Added or improved access to password-change functionality from the signed-in account/profile experience, with appropriate security and validation considerations.

04  |  Challenges and practical decisions

The three projects raised different kinds of problems. IQ POS required careful interpretation of web changes for React Native rather than direct UI copying. Cold Calling Agent required consistent privacy and account behavior across separate clients and backend environments. HireRosterly mixed visual usability defects with higher-risk functional issues: GPS-based attendance, historical leave dates, and password management all require stronger validation than a purely cosmetic adjustment.

The QA list provided the expected and actual behaviors, which helped turn broad bug reports into specific acceptance criteria. The distinction between implementing a fix and verifying it in the real authenticated environment remains important; build checks alone do not establish that GPS, security, or cross-device behavior is correct.

05  |  Outcomes and lessons learned

This week reinforced three lessons. First, cross-platform consistency means matching behavior and intent, not simply matching screen layouts. Second, privacy and account settings should be designed as core user journeys with explicit consent and clear recovery rules. Third, QA work is most effective when the expected behavior is translated into testable scenarios, including boundary conditions such as past dates and location-radius limits.

06  |  Next steps

• Verify IQ POS mobile screens and user journeys against the latest web version on multiple screen sizes.
• Run authenticated end-to-end checks for Cold Calling Agent signup consent, account deletion/recovery, and web/mobile backend consistency.
• Retest all six HireRosterly fixes, prioritizing real-device attendance GPS, past-date rejection, and password-change security.
• Record regression results and resolve any remaining edge cases before release.

Closing reflection

The week was defined by practical product quality: bringing web improvements to mobile, making account control more transparent, and removing friction from six core HR workflows. The next milestone is rigorous scenario-based verification so that the implemented changes remain dependable in real use.