Mobile apps

In brief, then in detail

• Flutter for both stores. One UI, one domain logic, and platform channels where the device must be reached directly. Shared code is a choice, not a religion.
• iOS. Swift and the Apple frameworks when the product depends on them. Signing, TestFlight, review guidelines, and a build the store will accept.
• Android. Kotlin, current API levels, and the device variety the audience actually owns. Play Console release tracks, not a file emailed to a tester.
• The hard problems. Offline use, push, payments, biometrics, and the crash that only happens on one OS version. Senior engineers with more than ten years take those, and they explain the constraint instead of promising that every device bug vanishes overnight.

How it is run

The app sits on the same Scrum cadence as the rest of the product. A CSM-certified analyst writes the journeys and the acceptance criteria, including offline and permission states. A PMP-certified project manager keeps the store dates and the review risk visible. ISTQB-certified testers cover the journeys on real device classes, not only on a simulator.

IncogX staffs engagements with PMP-certified project managers, business analysts who hold the Certified ScrumMaster credential, and ISTQB-certified testers. PMP is issued by PMI, CSM by Scrum Alliance, and ISTQB by the International Software Testing Qualifications Board. Certificate numbers are not published. Senior engineers on these teams have more than ten years in production systems.