Create a New App
Create an app that does not exist yet from the prepared template. Build the base first, then add features.
Decide four things first
Claude needs these four things. Short answers are enough.
| What to decide | Example |
|---|---|
| App name | lost-and-found |
| What the app does | Record items left behind in the building and track whether each was returned to its owner |
| Main features | Register an item, list and search items, mark an item as returned |
| Who uses it | Front desk staff |
The app name uses only lowercase English letters and hyphens. It becomes part of the app's URL and is hard to change later, so keep it short and clear.
Let an administrator know that you are about to create a new app. You can find out early whether a similar app already exists, and agree on who should be able to use it once it is ready.
Step 1: Build the base
In Claude Code, select the algoritmi-sandbox-vibe-coding-platform folder, start a new conversation, replace the parts in 【 】 below, and send the request.
Starting from the prepared template, Claude creates an app that already has sign-in and the settings needed to go to production. The first PR contains only the base. The screen shows very little, and that is correct.
Step 2: Check and merge
When the app is ready, check it on the screen Claude opens (Check the Screen).
The first PR of a new app gets a preview without your asking. Whether you can sign in and open the app can only be checked in a preview. When the "Preview deployment" comment on the PR turns into a link with the app's name, open it and check. Then follow Check and Merge to merge.
A few minutes after you merge, the app is ready in production and is registered in the App Portal.
At first, only administrators can open a new app. If the preview or production shows "Access denied", ask an administrator: "Please let me open 【app name】".
Step 3: Add features
Once the base exists, add features.
- For the first features, which usually span several screens, use Bigger Features. You make a plan, then work in small stages.
- For the fine adjustments after that, use Small Changes.
Step 4: Let your colleagues use it
An administrator decides, role by role, who can open an app. When the app is ready for others, ask an administrator.
Example message to an administrator: "Please let the front desk staff use 【app name】. Please also tidy up its name and description in the App Portal if needed."
For people who have not been given access, the App Portal shows "Access restricted" on that app.
What an app can do
| What you want | How |
|---|---|
| Store data: register, list, search | You can ask Claude. This adds a table, a container for data, so have an administrator look at it before you merge |
| Upload photos or files | You can ask Claude. Say "do it the same way as the image gallery in Example App". The first time, an administrator may need to set something up |
| Send notifications by email | You can ask Claude. Say "do it the same way as Example App". The first time, an administrator may need to set something up |
| Give different roles different features | You can ask Claude. An administrator sets who has which role |
| Connect to an outside service such as Slack | This needs a secret value such as an API key. Talk to an administrator first |
Quiz
You merged a new app. When a colleague opens the App Portal, the app shows 'Access restricted'. What do you do?