Androidapplications.
Android holds the largest share of the market across most of the world. An app makes sense when users come back often and when you need something a browser cannot do - notifications, the camera, working offline.
What you get
What the build covers.
One question comes before everything else: do you need an app at all, or will a fast website do. We answer that honestly, and often the answer is the website.
Development
Native or cross-platform, depending on what the app actually does.
- The approach chosen to fit the requirements
- Design to the Android guidelines
- Offline use where that makes sense
- Notifications people do not switch off after two days
- Connected to your own systems
Getting into the store
Google Play has rules that reject apps over small details. We walk through that with you.
- Setting up the account and the paperwork
- The privacy policy and the permissions
- Description, screenshots and video for the listing
- The submission process and answering review notes
- Updates and new releases
Visibility in the store
Search inside Google Play works by its own rules and brings a large share of the downloads.
- The title and the keywords in the listing
- Screenshots that explain the value
- Ratings and replies to reviews
- Rank tracking inside the store
- Tied in with the website
After release
Android changes its rules and its versions. An app nobody updates stops working within a year or two.
- Error and crash monitoring
- Updates for new versions of the system
- Tracking usage and drop-off
- A plan for further development
- Handing over the code and the access
How it runs
How it runs.
-
Phase 1
Is it needed
An honest comparison between an app and a fast website. Some clients stop here, and that is a good thing.
-
Phase 2
The smallest version
The part without which the app is pointless, in the store within a few months.
-
Phase 3
Growth out of use
What gets added is whatever the data shows is missing.
-
After
Upkeep
Updates, crash monitoring and new releases.
Who this is for
Who it works for, and who it does not.
It makes sense if:
- Your users come back often, not once a year
- You need notifications, the camera, location or offline use
- You have a budget for maintenance too, not just for the build
It does not make sense if:
- The app would do the same as the website - then the website is cheaper and more visible
- You have no plan for getting people to download it
The biggest cost of an app is not building it, it is nobody downloading it. We make the plan for downloads before the first line of code is written.
Frequently asked questions