← Back to Which technology will my app be built with?
Can I see what my first version will look like before it is built?
Short answer
Not as a picture: Kai-Zen describes your first version in words, and you first see its screens when the first step is built.
Before you start
Words used here (1)
- Kai-Zen
- Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper
Before anything is built, Kai-Zen, the planning agent, shows you the whole plan for one approval. It describes your first version in words: who it is for, what it must do, how good it must be, and the steps it suggests, with what each should bring. It does not show a drawing or a mock-up, a picture of how a screen will look: no step of Kai-Zen's makes one, and GilbApp has no screen that draws one.
The look you can choose before building. For an app built on GilbPlatform, Kai-Zen's round of questions asks about the app's style. The default is the App Style Studio, a developer tool from GilbPlatform's code bank, a store of code to reuse; it is not part of GilbApp or of your app. In it the style is chosen from a ready palette, one colour of your own, or the colours read from your website, with fonts, button and window styles, light or dark as the default, and a logo. When saved, the style is kept in the app's own vault, readable by anyone, and the app reads its look from there. This answer does not show how a person who does not code opens the studio. You may name another source for the style instead. If you want to choose the look yourself, write to [email protected].
You can also show what you like: name apps you like and say what you like about each. The answer Can I show examples, drawings or screenshots of what I want? shows how.
The first real thing you see is the first step. It sets up a ready-made core app with a sign-in, plus something useful for you if it can, and it is kept as small as possible, so it comes early. When a step changes a screen, Agent.Coder, the agent that builds apps, opens the changed screen in a real browser at phone size, takes a screenshot and counts the errors before it hands the step back; if it has no browser tool, it says so and the agent that handed it the work takes that proof. When the step is live, Kai-Zen asks you to check it live, the way a user would; send back what you want different, and it is fixed and put live again until you approve. It is put live only with your go.
At the approval you can say what you want first and what can wait, such as the screen you most want to see.
This answer is written for a computer screen.
Source: Standards: Kai-Zen.New (Setup, Show); App.Style.Choose (Open: a developer tool, not part of the app; Colours; Look; Logo; Save; Read); Kai-Zen.ValueDeliveryStepRules (First, Small); Kai-Zen.HumanCheck; Kai-Zen.GoLive; Agent.Coder.AfterIncrement. GilbApp 96968de7: no mock-up or style screen in src. Live answers: Can I show examples, drawings or screenshots of what I want?, How big should my first version be?, How does Kai-Zen put a change live?.
Checked against GilbApp d529620.