Day 2: I Built Per-User Onboarding and Settings With Cloud Code
Watch an AI agent turn four onboarding questions stored in the AppAmbit CMS into per-user settings for a Flutter app. Includes a settings screen, a server-checked password change, and a missing signing secret fixed live.
Watch the full tutorial or read the summary below
Overview
Day 2 of the Move Well build: an app that nags you to fix your posture, built prompt by prompt on AppAmbit. Move Well is the app's working name; on Day 4 it becomes Unshrimp.
The onboarding turns four questions into a setup made for each user. The questions are: hours spent sitting, work hours, where it hurts, and how hard the app should roast you. The agent stores the questions and 10 exercises in the AppAmbit CMS, then turns the answers into per-user settings.
Onboarding breaks on camera because a function is missing its signing secret, and the fix is made in the dashboard, never in the code. Next comes a settings screen with editable hours, interval and goal, plus a password change checked against the stored hash. The Database proves it: when a setting changes, only that user's row moves.
In This Episode
- 4 onboarding questions and 10 exercises created in the AppAmbit CMS by the agent, live and editable
- Screen time sets the pace, work hours set the window, pain picks your stretches, and the tone picks the roast: gentle, direct or no mercy
- Your answers become your own settings: interval, daily goal and active hours
- The bug: onboarding fails because the function is missing its signing secret. The fix goes in the dashboard, never in the code.
- A settings screen where every field is editable and each change saves on its own
- Proof in the Database: change a setting and only your row moves
- Change password: checked against the stored hash inside AppAmbit, and the old session ends
Chapters
- 0:00 Recap and today's goal
- 0:35 4 onboarding questions in the CMS
- 1:42 Answers become per-user settings
- 2:08 Onboarding as a new user
- 2:42 It breaks: the missing signing secret
- 3:28 Bob's setup, saved in AppAmbit
- 4:00 Building the settings screen
- 5:04 Same bug, same fix
- 5:44 Change a setting: only your row moves
- 6:24 Change the password (checked on the server)
- 6:59 Wrap-up and what's next
More in the Series
- Previous: Day 1: I Built a Secure Login With AI Agent and AppAmbit
- Next: Day 3: I Built Reminders That Roast You on Time
Links
Frequently Asked Questions
Q What are the 4 onboarding questions?
How many hours a day you sit, your work hours (which set your active window), where it hurts, and how hard the app should roast you: gentle, direct or no mercy.
Q Where do the questions live?
In the AppAmbit CMS, as content types. You can edit them from the dashboard without touching the app. The 10 exercises, sorted by body zone from neck to wrists, live there too.
Q Why did onboarding fail?
The save function was missing its signing secret, the same one login uses. It was added as a secret value in the dashboard, never in the code, and the function was redeployed.
Q If I change a setting, does it affect other users?
No. Only your row in the Database changes.
Q How does changing the password work?
You enter the current password and a new one. AppAmbit checks it against the stored hash, and the new password ends the old session.
Ready to get started with AppAmbit?
Monitor your mobile apps with real-time crash reporting, analytics, and app distribution.
Start Free Trial