5 ms·

Crashlytics was never really on my radar until today, but I'm really impressed by their design work. Really great stuff.

zmitri 14y ago
Crashlytics has literally changed the game with regards to crash reporting. Their UI and customer service has been wonderful (unlike most other mobile service providers...) and I really hope they continue to offer their services to devs.
- pifflesnort 14y ago
  They're very big on polish and claiming to be awesome, but it's all smoke and mirrors and gamesmanship. Drill down on a crash for example: https://d1f4seebrc9wq7.cloudfront.net/blog/wp-content/uploads/2013/01/02.41.png https://d1f4seebrc9wq7.cloudfront.net/blog/wp-content/upload... All the information provided at the top is done with great attention to beautifully rendered icons, and it's all totally useless for diagnosing a crash report. This is supposed to be a development tool, not an advertisement.
  - zedred 14y ago
    Agreed, I've had limited experience with the product and was disappointed. I think the above comments are correct, Twitter wanted them for the data not the talent.
  - bitcartel 14y ago
    Apart from the fancy graphics, any reason to use Crashlytics instead of the open-source QuincyKit?
  - zmitri 14y ago
    Have you used crashlytics before? I use it in production with an app that has >50K users. It shows you the exact lines, and break down where it happens. What you showed isn't even important.
    - pifflesnort 14y ago
      > It shows you the exact lines, and break down where it happens. So they support DWARF and backtraces. Just like everyone else. > What you showed isn't even important. Yes, exactly.
      - deleted 14y ago
        [deleted]
  - mackworth 14y ago
    I don't have much experience with other Crash reporting systems for iOS besides Crashlytics, but I will say that overall I have been happy with them. The image you linked to leaves out the actual stack trace, but trust me it's there. The reason I ended up going with them is that they are 1) The library is tiny and isn't bloated with things I don't need 2) It's integration with Jenkins is great. It automatically uploads my dsym with the correct build number and all crashes from that build get tagged with that build number. 4) Support is fast 5) Love supporting a local Boston company I will say that some of their design is a little over the top, they certainly love skeuomorphism. One thing that kind of annoys me about their site is that the content is a fixed width. This is frustrating because they add "..." to shorten some labels to fit instead of using all the screen real-estate available.

zmitri 14y ago

Crashlytics has literally changed the game with regards to crash reporting. Their UI and customer service has been wonderful (unlike most other mobile service providers...) and I really hope they continue to offer their services to devs.

pifflesnort 14y ago
They're very big on polish and claiming to be awesome, but it's all smoke and mirrors and gamesmanship. Drill down on a crash for example: https://d1f4seebrc9wq7.cloudfront.net/blog/wp-content/uploads/2013/01/02.41.png https://d1f4seebrc9wq7.cloudfront.net/blog/wp-content/upload... All the information provided at the top is done with great attention to beautifully rendered icons, and it's all totally useless for diagnosing a crash report. This is supposed to be a development tool, not an advertisement.
- zedred 14y ago
  Agreed, I've had limited experience with the product and was disappointed. I think the above comments are correct, Twitter wanted them for the data not the talent.
- bitcartel 14y ago
  Apart from the fancy graphics, any reason to use Crashlytics instead of the open-source QuincyKit?
- zmitri 14y ago
  Have you used crashlytics before? I use it in production with an app that has >50K users. It shows you the exact lines, and break down where it happens. What you showed isn't even important.
  - pifflesnort 14y ago
    > It shows you the exact lines, and break down where it happens. So they support DWARF and backtraces. Just like everyone else. > What you showed isn't even important. Yes, exactly.
    - deleted 14y ago
      [deleted]
- mackworth 14y ago
  I don't have much experience with other Crash reporting systems for iOS besides Crashlytics, but I will say that overall I have been happy with them. The image you linked to leaves out the actual stack trace, but trust me it's there. The reason I ended up going with them is that they are 1) The library is tiny and isn't bloated with things I don't need 2) It's integration with Jenkins is great. It automatically uploads my dsym with the correct build number and all crashes from that build get tagged with that build number. 4) Support is fast 5) Love supporting a local Boston company I will say that some of their design is a little over the top, they certainly love skeuomorphism. One thing that kind of annoys me about their site is that the content is a fixed width. This is frustrating because they add "..." to shorten some labels to fit instead of using all the screen real-estate available.