Whatnxt · product studio near Aylesbury
So, what happens next?
YouWe think our customers need an app. Or maybe a better website. We are not entirely sure.
WhatnxtThat is a normal place to start. Tell us who is waiting for it, and what they do today instead.
YouAnd then you build it?
WhatnxtThen we test the riskiest guess, design what survives, build it, publish it and look after it.
Questions people bring us, answered properly
Whatnxt helps founders and small teams who know something needs building but are unsure what, how or in which order. These are the questions we hear most, with what we actually do about each one.
Do I need an app?
Sometimes. We will tell you honestly.
Apps earn their place when people use them often, need the camera, location or Bluetooth, or must work without a signal. When that is true we build iOS and Android apps, usually with one cross-platform codebase, or natively in Swift and Kotlin when the hardware demands it.
Mobile development in detailOr is it a website?
Often, and a good one is hard to beat.
A website reaches anyone with a browser, needs no installation and updates instantly. We build focused company sites, content platforms with editors and search, and web applications with logins, data and integrations. A responsive web version is also a cheap way to prove demand before committing to the app stores.
Web development in detailHow will it feel to use?
Like it was obvious, which takes work.
We interview the people you are building for, map what they are trying to do, sketch options and test clickable prototypes with a handful of participants. What confuses them changes; what we merely dislike does not. Contrast, focus states, labels and text resizing are designed in from the start.
UI/UX design in detailHow do we get it out there?
Carefully, with a checklist and some slack.
We help you register Apple and Google developer accounts in your organisation's name, write clear store listings, complete privacy declarations from an honest inventory of what the app collects, and answer reviewers. For websites: domain records, certificates, redirects, live form tests and a backup before the switch.
Publishing assistance in detailWhat if it breaks?
Then we fix it, and find out why.
Live software needs regular care: operating-system updates, dependency patches and the occasional surprise. Choose ongoing maintenance, maintenance plus regular improvement time, or work quoted when something comes up.
Support and fault reportsNot sure which question is yours?
Answer three quick ones. You will get our honest guess at a sensible first step, and a page to read next. Nothing leaves your browser.
The path-finder is deliberately blunt. Real projects have more nuance, which is what the first conversation is for, but most people find the three answers clarify their own thinking surprisingly fast.
If you accept optional storage, your answers are remembered on this device.
The first fortnight, as it usually goes
People often ask what working with us is like before any code exists. This is a typical start; your own will be shaped to fit.
- First call
We listen, then ask awkward things
Who is this for? What do they do now? What would make it worthwhile? You leave with notes, not a sales pitch.
- Later that week
Your assumptions, written down
We list everything the idea depends on and sort each item as known, a hunch, or unknown. Try it yourself below.
- Early in week two
The riskiest guess gets tested
A handful of interviews, a paper sketch or a clickable prototype: the cheapest test that could prove us wrong.
- End of week two
A plan you could take elsewhere
What to build first, what to leave out, how we would test it, and an estimate. It is yours whether or not we build it.
Sort your own unknowns?
Write down what you believe about your idea, then be honest about each one. Is it known, a hunch, or genuinely unknown? Everything that is not known is something to test, starting with whichever would hurt most if it turned out to be wrong.
Kept on this device only if you accept optional storage.
Known
We have evidenceHunch
Probably, but untestedUnknown
Genuinely no ideaWhat you hold at the end
Whether we work together for a fortnight or for years, you should be able to carry on without us. Everything is created in your name from the start.
Our delivery standards- Code in a repository you own
- Developer and hosting accounts in your name
- Designs and the component library
- Research notes and decisions, with reasons
- A list of every third-party service used
- A short maintenance and release guide
- Accessibility results and known gaps
- Any outstanding risks, written plainly
Worth reading before you start
Research with the people you are building forGOV.UK’s guide to user research is plain, free and useful far beyond government.
Read itKnow the App Store rules earlyApple’s review guidelines explain what an iOS app may and may not do. Better read before design than after rejection.
Read itData protection for small organisationsThe ICO explains your obligations without the jargon.
Read itSmaller questions
Do you only work with start-ups?
No. Most of our clients are at an uncertain stage, but that includes established organisations testing something new.
Can you give a price before we talk?
Not a meaningful one. After a first conversation we suggest either a short discovery or, if things are already clear, an estimate for the build.
What if the answer is “don't build it”?
Then we say so. Stopping early is a good outcome if it saves you building the wrong thing.
Can we meet in person?
Our address near Aylesbury is a correspondence address, so meetings are arranged in advance. Most work happens through calls and shared notes.
When do you reply?
Monday to Friday, 09:00–18:00 UK time.