How We Build World-Class Tech Products?
In my previous blog post, I discussed how to objectively measure website and app quality and evaluate quality from day one using a well-designed observability setup with open telemetry at its base.
Toward the end of that post, I covered our definition of a good tech product. This is how we define it -
1. App launch time (or website loading time) should be as fast as possible. Less than a second is the benchmark here.
2. API response time should be as low as possible, specifically P99 and P95 latency. Less than 150 milliseconds is a good number to start.
3. Database query and write times should be as low as possible. Read latency should be less than ten milliseconds. (For a single query).
4. The crash-free rate should be as high as possible. The last three platforms I built had a 100% crash-free rate (yes, it's possible) at a sufficiently high scale. But anything above 98% is a good number here.
5. The Number of bugs users encounter per month should be a single digit (less than 10). Bugs are inevitable, especially if you are developing rapidly. However, the number can be kept in single digits if careful enough.
6. The app/website/platform should have the same performance at any scale for any feature.
7. The cost of the entire tech product should be as low as possible. If your infrastructure is over-provisioned, you may get a short time gain in performance, but you are setting yourself up for failure when the actual scale hits. Also, you are just hurting your bottom line.
Some potential clients read my post and asked me the real question - How do we do this? How do we make such bold promises?