Starstell.
A consumer product is judged in the first thirty seconds, on a phone, on a bad connection.
- Client
- Starstell
- Sector
- Consumer web & app
- Scope
- App + web
- Stack
- Next.js, React Native, Node.js
A consumer-facing app and website sharing one content and account layer, so a change lands in both without a second build.
What made it hard.
The first version usually contains three products. Deciding which one ships is most of the value.
Content ownership
If routine changes need a developer, the site stops being updated within a quarter.
Performance
Consumer patience is measured in hundreds of milliseconds on a mid-range phone.
Handover
Whoever maintains it next inherits these decisions and should be able to live with them.
What we shipped.
A consumer-facing app and website sharing one content and account layer, so a change lands in both without a second build.
How it holds up.
Performance and accessibility budgets are set at the start and enforced in CI, because both are cheap to hold and expensive to retrofit.
The systemOne API serves app and web, with content modelled so non-technical staff can change it without a release.
Theirs, from day one.
Repositories, cloud accounts and documentation sat with the client throughout. Senior engineers wrote the production code rather than specifying it.
Ask for the full metrics on a call →More consumer web & app work.
All 42 case studies →Building something like Starstell?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.