Pre-launch checklist

Ask us anything
1

Hello,

I need the wisdom of the crowd here :grin:, especially the ones who launched their projects.

What checks would you recommend to perform before going live with a project and put it on the market? I mean beyond the fact that it works.

I watched the tutorial about security from Joyce and it’s really good and helped me a lot. But can I go further on that specific part of security?

What other topics are relevant? What did you learn afterwards you wished you knew before launch?

Looking forward to reading you.

1 Like
2

Hey @MrUnfreeze :waving_hand:,

love this question

pre-launch is always that exciting/terrifying moment :grinning_face_with_smiling_eyes:.

A couple of things I always double‑check are:

  • Basic UX flows on both desktop and mobile (especially sign up, login, and payments if any).
  • Permissions and access rules, to be sure users only see what they’re supposed to.

Super curious to see what the rest of the community adds here too :thinking:

1 Like
3

Hi @Agustin_Carozo

Thanks for your reply!

UX: I saw that iPhone users must “dezoom” every time they load a new page. Do you know why it happens to them onyl?

Regarding permission : I’d be curious to see how others manage the subscriptions with stripe. I. E. Upon creation on an account, you must choose a plan which must be paid before being granted access. I wonder what it looks like in terms of workflow and thought process.

Thanks

4

Oh man - where to start.

One key lesson for me was that you simply cannot anticipate all edge cases once real users get their hands on your software. No matter how carefully you plan, production usage will surface unexpected behavior. That means you must assume ongoing observation and iteration after launch.

Coming from a no-code to low-code background (without being a formally trained software developer), here are a few practical takeaways from my experience:

  • Implement robust error tracking and reporting

    This includes proper handling, logging, and clear visual representations of failures. Tools like Hotjar or similar session-replay solutions are invaluable to actually see what users did when something went wrong.

  • Validate and sanitize all inputs—without exception

    Users will surprise you:

    • Emails like xyz@mail@com

    • Inputs with leading/trailing or embedded spaces

    • Text in numeric fields, numbers in text fields, and everything in between

  • Stress-test every interaction

    Expect machine-gun-style clicking on buttons. Ensure your system does not trigger duplicate events, workflows, or automations that lead to race conditions, data corruption, or downstream hiccups.

  • Test across environments

    Different devices, operating systems, and browsers will behave differently. What works perfectly in one setup may break subtly in another.

  • Optimize frontend logic and performance early

    Fetch only the data you actually need. Keep asset sizes small (e.g., convert images to WebP). Otherwise, bandwidth usage and infrastructure costs can escalate quickly once your app gains traction.

In short: real users are the best - and most ruthless - test suite you will ever have. Prepare accordingly.

What’s an important takeaway from my point of view is that you learn the most after launching your first project, so try staying relaxed and have fun. :grinning_face:

4 Likes