LivePocket Music
Chord loop, metronome, tuner and chord tools, offline in your pocket.
Google Play →flamedots · app studio for startups
Light the first version. Then keep it burning.
We design and build the first real version of your app: a small team, short loops, and a release in the App Store and Google Play. Then we stay with it, through the fixes, the updates and the next version.
2apps live in the stores
2more on the way
1design system behind every app
0accounts needed to use them
Work
Apps we built and run
Our own products come first: every client project starts from what we learned shipping these.
Live
LiveSideman
A backing band in your pocket: a groove to practise and jam over.
Google Play →
ComingShedlog
A practice journal that keeps score for you.
In the works
ComingChordCam
Film your cover with the lyrics and chords scrolling on screen, then share a video with them on it.
In the worksThe mark
Twelve cells burn. None go out.
Our mark is a grid of twenty cells. Twelve are lit and make a flame; the other eight stay faintly on, like embers. No cell ever goes fully dark.
That is the studio: a steady flame, not a flare. We light the first version, and we keep it burning through the bad reviews, the store rejections and the long weeks when nobody is watching yet.
What we build
One first version, done properly
Not a prototype that has to be thrown away. The code, the design and the store listing are the ones you keep.
01
The app
iOS and Android from one Flutter codebase, offline-first, fast to open, accessible from the start.
02
The design
Screens, icons and a small design system of tokens, so the next screen looks like the last one.
03
The launch
Store pages, screenshots, the review process and the first release in both stores.
04
The handover
Clean architecture, tests and docs, so your team, or ours, can keep building.
How we work
Short loops, something to hold every week
Shape
Find the one job
What must the first version do, for whom, and what can wait. One page, agreed before any screen.
Design
Screens you can tap
Clickable designs on your phone, tested with the people who will use them.
Build
A build every week
A working app on your phone each week. You steer from what you hold, not from a report.
Ship
Into the stores
Release, watch it in use, fix what people trip on, and plan the next version.
Studio
What keeps us burning
A small studio, with AI in the toolbox and a person deciding every detail.
Careful by hand and by machine
AI makes the work fast; a person decides every detail, and nothing ships that needs a manual to use.
Private by default
No account unless it is needed, works offline, usage data optional and kept off the advertising path.
Honest about AI
We say when AI helped build something, and we do not dress it up as a feature.
Small and shipped
One thing that works beats ten that almost do. The first version is the one people can use.
We don't walk away
A launch is where the work starts. We watch the app in use, fix what people trip on and plan the next version with you.
FAQ
Questions founders ask first
Who owns the app when it is done?
You do: the code, the designs and the store listings. It is your app in your developer accounts, built so that your own team, or ours, can keep working on it.
Why Flutter?
One codebase gives you an iOS and an Android app that look and behave the same, at the cost of building one. Our own apps are built the same way, so you get what we already run in the stores.
What do I see while it is being built?
A working build on your phone every week. You steer from what you can tap, not from a status report, and the plan for the next week comes out of what you saw in this one.
Do you use AI?
Yes, to work faster. A person decides every detail and reviews everything that ships, and we say where AI helped rather than selling it as a feature.
What happens after the first release?
We watch it in use, fix what people trip on and plan the next version with you. The code comes with tests and docs, so the next version does not depend on us.
Blog
Notes from the studio
How we design, build and ship, written from the apps we run ourselves.
-
A gate for Flutter architecture: keeping a codebase clean after handover
Clean architecture rules written in a document fade. We check them on every commit with a short Dart script that reads every import, so they outlast the people who wrote them.
-
Offline first, no account: what that means in Pocket Music
Why our music app opens straight into its tools, works in airplane mode and never asks you to sign up, and what still needs a connection.
-
Moving a live app onto a shared design system without changing a pixel
How we pulled Pocket Music's theme and generic widgets into one Flutter package for all our apps, and the screenshot diff that caught what 3,427 tests missed.
Have a first version to light?
Tell us what it should do. We light it, then keep it burning. We reply within two working days.