AddThis
Browser Stats
Browser Stats offer a more in depth look to the browsing habits on any Android device. Similar to all the other stats this section shows the totals first. In this case, its Total Visits and Total Searches. Visits By Url comes next and is probably the most processor intensive stat in StatDroid. These stats are collected by parsing and rendering every visit to a url. If you have visited Googles homepage 30 times, it will be shown here, along with any other page you have visited. Visits By Domain is the next menu item and is similar to the contacts email addresses by domain. This stat can give you a general insight as to which sites get visited most.Next on the list is Unique Visits By Date. This stat will show you how many unique pages have been visited for a given date. If you visit only one page 30 times, it will register as a 1 for that date. However, if you visit 30 different pages once, this will show as a 30 for that date. This stat will let you know the breadth of your browser activity.
The searches section in the Browser Stats, is similar to all the others stats, it allows you to view how many searches where done by Date, Day, and Time. This will inform you about when most searches are conducted.
The last menu item is Urls By Domain. This is an interesting stat about all the Urls stored in your browser (visited or not) and how many of them belong to a specific domain. You will notice that it will even includes the urls and domains that come pre-installed as bookmarks (CNN, FaceBook, Amazon, etc.).
From our studies, a search is only logged if the search button (magnifying glass) is pushed while running the browser application. We have tried the search button from other screens, but it doesn't get registered with the Android browser search log. We have also tried searching from Googles home page in side of the browser, which seems to be the end location when doing it with the search button. We will continue to look for documentation on this behavior and post the results when they are clear.
When looking at browser stats, we suggest that the "Minimum Value" in the results settings be set to 2 as there can be enormous amounts of data which will increase the render times of the data lists. We will be working towards some features to counter this in the near future. One of which will be automatic filters, which will be set automatically based on the data that has been received. We are also planning a simple progress bar. While we haven't seen any render times longer than 20 seconds (which is too long without any feedback or results), we will continue to optimize the responsiveness of the UI as much as possible. This is because we have a feeling that there are some devices with thousands of web pages visits.
When looking at browser stats, we suggest that the "Minimum Value" in the results settings be set to 2 as there can be enormous amounts of data which will increase the render times of the data lists. We will be working towards some features to counter this in the near future. One of which will be automatic filters, which will be set automatically based on the data that has been received. We are also planning a simple progress bar. While we haven't seen any render times longer than 20 seconds (which is too long without any feedback or results), we will continue to optimize the responsiveness of the UI as much as possible. This is because we have a feeling that there are some devices with thousands of web pages visits.