The smartwatch "revolution" didn't happened as expected by the industry.
The sales numbers tells that Samsung, Google or Apple have conviced enough people.
Smartwatchesare perceived like new toys, instead of useful things and, often the disadavantages of having one are more than the advantages:
- ridiculous battery life
- no killer apps
- ridiculous apps (sending hearths or drawing to someone...)
and they are also expensive.
(Another interesting review from engadget about apple watch one year on)
With a lot of skepticism, last year I decided to buy one, just to understand the potential of these devices in everyday life.
Since, I found frustrating to charge my watch every night, I decided to become a bacher of the new pebble time, because it guarantees (in some conditions) 7 days of battery life, display always on, waterproof, and imho it is designed as a watch first, instead of a wrist-phone.
I'm not a typical smartwatch user.. not the one for who a smartwatch is designed for.
A smartwatch is useful if it can cover some microtasks related to "TIME" like:
- calendar notification
- alarms
and it is important that if it can work most of the time without the dependency from the smartphone.
I don't care about app notifications, neither of app integration.
I like the possibility to develop my own apps and expand watch functionality with apps.
BTW, an honorable mention is for the stock Health app, it tracks my daily sleep and daily steps: it is an addictive functionality and useful.
I use the smartwatch also in the sea, during surf sessions and this is a plus, because I can leave my phone inside the bag on the beach and receive call notifications.
Watchfaces are a nice idea, to change the look to the device but, you have to choose wise if you want to preserve battery life, because some "cool" watch faces can drain your battery faster.
Developing a WatchApp: "Work Time"
One thing I do when I arrive at work, it is to keep track of the arrival time: in order to calculate when I can leave the office.
This is a repetitive task and it can easily covered by my pebble!
I developed an app "Work Time" that vibrates when it is time to go home.
Create an app for a limited device it is an interesting challenge: inputs, cpu, memory, screen are limited.
Work Time is composed by these screens:
- Estimated Exit: It show you at what time you can leave
The app is configured using these 3 screens in sequence:
- Check In: the time of the arrival. Default is the current time.
- Work Time: how much time you work
- Break : how much time is your break
When your settings are done, you can close worktime, it will notify you with a vibration when you can go home and a screen like this one:
The pebble documentation is better than other platform I developed for... but creates a watchapp for pebble is not that easy due to:
- small community around the subject
- hard debugging: logs based
- cloud.pebble.com: online based editor and sdk.. sometimes it is a limit
- C language: good for optimization, bad for complexity
Btw, if you are interested, the code for WorkTime is here: https://github.com/crazycoder1999/worktime
Showing posts with label github. Show all posts
Showing posts with label github. Show all posts
Thursday, 28 April 2016
One Year with Pebble (Time): a user and a developer perspective
Friday, 5 July 2013
YourPhoneAsHomeConsole opensource on github
I've found some time, to check a little bit the code of my last hack: Putting a WebServer Inside a Phone (why? http://pestohacks.blogspot.it/2013/03/putting-webserver-inside-phone.html ).
The code is now OpenSource and Downloadable ON GitHub
This version runs on BlackBerry Z10, it is just a proof of concept.
It is based on mongoose and jawsjs.
After launched the app:
The code is now OpenSource and Downloadable ON GitHub
This version runs on BlackBerry Z10, it is just a proof of concept.
It is based on mongoose and jawsjs.
After launched the app:
- your phone and your pc should stay in the same LAN
- you have to open the browser (chrome is better) from the pc and connect to the phone http://SmartphoneIP:8080
- play space invaders using your phone as a pad :)
Labels:
bbos10,
blackberry,
github,
mongoose,
mongoose.,
opensource,
websockets
Tuesday, 4 September 2012
Tethering indicator... on github!
Ok!
First Alpha of Tethering Indicator is out!
It is not perfect.. and a little buggy.. but it works... need improvements and the main ingredient of all good application... TIME!
So for now I will stop to develop it , but I have commited the code on github .. so anyone that wants to try it ... can test it, improve it and change it :)
I'm not so good with osx development (I'm a bit new) so I hope that someone will change and fix the code... so I can learn something too :)
I'm not leaving the project, I've just want to develop something different for the next month
I will publish update everytime I can!
First Alpha of Tethering Indicator is out!
The client application on mac... as you can see the connection of the phone was 2G :/
It is not perfect.. and a little buggy.. but it works... need improvements and the main ingredient of all good application... TIME!
So for now I will stop to develop it , but I have commited the code on github .. so anyone that wants to try it ... can test it, improve it and change it :)
I'm not so good with osx development (I'm a bit new) so I hope that someone will change and fix the code... so I can learn something too :)
I'm not leaving the project, I've just want to develop something different for the next month
I will publish update everytime I can!
GITHUB TETHERING INDICATOR
Other post about tetheringindicator here
Subscribe to:
Posts (Atom)