CritiMon

Launched a new version of CritiMon. The web site is mostly some bug fixes and small improvements. I've made some small changes to the landing page, one being the pricing section I think I've made a bit easier to see the differences and I've added the promo video on to the landing page as well. I've also add a submit enquiry form to the bottom of the page - thinking I might get rid of the chat bot that's in the bottom corner, doesn't get used that much, and when it does its usually spam. Any feedback here would be appreciated.

I've also made a change to the official C++ library for CritiMon. The earlier version could only later for crashes that were or inherit std::exception but it now registers certain signals such as SIGABRT, SIGFPE and SIGSEGV to name a few. This means that with the C++ library you can now receive any type of crash within your C++ applications, not just standard exceptions.

Woke up this morning to find I had my first user sign up to CritiMon. However, they've signed up around half 7 UK time and then not done anything, no registered apps or anything. From the looks of the analytics, they signed up, went to the account settings and then nothing else.

What's the best thing to do in this situation, wait a day or two and try contacting them, contact them straight away to see if there's something they don't like or don't understand?

I've just released a new version of CritiMon which changes the on boarding process based on some feedback that I got when I nearly had a sign up.

When you sign up it removes the First Name/Last Name requirement to be just the name, and also removes the security question and security answer, so now just need, name, company, email and password.

I've also added the option to use Google Sign On so you can sign up/sign on with a single click.

Just released a new version of CritiMon that adds the option to prevent development and testing devices from reporting crashes and errors while you are working on a project.

The idea is on the first crash/error that is received, on the crash menu you can select that the crash came from a development device. This then means that if a crash comes from the same device it ignores the crash and doesn't save it, as well, not including it in the active user analysis or app release detection. This ensures that the crash reporting doesn't get flooded in crashes and errors while you are developing and you know that the crashes are only coming from your actual users.

You can from the account settings see a list of development devices and turn on and off whether or not crashes should be reported for the development device.

Hi IH,

Its taken a fair amount of time, but I'm pleased to say I've finally managed to release a new version of CritiMon, so hopefully, people like the changes I've made so can make some nice progress fingers crossed 😀

One of the more noticeable changes is to remove the red menu on the website as feedback said it made the site look spammy/danger which wasn't exactly the look I was going for 😩

I've made some changes to the landing page as well so hopefully that makes it look a little better and informs well what CritiMon is.

I've also changed (which you can see on the screenshot at the top of the landing page) where the active user and crash group charts are to remove the black background and make the charts full width to the screen instead of being centered on the page.

I've also added support for 2 new official libraries for Python and Ruby so the full list of supported languages/platform now includes:

• Android (Java and Kotlin)
• C# (.Net Framework and .Net Core)
• Javascript
• PHP
• Python
• Ruby

There's a free plan, but while in beta there is a 50% off for anyone who signs up to a paid plan and it will remain 50% off for the lifetime of the subscription.

I've also added 2 coupons during signup so if you want to sign up to small plan use coupon code SMALLPLAN_50 and for a pro plan use coupon code PROPLAN_50 which will give a further 50% off for the first 3 months.

As always if there's any feedback I'd love to hear it.

Thanks
Chris

I just launched CritiMon to Product Hunt. You can check out the product hunt page at https://www.producthunt.com/posts/critimon-critical-monitoring.

I've also added a couple of new features such as an activity dashboard which provided a breakdown of crash statistics across your organisation such as crash counts, crash per a platform and an activity stream to show who has been doing what during the past week.

I've also implemented @mentions to people within your organisation when adding notes to crash.

I've been using PHPStorm (https://www.jetbrains.com/phpstorm/) for a few years and developed the frontend and API for CritiMon with PHPStorm.

Another really important tool that I use everyday, for both my personal project and my full time job is Insomnia (https://insomnia.rest/). Insomnia is REST API test client which was super useful for sending API requests for the website and the crash API.