[1] https://github.com/hamaluik/timecop [2] https://www.youtube.com/watch?v=oI2aMKwXXnE
1,400 karma · joined August 16, 2018
[1] https://github.com/hamaluik/timecop [2] https://www.youtube.com/watch?v=oI2aMKwXXnE
If you would like a promo code you can email me and I’ll get you sorted.
I’ll play around with your other suggestions but not sure if I’ll keep them (but thank you for them!). I had fiddled with how things worked and settled on where it is now because it felt the most intuitive to myself. For example when I had the running timers in the main list itself I found it easy to forget that I had a timer running. Grouping all running timers in one spot helped cut that down without too much fuss otherwise.
Thanks for the feedback!
I use it at work for recording when I'm in meetings, when I'm actively developing, when I've researching, etc—things that I need to report but don't want to manually write down and things that aren't captured by things like screentime. I always have my phone with me and handy, whereas I don't always have my computer with my nor handy.
Once I can figure out how to make one of those step-by-step walk-through tutorials I'll definitely add that to the app, because that functionality has absolutely 0 discoverability.
I think its killer features are the cross-platform support by default and the hot-reload—I found the hot-reload functionality so invaluable that I ended up jerry-rigging hot-reload into my current product at work.
You're right that it is definitely still rough in some places though. The libraries on pub.dev can be very hit-or-miss, and I definitely wasted some time trying various libraries from there before either giving up or rolling my functionality.
I too explored a mapping project using it a year or two ago now and ended up having to essentially create my own map view using mapbox APIs (unfortunately I don't have code that I can share from that project). That said, I find Flutter is at least relatively easy enough to implement things that you can't find from the ecosystem.