Apps for iPhone and Android that feel right

With React Native we write the app once and ship it to both iPhone and Android. The saving is not only in the build - it is mostly afterwards: a new feature or a bug fix lands in both apps at once instead of being developed twice and tested twice.

Where a platform has its own rules, we follow them. Navigation, back behaviour, permission dialogs and sharing look like iPhone on iPhone and like Android on Android. And when a feature genuinely needs native code - Bluetooth, background processing, a specific SDK - we write that piece in Swift or Kotlin alongside.

Push notifications, camera and photo upload, location, Face ID or fingerprint, calendar, in-app payment, NFC, offline use: these are the reasons an app is worth building at all. We work out early which of them you actually need - the rest only adds cost and review time in the store.

Offline is the part that gets underestimated most often. For the trade and industrial businesses around Schaffhausen, that is often the real reason for having an app at all: someone who spends the day on installations, in a warehouse or out on the road cannot wait for a website to load. We build the app so it keeps working on the train, in a basement or on a building site, stores input locally and syncs once there is a connection again. That needs proper conflict handling, and we plan for it rather than bolting it on later.

Submission is a craft of its own. We handle bundle IDs, signing and certificates, app icons in every size, screenshots, store copy, age ratings and the privacy declarations Apple and Google now require for every app. The developer accounts are set up in your name so the app belongs to you - we walk through it with you.

Before launch you get a test build through TestFlight or the internal testing track on Google Play, so you and your team can try the app on your own devices. Apple review usually takes only a few days, though neither store commits to a turnaround. Rejections happen, and we fix the points raised until the app is through.

iOS and Android get a new major version every year, and both stores periodically require apps to be built against newer SDKs. An app left untouched for two years eventually gets pulled or breaks on new devices. We keep your app maintained, update dependencies and test against each new OS release.

Visibility is part of that: crash reports and simple usage numbers show you where people get stuck. Smaller changes to copy and logic can often be shipped straight to devices with React Native without a fresh store review - larger changes take the normal route.