Last week I called Bolt magic. This week? Stripe earned a standing ovation.
When you know what you want—tiers, add-ons, discounts—Stripe just works. It took less than two hours to implement my first pricing page. Monthly vs. annual toggle? Done. Growth tier logic? Seamless. Branded UI? Right there. And it integrated cleanly with everything I already had in Bolt.
As someone who loves pricing and packaging, it’s satisfying to see a tool do exactly what it promises: get out of the way so your customers can see value clearly. Pricing isn’t a spreadsheet—it’s a story. Stripe helps you tell it well.
🛠️ Build Log: Days 7–12
Day 7
- Fixed secrets in Netlify deploy. Whoops.
- Solved Bolt login redirect with a container-based exception and temporary hardcoded credentials.
- Updated branding (fonts were finicky)… four times
- Added personal story content to test UI – it looked so good.
- Tracked swipes with DB policy.
- Introduced category structure: default and genre.
- Enabled admin table editing.
- Created collection button and displayed story cards per collection.
- Recorded progress for share-out.
Day 8
- Refined swipe screen per collection– unexpectedly fixed color issues and personalized login screen as well.
Day 9
- Created full pricing page.
- Implemented pricing tiers, growth logic, and monthly/annual toggle.
- Branded and functional in just a couple of hours.
I ran first Bolt QA/code review and it gave me false confidence going into the end of the week… “App is secure and well-structured, but pricing plan logic still needs enforcement.”
Days 10–11
- Took a well-earned break.
Day 12
- Hit a wall with admin table functionality during load testing.
- Bolt flip-flopped table logic—fixed, broke, fixed again.
- Set up category creation… but Bolt missed DB logic
- Clarified the UI by restricting category types
- Asked for user-specific categories and Bolt removed visual elements instead.
- Lost category type colors
- “You’re absolutely right!” the assistant said. Yes—I know. That’s why I’m the PM.
This was the week I started pushing Bolt hard. When it works, it flies. When it breaks, I feel every missing credit. Sometimes it feels like real agile SDLC with fixing something breaks something else, feedback on how to write better code (i.e. prompts) but when Bolt is writing its own prompts for fixes, the QA process is lacking.
Evolution of Admin Page and Categories
Krista Gamble | K.M. Hasling 