If you're new here, I'm André, a tech entrepreneur and founder of LaunchFast, a stack designed to help web developers significantly speed up their project development time. I post daily updates on my journey and progress.
Alright, folks, today’s a short one.
Here’s what got done:
Reviewed the remaining 7 developer test drives of LaunchFast.pro
Reviewed the remaining 7 developer test drives of LaunchFast.pro
I reviewed 7h+ of video and noticed that 90% of the feedback came from the first 2 test drives.
The remaining test drives caught all the same pain points.
This is the Pareto Principle at play: 80% of the outcomes come from 20% of the effort.
So do yourself a favor and iterate on your product after every test drive with real users.
This will allow you to improve considerably faster.
Here are the main things to improve on the CLI:
Allow users to use their favorite package manager (npm, pnpm, yarn, or bun)
Automatically install the Fly CLI and reload the env vars
Explain why we need Fly’s CLI and a GitHub’s Private Access Token (because LaunchFast deploys to Fly and we need to copy LaunchFast’s template)
Override create-remix’s prompts for more forgiving ones (installation sometimes fails when users don’t add a “./” to the folder name)
Add numbered steps (e.g. 5/12) so users know how many steps are left
Make the instructions’ color more vibrant (so users don’t skip them)
Simplify the process (e.g. don’t ask for the App name, users can edit that later)
Detect installed code editors (VS Code, Cursor, etc) and ask which one they want to open the project with
Add a try-catch block that outputs the error in case the script fails (to make it easier for the user to debug and recover)
And a bunch of other minor improvements…
Next steps
Tomorrow I’ll work on coding these improvements on the CLI.
There’s also another test drive scheduled in the afternoon.
I’m eager to see the reactions after these improvements.
That’s it for today folks. Have a great upcoming Friday ♥️
🔥🔥🔥