Native Android apps
Native Android apps in Java on the platform API, without heavy libraries. Our own Android apps work offline and ask for no permissions at all.
PN Scripts · Mobile app development
Android apps & games.
We design and build Android apps and the API behind them: native Java apps and mobile web apps that also run on an iPhone. The code, the store accounts and the documentation are in your name from day one.
The standard
Built for real phones and patchy networks
We design for mid-range phones and unreliable connections: screens open quickly, navigation is obvious, and sign-in stays secure. PN Scripts can also build the API behind the app, so both change together.
- Screens that follow the Android conventions your users already know, with large touch targets and light and dark themes.
- An API that returns clear errors and loads long lists in pages, so the app stays fast.
- A release checklist, updated whenever Google Play changes its policies.
- An admin panel for your staff, with roles and permissions, when the app needs one.
- One company is responsible for the app, the API and the store releases, so there is no dispute between suppliers when something breaks.
What we build
What mobile app development includes
From the first prototype to the maintenance release after the next OS update.
APIs built for mobile
Versioned APIs that page long lists, return errors the app can show, and keep older app versions working. Built by the same company in Laravel or the stack you already run.
Store releases
Signed app bundles, store listings, Data safety and content rating answers for Google Play under your own developer account, with a release checklist kept current as store policies change.
Push, deep links, analytics
Push notifications, deep links and analytics events limited to what you approve, and documented for the store privacy forms.
Speed on real devices
Fast start-up, clear navigation, logins kept in secure storage, and offline mode where the product needs it.
Maintenance releases
We track Android and Google Play policy changes, including the yearly target API level, and plan maintenance releases so the app and its API stay compatible.
Release process
How an app version reaches the stores
The path every build takes before it reaches a home screen.
-
01 · Critical flows
Prototype
We prototype the flows that carry the product first and hold back nice-to-have screens.
-
02 · API
Contract
Pagination, error formats and API versions are agreed with the server side before any screen depends on them.
-
03 · Android builds
Build
Signed Android builds from a repeatable build script, with the signing keys and the pipeline in your own accounts.
-
04 · Real devices
Test
Unit and screen tests on every build, then the Android emulator and real mid-range phones on mobile networks.
-
05 · Store submission
Review
Store descriptions, Data safety answers and replies to Google Play reviewers.
-
06 · Regular releases
Maintain
Crash reports and planned maintenance releases after launch, for as long as you want.
How we work
From prototype to store listing
-
A first version scoped for store review
We prototype the critical flows early and hold back nice-to-have screens until the core of the app has proven itself with users.
-
An API the app can rely on
Clear errors, safe retries and monitoring, so a problem in production can be traced from day one. Automated tests cover logins, payments and data.
-
Published in your name
The developer accounts, store listings, signing certificates and build pipelines are yours from day one, and every release step is documented.
Ways to work
Three ways to build your app
Android first, with a mobile web version when it suits the product. Each option is planned around store review, unreliable connections and an API the app can depend on.
-
MVP
Test the core idea with users
Pricing model Fixed sprint
- Scope
- The core feature only
- Platforms
- Android
- Release
- Internal test builds
- Support
- Handover documentation
-
Recommended
Product
Launch on Google Play
Pricing model Milestones
- Scope
- Store-ready app
- Growth features
- Push and analytics
- Release
- Google Play
- Support
- Crash reports, planned releases
-
Scale
Ongoing development
Pricing model Monthly
- Scope
- Several app variants
- Growth features
- Feature switches and A/B tests
- Release
- Regular store releases
- Support
- Agreed response times, policy watch
| Need a prototype first? Ask about a short discovery sprint. | MVP | Product | Scale |
|---|---|---|---|
| Android app with tests on every build | Included | Included | Included |
| Push notifications, deep links, analytics events | Not included | Included | Included |
| Google Play submission and store listing | Not included | Included | Included |
| Offline mode where the product needs it | Not included | Included | Included |
| Crash reporting and planned releases | Included | Included | Included |
| Several versions of the app, including white-label | Not included | Not included | Included |
| Remote feature switches and A/B tests | Not included | Not included | Included |
| Agreed response times and store policy monitoring | Not included | Not included | Included |
Technology
Mobile app technology we use
Chosen because developers for them are easy to find and the code stays maintainable for years.
- Java and the Android SDK Native Android apps without heavy libraries
- HTML5 and PWA Mobile web apps that also run on an iPhone
- Laravel APIs, logins, roles and admin panels
- Push and deep links Bringing people back to the right screen
- Crash reporting Release health after launch
- Android emulator Every build tested before real phones
Questions
Mobile app development questions
What clients ask before they commit to building an app.
What happens after the app is live?
We keep maintaining it for as long as you want. Google changes the Play policies and Android versions every year, so we track those changes, plan maintenance releases around them, and update the app and its API together. You get scheduled updates instead of emergency fixes.
Do you build iPhone apps?
Our work you can check is on Android: native Java apps. For iPhone users we can build a mobile web app that runs in Safari and can be added to the home screen. If your product needs a native iOS app from day one, we say so in the first call and help you plan it, rather than promise work we have not shown.
Can you publish under our developer accounts?
Yes, and we recommend it. The Google Play developer account, the signing keys and the store listing stay in your name from day one. We prepare the builds, the store metadata and the answers to review questions.
Do you build the API too?
Yes, and it usually saves time. When the same engineers build the app and the API, logins, payments and admin tools fit together sooner, and you have one contact when something breaks. We can also connect the app to an API you already run.
How do you handle analytics and privacy?
We track only the events you approve and document what the app collects and why. That document answers the Google Play Data safety form.
How is an app priced?
You get a written scope and estimate before anything is agreed, and work begins only after you say yes. An MVP is usually a short sprint on a fixed scope, a store-ready app is billed in milestones, and ongoing work runs monthly.
Start
Tell us what your app has to do first. We reply within one business day.
Ready to plan your app?
Google updates Android and the Google Play rules every year. We plan maintenance releases around those changes, so updates do not catch your users out.
Describe your app