i published my first app on Google Play and i can't figure out how to count the total of downloads by users.
It lets me to choose between currents installations and uninstallations per day, but none that tells me the total of downloads since the publishing of the app.
To count the total of downloads i take the number of installations and i substract the total of uninstallations (i get it making the sum of uninstallations of every day!)
How to figure out the total of downloads in an easier way?
You need to code for that if you want exact number of download.
create a webservice as the app starts by sending serial number of device to server.
keep the record over there.
Related
I came across the offer by Heroku that says that I can receive free 450 dyno hours for just adding my credit card. I was wondering how the free hours are added. Are they like the standard 550 hours, i.e. added every month or is it just for one time?
Also I just want to run one dyno and so having 1000 total hours per month would be more than enough. So if they add 450hrs/month with the credit card, does that mean I can run my dyno infinitely without being charged at all?
Yes, you get 1000 dynos per month after adding credit card. I have the same.
Yes, correct you will get 1000 dyno hours once you verify your identity with a credit card. For a single APP they are enough but in case you want to add more APPs, allowed dyno hours will be sum of hours consumed by each APP. Initially 550 hours were provided to keep the APP active for 75% of time i.e. 18 hours (18*30 ~= 550).
On the Google Play Store I have always used the number of total cumulative installs as part of my growth plan.
However, I am no longer able to see "cumulative total installs". Show only "Active Installations".
It seems that Google has changed the organization again, so much so that the answers of 2019/2020 are not useful.
How can I see them?
In order to get cumulative total download on Google Play Console, I had to:
Search for “Statistics” tab
Change the report configuration a bit. First, click “Installed
audience” (the default metric), and navigate the menu as following:
Users > User Acquisitions > New Users
Click the “Edit” button And change the “Events” to “Unique Users“. This ensures that the final report will not be over-counted if you’ve had a significant number of users who have uninstalled and re-installed your app over time.
Also adjust the metric calculation to “Cumulative“. This means each
data point along your time series will be equal to your total
installs accumulated up until that day.
On your main dashboard, set your time range to "Lifetime". Then you will see the total installs in the "New users acquired" section
My understanding of the parse.com API rate limit is that it’s not a concurrent-job limit, it’s just the number of requests started in a given second. So if a user is, say, uploading a file from a slow network and it takes 30 seconds, that’s not 1 of my 30 req/s taken up that whole time. It’s just one request, the first second.
On my team, though, is a wonderful security guy whose job it is to worry. He thinks that if 30 users upload a file each, for 30 seconds, at a 30 r/s limit, no one else will be able to use our app until they are done.
Which one is correct?
Your understanding was correct. It's the number of requests started per second. The duration of the request does not come in to play.
Source: I work at Parse.
I think you are right. I've made some experiments with Parse, for example i reloaded a UITableview 10 or 20 times in one second (can't remember) for 3-4 minutes and checked the requests in the admin panel. The maximum value was always less than 30, but it doesn't matter, the point is that you can test it this way and get more informations.
Just create some test project and reload the SampleViewController.m (which contains a Parse query) 30 times in one second, after this you can check the data browser which will display the traffic by req/sec.
As a second option you can upload a bunch of images by current user in every second, since the upload time is longer than 1 sec, you can check what happens when you start uploading a bunch of images (or other data) in every second.
There are couple of apps at the Windows Phone Store which are automatically updating phone lock screen by a custom interval, lets say 1, 2, 4 or more hours.
I did some search over internet to find some articles or best practice to implement custom update interval, which is bigger than 30 minutes but without any result.
Maybe you know some code snippets or reference on articles ?
Thanks in advance!
As you have already found, the periodic agents are invoked once every 30 mins. However, you can simply do nothing until your desired update period has passed then execute your update.
You already have access to your app's isolated storage from within your background agent. You can simply store a counter in some file to track the time that has passed and once it meets your requirement you can execute your update and reset the counter.
I am using to test my web server https://buyandbrag.in .
I have tested it for 100 users. But the main server is not showing like it is crowded or not.
I want to know whether it is really pressuring the main server(a cloud server I am using).Or just use the client resourse where the tool is installed.
Yes as mentioned you should be monitoring both servers to see how they handle the load. The simplest way to do this is with TOP (if your server OS is *NIX) also you should be watching the network activity i.e. Bandwidth, connection status (time wait, close wait and so on).
Also if your using apache keep an eye on the logs you should see the requests being logged there
Good luck with the tests
I want to know "how many users my website can handele ?",when I tested with 50 threads ,the cpu usage of my server increased but not the connections log(It showed just 2 connections).also the bandwidth usage is not that much
Firstly what connections are you referring to? Apache, DB etc?
Secondly if you want to see how many users your current setup can hand you need to create a profile or traffic model of what an average user will do on your site.
For example:
Say 90% of the time they will search for something
5% of the time they will purchase x
5% of the time they login.
Once you have your "Traffic Model" defined, implement it in jMeter then start increasing your load in increments i.e. running your load test for 10mins with x users, after 10mins increment that number and so on until you find your breaking point.
If you graph your responses you should see two main things:
1) The optimum response time / number of users before the service degrades
2) The tipping point i.e. at what point you start returning 503's etc
Now you'll have enough data to scale your site or to start making performance improvements from a code point of view.