Mobile apps
iOS and Android apps, usually from one cross-platform codebase, native when the hardware demands it. Test builds land on your phone every fortnight. Mobile in detail
Software design, build and launch. Reading, England
Software with somewhere to be.
Raketa Dynamics designs, builds and launches mobile apps and websites, then keeps them flying. We move quickly because we plan properly first, and we write the plan down where you can see it.
- Crew window
- Mon to Fri, 09:00 to 18:00 UK time
- Builds
- iOS, Android, web
- Base
- Lower Earley, Reading
- Shortcut
- Press / to jump anywhere
What lands on your desk in week one
Every Raketa project starts with a launch brief: a short written document we build together in the first week. It is the single most useful thing we make, because everything after it is measured against it.
- MissionOne paragraph: who this is for and what changes for them when it ships.
- Out of scopeThe features we have agreed not to build yet, written down so they do not creep back in.
- OwnersWho decides what, on your side and ours, and how quickly decisions are needed.
- RisksThe few things most likely to go wrong, and how we will test them first.
- Definition of doneWhat must be true on launch day, including accessibility, performance and store approval.
Four engines. One launch.
Web builds
Marketing sites, web apps and portals with clean deploy pipelines, a staging copy you can explore, and pages that stay light on mobile data. Web in detail
Interface design
Flows and screens tested with real people before code, so the build goes straight instead of in circles. UI/UX in detail
Publishing
Store listings, privacy answers, review handling and release routines that do not wobble on launch day. Publishing in detail
Timeline estimator
Set the shape of your project and see a rough planning range for each phase. Real plans come after a conversation; this is for budgeting your own thinking.
Ranges assume prompt decisions and feedback within a few working days. They are not a quote or a commitment.
Platform picker
Not sure whether you need an app at all? Three quick questions. We suggest a starting point and explain why. A suggestion, not a quote.
Waiting for answers
Answer all three to see a suggested platform.
How a Raketa launch runs
- CountdownA focused discovery: goals, users, constraints, risks. Ends with the written launch brief and a plan you can hold us to.
- IgnitionPrototypes and design in short loops. You see something clickable early, and real users try it before we build.
- AscentBuild in fortnightly increments with test builds on real devices and a live staging site. A written note every Friday.
- OrbitPublishing, monitoring and a calm first month of support, then a maintenance rhythm that suits you.
After launch, nobody vanishes.
The first month after release is when real users find the edges. We stay on watch, then agree a rhythm that fits how much the product changes.
| Rhythm | What happens | Good for |
|---|---|---|
| First month | Crash and error watching, quick fixes, a short report at the end | Every launch |
| Monthly care | Updates for new OS versions, dependency upgrades, security patches, checks | Products that change slowly |
| Retained crew | Care plus an agreed block of build time each month | Products with a roadmap |
| On request | No plan; each job quoted before work starts | Stable, simple sites |
From the kit
Three things worth checking before any launch, whoever builds it. More in the kit.
Who owns the accounts?
Apple, Google, domain, hosting. Each should be in your organisation's name with at least two people able to sign in.
Can you roll back?
Know how to return to yesterday's version in minutes. Staged rollouts on Google Play and phased releases on the App Store help.
Have you tested on an old phone?
Many people keep a phone for years. Borrow one, turn up the text size, and use the product on mobile data.
Questions before take-off
How fast can you start?
Usually within a few weeks of a first call. We tell you honestly if our schedule cannot fit your dates.
Do you work outside Reading?
Yes. We are based in Lower Earley and work with teams across the UK, mostly by video call, meeting in person when it helps.
Can you rescue a project that has stalled?
Often. We start with a short paid review of the code, accounts and backlog, and tell you plainly what it would take.
What does it cost?
After the first conversation we give a range; after the countdown week we give a fixed price for the next phase. You are never committed further than the phase you have agreed.
Fast is a planning decision.
Projects drift when decisions are left open. We write down scope, owners and what "done" means before anyone opens an editor, then we protect that plan. Speed comes from fewer surprises, not from long nights.