This is the second post regarding our new Crash monitoring platform "CritiMon" coming as an early access preview in Q1 of 2019. In this post, we will be  talking about registering new applications as well as what we believe to be a unique feature that other crash monitoring platforms don't provide.

In the last post, we gave a quick overview of the purpose of the platform and how it will work. If you want more information and/or want to read the rest of the posts in this series then click here.

When you've signed up for an account, the next step is to register your application. When you register, you will see the following page:

As you can see from the above screenshot, we plan on supporting Java (Android), C#, C++, PHP and Javascript. All of the SDKs that we have for various platforms and languages will be made available open source, most likely via GitHub. Not all of these will be available when it is first released during the early access but these will be added as the platform progresses. However, there will also be a unique feature that other platforms don't do. They're will be the ability, that if we don't officially support a particular language, you will be able to create your own SDK for your own language/platform and send us crash data. Anyone will be able to do this, and of course you can distribute the SDK that you've created for others to use, however, if you want us to provide a link to your SDK then it will need to be made open source. This is to protect us, and other users to ensure that community built SDKs are not doing anything untoward and trying to collect data that they shouldn't be. We will have more information on how this will work nearer the time.

Once you've provided an application name and selected which language the app is for, you can register the application, and the application will be shown in the app view. In the app view, each app has its own unique ID which is used to initialise CritiMon along with your account API.

That's it for part 2 in our CritiMon development blog. In the next post we will be talking about viewing and managing your crashes. If you have any feedback or have any questions, then please let us know in the comments section.

*Note that screenshots are subject to change during the development of the platform so how things look in the blog post, may not be how it looks when the platform becomes available.