Mobile apps for Android and the web
Native apps for Android and iOS, or installable web apps from the same codebase as your site.
What you get
- An app you can install on a real phone, not only screenshots.
- Offline behaviour that is decided on purpose, not by accident.
- The source code, build instructions and a signed build when you are ready for the store.
Who it is for
- Teams that need an Android app for their users.
- Businesses whose customers mostly use a phone and may not want to install from a store.
- Founders testing an idea with a small, working version first.
How it works
- Choose the formatA native app for Android and iOS, or an installable web app. The choice depends on what the app needs from the device, and who installs it and how.
- Design the core screensThe main flow first, on a small screen, so thumb reach and text size are right early.
- Build and test on devicesYou install each build on your own phone and tell me what feels wrong.
- Prepare for releaseStore listing material, privacy text and a signed build, or a PWA deploy with an install prompt.
A small first step
A one-screen prototype on your phone, so you see the real thing before agreeing the full scope.
Related work
Questions
Native app or installable web app?
Native when you need device features or a store presence. An installable web app when reach and speed to market matter more. MR Works will say which fits your case.
Do you build for iOS?
Yes. The MERIDIAN app is one codebase for Android and iOS. Publishing to the App Store needs your own Apple developer account.
Can you publish to Google Play for me?
I can prepare the build and the listing. The Play account stays yours.
Does the app need a backend?
Only if data must be shared between users or devices. A game that keeps its score on the phone needs none; a store or a booking app does.
Can you add features to an existing app?
Yes, after a short look at the code. See the rescue service.