Jamku Usage Pattern March 2022

[adarshmadrecha]

We strongly believe in Transparency in everything we DO.

We often receive questions like -

• Total Jamku User count?
• In which Cities/Countries Jamku is present?
• How many users use Jamku on a regular basis?
• How true is the claim that "Jamku is India's Largest CA Practice Management Software "?

Background
We have been sharing the Google Analytics insights in our WhatsApp groups (for Jamku Users) for many years now. This time, we are sharing the same analytics to All.

Page Views

Home page /dashboard is the highest viewed page (No surprises here).
Task Search Page /task is 2nd highest. Afterall, Task management is the heart of Jamku.

User Count

This shows Jamku users for 3 buckets - Monthly, Weekly, Daily.

Usage basis Time of the day

Geography of Users (Dark blue indicates high usage, light blue indicates average to low usage and grey indicates no usage)

On Global Map, based on Country

On India Map, based on City

Top 25 Cities (based on number of users)

Notes:

1. Google Analytics data is not collected for 100% of the users. Many users use Adblocking plugins such as "Adblock Plus", "AdBlock" which also blocks tracking by Google Analytics.
2. Some of the users are behind corporate network firewall which blocks Google Analytics IP address. Hence these users never show in these reports.
3. All these data are for "last 30 days". These screenshots were taken on 29th March 2022 from Google Analytics Dashboard.

[adarshmadrecha]

At Jamku 👩‍🦰, We user Firebase Monitoring to track real world API performance.

Here's the glimpse of the average API response time.
We currently have 2 servers

• api.jamku. - Main API Server, (used by jamku.app)
• api22.jamku - Backup API server (used by v3.jamku.app)

FYI, one second is 1000 Milliseconds. Based on more than 50 Lacs (5.1 Millions) API request of Last 30 days, the main API server is responding in about 1/10th of a second. The backup server runs on bleeding edge technology - http3, more about it here. It responds in 60 Milliseconds. That's insanely fast.

Note:

1. The firebase monitoring tracks full response time. i.e. the time from request being sent from device/browser to the time it is received by the device/browser. Hence, we use the term "real world API performance", as it factors in the internet speed of the users.
2. The server response time from when it receives the request and the time it responds is tracked using AWS, the server's response is much faster than shown in firebase monitoring dashboard.