Apps for Android and Windows 10 Mobile
I think I would like some integration or assistance with using MT with IFTTT, think there could be some real merits.
I'd just like to be able to tag my time for the day from my windows computer through my phone when I get home. Is there a way to do that already?
and iOS. ManicTime is great but on desktop alone i spend way too much of my time doing tracking and not enough doing work
Been thinking about this a lot since I made by last two comments :)
What about using NFC tags? They are cheaply available and can be used as anchor points to automatically take the guesswork out of where we are. Obviously not everyone is going to use them - but they are becoming more popular.
I often see gaps in my Manic Time and wonder what I was doing. Sometimes I have to run out and I'm driving. Other times its a bathroom break.. but I can't tell for sure. GPS would help with the driving, but what about in the house? That's where these NFC "anchors" would solve the problem.
So lets say I buy five flat adhesive NFC tags. I easily program them with a free app on my phone. I program the tags as URLs representing the five places I spend my time.
So when I'm in any of those places, I simply set my phone down on the NFC mat, and manictime now knows definitively where I am, and I can determine what I was doing and for how long.
From a programming perspective, you'd want to tap into the accelerometer events - no need to use up the battery. When the accelerometer suddenly stops or slows - you flip on the NFC and scan for a tag for 30 seconds. After reading a tag or timing out, the monitoring process goes to sleep until the next accelerometer event fires.
Also - if you make an Android application - try not to use Google Services, or write in the ability to turn them off. By doing that - you've just made your app usable by all Blackberry 10 users :)
As mentioned, tracking how long we're on the phone and which numbers, and whether its outbound or inbound would also be quite useful.
I would also like it to keep track of when the phone is asleep, and if it wakes up, for how long.
Also, similar to the documents in ManicTime - have the ability to take "screenshots" throughout the day .. "record a 10 second audio clip every 30 mins", "make a record of all of the bluetooth and wifi devices currently detected" "make a record of all access points in the area, or which one we're connected to" "use the audio to determine if its a noisy environment we're in or if its quiet" "use the camera sensor to detect if its bright or dark where we are" All little tidbits that could help us fill in the gaps later on as to what we were doing.
ManicMobile may be worthy of a separate application - but its "the other picture" of my life that I need tracked in the same way... I have given a lot of thought to what an application like this should look like. It should be able to detect if we're in a vehicle, walking, or bicycling. It should build "trips" for its autotagging - so the route we took is stored but more importantly - we were travelling from point A to point B. Time spent at Point A .. time spent at Point B. Places that we stop off at often, it should prompt us "what is this place?" and we can say "its work" .. "its home" ... etc. Same thing with frequent trips ... "Driving to/from home" ... "Driving to/from work" At the end of the day I want to see time spent travelling, and time spent at each location. Certain locations are billable. Certain locations are not. And of course - it should integrate in with ManicTime to show that I was outside and break it down into travel time and work time.
I bet that the applications, emails, phone calls, sms, Geo-tagging would be extremely useful. Having this all tracked and view the report would be fantastic for the remote users, who actually spend not much time @ office, but drive around the city.
the mobile clients should also be able to autotag according to available wifi networks(or at least accordingt to the connected wifi), same would be nice with phone cell ids. So you can automatically log that you where from time x to time z at client y.
I think those are all great suggestions. And I agree that having both START/STOP for Stopwatch, plus INSERT for basically creating a time record without using the Stopwatch, would be good.
And though I can't think at the moment of a usecase for the triggers/conditions (Stopwatch started, etc.), it is conceivable to me that they'd be helpful for some folks.
I know it might be to early for details, but it shouldn't hurt to write down some ideas (regarding the Tasker plugin):
I'd like it if one could not only start and stop a stopwatch, possibly with a tag ("START: %TAG" and "STOP: %TAG" with %TAG optional?), but insert tags into the timeline (INSERT: %TAG / %FROM / %TO).
%FROM and %TO could be optional if empty values default to the current time, in which case a stopwatch could be started / ended - which would render a separate START action obsolete.
The plugin could only provide actions (like above), but also triggers and conditions (Stopwatch started / stopped / toggled / currently active) - but I don't really know a usecase for that.
Excellent points regarding useful data--does one really need to know that level of minutia? I can imagine though that some might find the data in aggregate to be useful (ie, total time spent this week on SMS). But definitely better to wait and see if there's truly demand for that.
And Stopwatch with Tasker support should be pretty powerful for folks (for those who use Tasker). I think the location element could potentially even be handled by Tasker as well (eg, within Tasker configure start/stop of Stopwatch based on location).
I suppose actually that folks could potentially use Tasker to start/stop the Stopwatch (and assign certain Tags) based on certain apps (eg, when I use am using SMS, start Stopwatch and assign Tag "Texting", and stop Stopwatch on end of app usage). Might need to enable Tasker to start multiple Stopwatches though so that you don't run into collisions (and in that case, perhaps give the ability within the Tasker plugin to configure whether a given Tasker initiated Stopwatch should appear in the Notification area, or be only in the background).
So first we add a stopwatch, with Tasker support, then we take it from there. Agreed.
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.