I agree (regarding a Tasker plugin)! That could be a brilliant move, and save ManicTime from having to code all sorts of extra things (because could just let Tasker handle a lot of it).

First there is battery usage, then there is the data. We made a test app, but I didn't find the data all that useful. It would probably be better if I had a work phone, so I know its purely for work stuff. A lot of the data is ... 10 seconds reading email, then later 10 seconds reading SMS, later 1 minute checking directions...5 seconds checking the time, 30 seconds checking game score...
It helps to remember what you were doing in some cases, but other than that we (I in this case :)) have so much of phone interaction during the day that after a while I never looked at all the small phone interactions.

We could combine the stopwatch with location, like start this tag when I am at location X. I think that might be a good extension of the pure stopwatch feature.

A tasker plugin (as suggested before) would be a jackpot :)

Okay, that's clarifying.

And I can understand regarding the tracking difficulties--it all works a lot different within Android versus in Windows (where I perceive it is a lot easier to tell when an application is actually active, being used). For those that want app tracking, perhaps exploring a selective app tracking (as was mentioned below by others) would be useful.

But I totally agree--start with the Stopwatch and go from there. People may not need total app tracking--the Stopwatch could be sufficient (you'll know more once folks start using it and giving feedback). I know that one of the downsides to tracking all apps is that is going to use more battery (it's impossible for it not to), which is another reason selective tracking and/or just using the Stopwatch is advantageous.

When you build the Stopwatch functionality, I highly recommend that the Stopwatch add an icon and listing to the Notification area/drawer, both to remind the user that the Stopwatch is running, and also to provide easy access. Perhaps there can be multiple icons as well: one icon for when the Stopwatch is running, another for when paused, and another for when stopped (but Stopwatch is still available in background and via Notification area).

Correct, currently it only tracks phone calls. And tracks is not correct word, it only sends call log to MT Server.
We tried a few things, tracking was one of them. We can get some information easily, but its not so simple to get it working on all the different android systems.
We will see.
First we will definitely add a stopwatch and we will take it from there.

Oh, so then does ManicTime Android only track Phone Calls (and not track time spent in apps)? For my purposes, the Stopwatch is what I'm most interested in anyway, so I can probably live without app tracking. But I had been assuming ManicTime Android would track app usage, similar to RescueTime, and it seems others were expecting that (or some version of that) as well.

I think all "calls" references should mean phone calls. We will fix it so it reads phone calls everywhere.

Awesome! :) And sounds good regarding (1) and (2). Unfortunately I personally won't be able to do anything with the Android version until (2) gets implemented (due to my network setup, which is for security reasons). But I understand and agree with the order of events you're suggesting--they make sense from a development perspective.

You know, once you implement (2) for Android and the Server, you could then add that feature to the Desktop version as well, which would enable for more creative setups (eg, being remote, without access to the Server network). I personally don't need that at the moment, but I could see it being useful to folks.

One question and possible suggestion from looking at the thumbnails on Google Play: When it talks about "sending new calls to server", "call data", etc. is that referring to Phone Calls, or to "call" in the technical sense (as in, a way of describing sending data to the server)? I am guessing you may just be using it in the technical sense, and if so, you might want to change to differently terminology, as the average user is going to think you mean phone calls, which will cause unnecessary confusion. My assumption is that the ManicTime Android app tracks which Android apps are used and how much, similar to the Desktop version.

I published it.
https://play.google.com/store/apps/details?id=com.finkit.manictime

1. We will, but we will first release a new server, one which will support tagging on the server. Then we can also receive tags from other devices. I think this should be done this month, at least to a beta stage.
2. Interesting, I think we could add this. But first the stopwatch.

I'm excited that a version for Android is in development, but that the beta, or "testing", app is no longer available (I signed up to become a tester, but the link on that page no longer goes to the app).

Regardless, I wanted to suggest a few things:
1) Definitely include a Stopwatch (similar to Desktop).
2) It would be super-helpful if we could use things like Dropbox, SugarSync, OneDrive, etc. as an intermediary for sending data to (or from) ManicTime Server. In my particular case, ManicTime Server is not going to be accessible to mobile devices via wifi (for security reasons for the machine it is installed on). But if we could designate a folder within the syncing service of our choice to be used to transmit data then ManicTime Android could still send data to ManicTime Server, without having to be on the same network (obviously ManicTime Server would need to be configured to look in the proper synced folder on the local machine).

Thanks for considering everyone's ideas and suggestions! :)

We have a first version for Android. For now it will only sync the calls to ManicTime Server. Then you can import them as a timeline in ManicTime.

https://play.google.com/apps/testing/com.finkit.manictime

Another vote for android. It would be fine with me if I just select specific processes for tracking (rather than tracking all processes). A few things to consider when building are android devices with multiple user accounts, android devices that run splitscreen windows (samsung devices), android tablets (vs. phones), and GPS logging. Another commenter suggested a tasker plugin which is a good idea too.

I would love for the Android app to have a Tasker plug-in. This would allow people to track things they may not necessarily involve them directly using their phone. One example: using Tasker they could time how long they spend at Work Site A and how much time at Work Site B. Tasker can start/stop a timer when you enter/exit the Work Site. Another example would be to see how much time was spent driving in your car.

Having manictime on mobile could be great.
My point of view is that it should be as simple as possible.
Maybe only phone / calls and emails activity should be logged.
Having the Start / Stop button is essential.
Being connected to a Manic Time Server seems to me essential.
Once published to the server, the Mobile Activity should be displayed in a new Mobile TimeLine on the Manic Time Client.
Mobile Tags should be identified in the Main Tag Timeline so It could be easy to manage conflicts between Tags from Pc or Mobile activities.

+1 for an android version. I would absolutely consider upgrading my manictimes to a premium version.

Logging calls would be great (although I already can import my mobile (land line, too) calls to a timeline using a custom timelane: android -> csv -> php -> mysql -> php -> manictime), plus listing the webpages that were displayed (I don't know if this is possible), and emails read and written (I'm using K9Mail and I don't know if this is possible).
Also, I watch the server status with PSIAndroid - logging this would be cool, too.

I don't have anything against Android application, but I can't really imagine how it should work. It should track something? Or just view data from MT server? Or anything else? 99% of my work is done on desktop PC.

We are actually working on Android. Do you have any idea what you would like to see in the app? Which data to track?

Or a connection to a third party mobile app, like the "Moves" connection...

I voted for this, and I'm specifically looking at Android.