Native or cross-platform
We will recommend one, with reasons, rather than defaulting to whichever we prefer building.
Cross-platform (React Native or Flutter) makes sense for most business applications. One codebase, both stores, meaningfully lower cost to build and maintain.
Native earns its extra cost when the app leans on the device: heavy camera or sensor use, background processing, tight platform integration, or when animation smoothness is the product.
What we own
Architecture, interface design, the build itself, store submission and the review process, and the release cadence afterwards. App Store review rejections are routine and we handle them; you should not be reading Apple's guidelines.
Offline is not an edge case
Phones lose signal in lifts, basements and on trains. We decide early what the app does with no connection (queue writes, serve cached reads, or block with a clear message) rather than discovering the answer through crash reports.
After launch
Releases every two to four weeks, crash reporting wired up before the first public build, and a rollback path that does not require an emergency store review. Both platforms ship OS updates annually that break things; staying current is maintenance, not a new project.
Where this connects
Apps almost always need a back end and an admin surface, and that is web application development.