The time has finally arrived for us to stop talking about our new crash monitoring service CritiMon, but to actually show it off and let our fellow developers make use of our new service.

We are now opening up registrations to our early access preview so we can get user feedback and find out what you find great about it, what’s not so great and what features are the most important to you.

We care and we greatly value the feedback we get from our customers and we will endeavour to make changes and add feature as quickly as we can.

What Is CritiMon?

CritiMon Logo

For those of you who are new here, lets explain a little about what CritiMon is. Its a cross platform, any programming language crash monitoring and error exception reporting system. We have a number of SDKs and libraries that are available such as Android, Javascript with more to come. With just a couple of lines of code you can start sending unhandled crashes, errors that might force close your software/app or stop your web page rendering or displaying information correctly.  

However, receiving crashes for just major faults that force close or stop scripts processing or are very well and good, but what about the errors that happen internally and that are handled by your code, such as in try/catch blocks. These errors shouldn’t happen, but in the event they do they get handled, it might not be able to carry on with what it was doing, so you might just display an error to the user and then rely on them sending you a bug report. Can you really rely on your customers reporting issues to you. This is where CritiMon comes in.

Where you need to in your exception block, you can send the details of the exception to CritiMon. This will include all the information required to help you debug the problem, such as app version, the file, the line number and some device specific details, such as operating system for example.  

Plus if you need to, you can submit custom properties as a JSON object, in any structure you see fit to provide some extra debug information that you might need to determine what caused the issue.

For each crash received, it allows you to assign them to your team members, add notes to keep tracks of what's happening with a particular error and hide particular crashes that you no longer want to see, for example crashes from previous app versions, specific crashes that you won’t be able to resolve such as external third party API issues or specific hardware bug.

Why We Built CritiMon

I’ve been a developer for 15+ years, as a hobby and as my main job. As an individual developer I was always looking for a crash monitoring platform that would cater for everything I develop in. I develop in a wide range of things such as software applications for Windows/Linux, web frontend and backend and mobile development with Android. There wasn’t a crash platform that would cater for every platform and/or that was affordable and signing up for multiple accounts to cater for each platform just wasn’t practical and wasn’t something I was prepared to do.

Another reason was out of the crash monitoring I have tried, alot of them are delayed in how quickly they notify you about a crash – some up to 24 hours. If I have a problem in a release I don’t want to wait up to 24 hours to find out there’s a problem, waiting that long could have a huge negative impact on a large proportion of our user base.

Another reason was that the Google Play Store wouldn’t always send crashes. We had an app in the play store that had around 500-1000 users with each of our web servers receiving around 2000 requests a day. Then all of a sudden, our user base started plummeting and I couldn’t see any reason why. Everytime I tested I wasn’t able to replicate any issues and the Google Play store didn’t show any crashes or errors within the app. Eventually I tracked it down to a large proportion of users uninstalling were from a specific android version. Eventually I tracked it down to a third party library had received an update automatically from Google Play services and this was causing the crash but unfortunately by the time I discovered this, the damage was already done and the app never recovered. This was the final nail and from this spawned the idea of CritiMon.

CritiMon Launch

Today is the day we open up signups to create an account and start receiving instant crash notifications of new crashes and ensure issues that make it to production are solved as quickly as possible. We are initially launching as an early access preview so we can iron out any issues and get user feedback on what features you think are most important and what parts of CritiMon you like and what parts you don’t. During the early access preview, we will initially be limiting signups to 250 users but this will be expanded on until we do a full public release.

We have three price plans, a free plan, a small plan and a pro plan so I’m sure there’s a plan that’s suitable for you, and, if you sign up during the early access, you will receive 50% off any paid plan for the liftetime of your subscription.

CritiMon Pricing

If you have any questions or want to give us any feedback then please drop us an email at [email protected].

You can also find documentation about creating your own custom SDK for platforms and/or languages not officially supported by checking out our knowledge base at

Also, if you need any help, you can raise a new support ticket, or if you want to request new features for the platform you can raise them via our support portal at

We really hope you find our new service useful and we can't wait to find out your thoughts and where we can take it next.

Chris Board
Boardies IT Solutions