"Checklist" before commercial release of a bubble app

Need help
1

Hi all,

After several weeks of development, our web-app is ready to be released to our first customers.

However, I’m wondering if I haven’t missed something very important before releasing it (like privacy topics, security, performance, etc…) and I don’t know what are the key things to check before releasing a product.

Is anyone have something like a “Checklist” before releasing an app ?
If yes, I would really appreciate if you can share it, so we will be sure to release a robust and complete finished app.
I’m sure I’m not the only user to ask myself the question.

Thank you very much in advance,
Thomas

2 Likes
2

Some believe the conventional wisdom that if you are not ashamed of your app upon publishing it … then you are launching too late …

But … that is them

Many folks monitor as much as they can and iterate/improve as fast as they can. A never ending process some may say …

3

Hey, I’m in the same boat - a couple of weeks off release I think, and trying to work out a checklist. I’ve come up with something similar to what you have.

  • I know the app works well, at least for my setup, on both desktop and mobile. I anticipate small glitches here on other operating systems, devices, etc, but nothing that will truly break it.

  • I want to spend the next week investigating privacy, making sure it’s as watertight as it can be. Going for a belt and braces approach where I have privacy settings set AND a workflow that redirects the user if they shouldn’t be on that page.

  • I want to work on analytics for myself, make sure I’m getting all the data I need to improve the product, currently sending data to Airtable, but want to configure it a bit better.

  • Finally, the big one: Stripe. Payments are obviously hugely important. I’ve successfully set it up to take subscription payments, but I want to take some time to explore all possibilities (ie their card fails, they cancel subscription, they want to take a second subscription). Lots of testing to be done here.

Do let me know if you figure out anything you wished you’d checked before launching :slight_smile:

4

Hello Oliphant,

Sorry for the late answer. I finally released it with some kind of privacy and data testing.

Thank you very much for this first answer, especially for the 2 lasts points on analytics and Stripe which are not the first topics that come to mind.

I’ll publish a new “checklist” template when I’ll have enough feedbacks from our first users :slightly_smiling_face:

Thanks again for the answer !
Best,

1 Like
5

Really like this launch checklist idea. If you’re putting together a list, here are a few more generic things I’m keeping in mind for launch. Looking forward to seeing this progress and good luck with the launch!

  • Proof copy
  • Double check any development permissions/constraints (pages only viewable to specific users)
  • Internal tests in development (various browsers and devices)
  • External tests in development (outside your development network if possible)
  • Save new development state
  • Push live
  • Retest everything while live (run through a few workflows: create a new user, post something, interact a bit, etc)
  • Peek at databases (live vs dev)
  • Tell the world!
  • Setup status monitor or feedback solutions
1 Like
6

This topic was automatically closed after 70 days. New replies are no longer allowed.