Mobile app studio
Your next app release, shipped
Someday is now. AI Agents for the release: the Product owner clarifies it, the Coder writes the iPhone and Android code, and Marketing drafts the launch note. You give the final go.
Small screen. Big idea.
An app interface taking shape
- The app and the release
- The bugs and features that repeat
- Where you give the final go
Nothing is sent or shipped unless you asked for it or approved it, and money always asks.
Slack and Telegram keep you in the thread. GitHub holds the pull request, and a merge waits for you.
A closer look
An idea goes in.
Real work comes out.
An app interface taking shape. Explore how the pieces fit.
Illustrated workflow
02 / The team works
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
How it works
From a goal to a result.
- 01
Set a goal
You say what done looks like: a ticket, a client, a deadline, or a draft.
- 02
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
- 03
You approve the risky step
Anything that sends, publishes, ships, or charges waits for your Approve. Approve a kind of step once and that assistant remembers it, but money always asks.
- 04
You get the result
A pull request with the tests, and a launch note, both ready for your final go.
Example
Send the new build notes to your testers
It sends to people, so it asks first.
The team
You, and the assistants.
You
You set the release goal and approve the launch note and the ship.
Coder
Writes the code for your iPhone and Android app with you, writes the tests, and opens the pull request on its own. Nothing merges until you approve it.
Product owner
Clarifies the requirement, writes the issue, and ranks it against the release.
Marketing
Drafts the launch post and the store note. Sending or publishing them waits for your Approve.
Integrations
The tools it starts with.
- GitHub
- Slack
- Linear
- Notion
- Telegram
Built in
What your assistants can use.
Its own computer
Each assistant works on its own computer in StellarFirm cloud, set up with the tools its job needs, and hands you the files.
Roles you make yourself
Name a role we don't ship, say what it does and give it any of our skills or your own. Comes with Ultra and enterprise.
A running app beside the chat
The Coder starts the app it built and shows it live next to the chat, so you can click through it yourself.
Build iPhone and Android apps
The Coder builds iPhone and Android apps with React Native and Expo, on your own Expo account. Each build and each store release waits for your Approve.
Keep going until it is done
Say what done looks like and the Coder keeps going, up to ten more rounds, until the goal is met. /stop ends it.
Long jobs in the background
A big job starts at once and runs in pieces in the background, streaming back as it goes. You can stop it any time, and sends and spending still ask.
Follows up on its pull requests
Switch it on for a Coder and it takes on failing checks, merge conflicts and review comments on its own pull requests. Merges and replies still ask you.
Put the app it built online
When the Coder has built an app, it can put it online at an address like your-name.stellarfirm.app once you approve. You can take it offline again any time.
Ready to use
Prompts and skills.
Skills
- Implement a change
- Write tests
- Clarify requirements
- Draft a launch post or waitlist email
- Draft an issue
Ready prompts
Clarify this release note into issues the Coder can pick up.
Add a settings screen to the app, write its tests, and open the pull request.
Draft the launch post for this release and hold it for my Approve.
Questions
Before you join.
Start with your first assistant.
Leave your email. Invites go out every day until 27 October, and we'll write when your spot is ready.