Readit News logoReadit News
okgabr commented on Show HN: App Performance Monitoring (APM) for mobile apps   instabug.com/product/app-... · Posted by u/okgabr
okgabr · 5 years ago
Instabug first launched on HN back in 2013 as a bug reporting SDK for mobile apps. Over the years, we heard from mobile developers that they want more granular metrics about how their apps are performing in the wild, so we released a new APM tool. We found that most APM products in the market focus on server-side monitoring, so we built ours specifically for mobile developers.

Here is a quick summary of what we launched:

1. UI Hangs: track the performance of each ViewController, Activity, and Fragment in your app.

2. Network Performance: we record the response time of all your network calls, as seen by users and show you the full round-trip with both client-side and server-side errors.

3. Execution Traces: you can define your own traces to track the performance of any logic in your app that can be a bottleneck to your users’ experience.

4. Apdex Scores: a single metric that represents your overall app quality as perceived by your users with a breakdown of satisfying, tolerable, frustrating, and crashing sessions.

5. App Launch: see how long your users are waiting from the moment they open the app until the app is fully launched and accepting touch events, across devices and OS versions.

Building this was a bit tricky for us. APM is the most data heavy and complex product we’ve built (specially that we had to switch to working remotely overnight like most of the world). And since APM is all about performance, we had to make sure to keep the footprint of our SDK as small as possible, and more importantly, to do so without sacrificing accuracy or taking shortcuts.

We’d love your feedback and please let me know if you have any questions.

okgabr commented on Ask HN: Did any Show HN posts turn into successful startups?    · Posted by u/portobelln
okgabr · 7 years ago
Almost 4.5 years ago we launched Instabug (www.instabug.com) on HN (https://news.ycombinator.com/item?id=5526949)

Successful is a broad term, but we have tens of thousands of apps on our platform and our SDK is running on over a billion devices. We did YC and raised multiple rounds after.

okgabr commented on What We Learned from Analyzing 100M Bugs   instabug.com/state-of-mob... · Posted by u/okgabr
coldtea · 7 years ago
I expected something much more interesting: e.g. most common types of bugs, or causes of bugs -- and thus suggestions on how they could be avoided.
okgabr · 7 years ago
Good point and sorry to disappoint you! The good news is that we still have a lot to share, this is the first time in six years to dig deeper into our data and share it with the community. I’m sure we’ll do more and more soon. A series about the most common causes of bugs and suggestions on how they could be avoided would definitely be a great start!
okgabr commented on What We Learned from Analyzing 100M Bugs   instabug.com/state-of-mob... · Posted by u/okgabr
ericpauley · 7 years ago
The figure is showing percent of all bugs, not percent of resolved bugs. Likely the rest of the 100% is unresolved bugs.

The confusion on the second point hinges in "most likely". You're likely interpreting that as the expectation of resolution time whereas they are using maximum likelyhood estimation. MLE is rather useless in this case, but it is technically still correct.

okgabr · 7 years ago
You’re right! Thanks for adding your thoughts to clarify. The wording “most likely” could be confusing indeed. How about we change it to be “Bugs discovered through Instabug are most often resolved within 24 hours of being reported.” Would that be clearer? And also saying that this is percent of all bugs, not percent of resolved bugs

u/okgabr

KarmaCake day724June 3, 2013
About
co-founder @ Instabug (YC W16), trying to help mobile developers squash bugs faster. (www.instabug.com)

email: ogabr AT instabug DOT com - twitter: @okgabr

View Original