Skip to main content


Another crash reporter? Why?

Because all existing solutions fall short. PLCrashReporter comes very close, but not quite:

It can't handle stack overflow crashes.
It doesn't fill in all fields for its Apple crash reports.
It can't symbolicate on the device.
It only records enough information for an Apple crash report, though there is plenty of extra useful information to be gathered!
As well, each crash reporter service, though most of them use PLCrashReporter at the core, has its own format and API.

KSCrash is superior for the following reasons:

It catches ALL crashes.
Its pluggable server reporting architecture makes it easy to adapt to any API service (it already supports Hockey and Quincy and sending via email, with more to come!).
It supports symbolicating on the device.
It records more information about the system and crash than any other crash reporter.
It is the only crash reporter capable of creating a 100% complete Apple crash report (including thread/queue names).
It can be compiled with or without ARC.



Popular posts from this blog

Pattern: Riblets vs. VIPER

Engineering the architecture behind Uber's new rider app

Not being held back by our extensive codebase and previous design choices gave us the freedom where we otherwise would have made compromises. The outcome is the sleek new app you see today, which implements a new mobile architecture across both iOS and Android. Read on to learn why we felt the need to create this new architecture pattern, called Riblets, and how it helps us reach our goals.

The platforms share:

Core architectureClass namesInheritance relationships between business logic unitsHow business logic is dividedPlugin points (names, existence, structure, etc.)Reactive programming chainsUnified platform components
Each Riblet is made up of one Router, Interactor, and Builder with its Component (hence the name), and optional Presenters and Views. The Router and Interactor handle the business logic, while the Presenter and View handle the view logic.


Stetho - A Chrome debug bridge for Android applications

Stetho is a sophisticated debug bridge for Android applications. When enabled, developers have access to the Chrome Developer Tools feature natively part of the Chrome desktop browser. Developers can also choose to enable the optional dumpapp tool which offers a powerful command-line interface to application internals.

Facebook Github


WireMock is a flexible library for stubbing and mocking web services. Unlike general purpose mocking tools it works by creating an actual HTTP server that your code under test can connect to as it would a real web service.

It supports HTTP response stubbing, request verification, proxy/intercept, record/playback of stubs and fault injection, and can be used from within a unit test or deployed into a test environment.

Although it’s written in Java, there’s also a JSON API so you can use it with pretty much any language out there.