Usage Stats

This page is updated periodically to report usage statistics of Scrite. The stats on this page were updated on 3rd October, 10:00 AM IST.

Installation Count

– Windows302673%
– macOS86320%
– GNU/Linux2727%

Active Installations

The following chart plots number of active Scrite installations in each month starting from June 2020, one month after the first public beta was released. Installations of Scrite on test machines are not counted.

Bar graph of active monthly active Scrite installations since June 2020
Statistics for October is tentative, because the month is still underway.

An installation is considered active if it is launched atleast once in a given month. Assuming that each user has one installation of Scrite, we approximate active installation count as active user count. (NOTE: Installations of Scrite on computers used for developing, testing and building the app are not counted.)

The active user count has been steadily increasing since November 2020, with the pace rapidly picking up even further since March 2021 after the release of version 0.6 beta.

Average Usage Stats

The following graph plots the average number of times Scrite was used by a writer in that month. For example, in the month of July 2021, we had 659 writers using Scrite for an average of 13.41 times in that month.

Bar graph of average monthly use per writer, since June 2020
Statistics for October is tentative, because the month is still underway.

NOTE: Here we make an assumption that each writer has installed Scrite on one computer.

New Installs vs Upgrades

This chart plots new installations vs upgrades in each month since the first public beta of Scrite. In the recent months we are noticing that each day Scrite acquiring 8-9 new users, up from 5-6 users that it used to be early this year.

Bar graph of new Scrite installations vs upgrades for each month since June 2020
Statistics for October is tentative, because the month is still underway.

In the months between May and September 2020, we had a spike in new users. We can attribute this to the fact that

Since October 2020, we notice that the number of upgrades far exceeding the number of new users in each month. We would like to believe that this is because writers are happy to stick with Scrite month-on-month. Also we have not participated or invested in publicity of Scrite.

Version Stats

Shown below is a graph of active users by version.

While a little more than 30% of our entire user base is using version 0.6.x beta and close to 25% have already upgraded to the latest version 0.7.x beta. Although we still notice many of our users using the previous beta releases.

Here is what some of our users are saying about Scrite.

Forum Stats

The discussion forum is actively used by users to submit feedback, discuss product features, ask questions and report bugs.

User Registrations558
Topics Created199

GitHub Stats

The entire source code of Scrite is available on GitHub. We know of many developers who have downloaded the code and reviewed it.

A Star in GitHub is similar to a the Like button social media platforms. Developers who like the project for its intent, code quality, software engineering methodologies or other similar such reasons, tend to star-mark a project.
Developers who want to actively follow the progress of a project on GitHub can mark the project for watching.
Developers who want to take a copy of the source code and try out ideas of their own tend to fork a copy of the code from the main repository.

You can look up detailed stats regarding code commits on our GitHub page.

How are app usage stats determined?

Each installation of Scrite is assigned an unique installation ID, that is locally generated and stored in the writer’s computer. The installation ID remains same across all updates. However, if the writer resets their system (by switching user accounts, by purging application installation data or by formatting & reinstalling the OS), then a new installation ID is generated.

Every single time the Scrite app is launched and for every hour of use there after, the Scrite app checks our server for updates. A standard HTTP call is made to check for updates, along with which a unique user-agent string is sent. This user-agent string contains some information about the Scrite instance requesting for updates. Information like installation ID, OS type and version. All HTTP requests are logged on our server and are therefore timestamped.

Periodically we process these logs to determine the number of installations, active usage stats, update cycles and so on.