Is error/analytics tracking a must for an MVP?
Yoooo!
Long time lurker here 👋. I'm finally ~90% done with a product and am wondering if I'm overengineering my MVP. I've spent hours implementing error tracking (Sentry) and analytics tracking (Amplitude) into my mobile app.
This got me thinking... How many of you implement this on the first iteration of your product?
Thanks,
I like to monitor high priority events such as signups & conversions with LogSnag. For the rest, I’m logging on some Discord web hooks, and some analytics tools (self-hosting my Plausible instance).
+1 on Logsnag. Awesome tool, and Shayan (the creator) is great w/ support and building new features.
I just launched the MVP for feedbeggar.com and use Sentry. It's a Laravel app and integrating honestly took only two minutes.
Sentry already helped me find out why some of my backups failed. So yeah, it probably already payed off.
Good MVP = Solve on problem well.
BAD MVP = Solve many problems in a buggy way
I think it also depends on how many people are you expecting, how many user journeys you have and how complex they are. If you already know you’ll have a considerable number of user (bc you have built a waitlist or something like that for instance), it may be useful to spend some time on it before launching.. else I’d go with something easy and quick to implement ( hotjar maybe? ) and then try to find here how users are doing with the journeys, if they’re getting stuck at some point, etc, and you can start there to implement some other tools like sentry
Hey Raul I'm in a similar situation to you. I think the error reporting is a must, for the analytics side it might not be completely necessary, but at the least it can give you insights into what features are being used and could help with customer development and future product iterations. What type of analytics are you tracking?
I guess it's really dependent on the type of project, business model, the duration that you estimate to stay in that stage, and the end user.
Just Launch !
Error tracking - for sure. Given that it's an MVP, you will need it even more.
Analytics - not that much. Unless you are planning a big paid promo campaign.
For any project that I start and which will be used by end-users, Sentry and Usermaven must be installed. Sentry, when linked with Slack, will keep you up-to-date on the types of errors your customers are facing so you can fix them as soon as possible.
I believe that speed is crucial when launching your MVP. If a bug exists in your product and a customer becomes stuck, but does not inform you, you will be left in the blindspot. As a result, other users may encounter the same issue.