Android Wear – Bits watch face… simply amazing

I have downloaded and enjoyed several watch faces. It’s fun to accessorize, match my watch to my shirt, etc (something that is really weird for me to say). Beyond the fashion aspect is the functionality, and how the utility helps me be more efficient in day to day work.

Bits watch face
Bits watch face

The new Android Wear software rolled out recently, and wow is it great.

On the topic of this specific watch face, it was great before the update. It allows you to choose up to 6 circular widgets that circle around the middle watch widget. They give you the option to change what widgets show. You can show up to 6, but if you show only 3, it will show you more information about that widget. For instance, if you choose battery, weather and date, it will show an image of the weather condition and battery image + percentage.

Tap for more info
Tap for more info

If you decide you want all 6 widgets (which I like), as of the new update, you can click on each widget to expand them to fill the screen and give you more information about that widget. Simply put, it is AWESOME!

The watch face itself just had an update to its styles as well. Before it had the option to have a black background and 4 or 5 colors to highlight the widgets or a colored background with black or white borders around the widgets; this is call ‘Utilitarian’ design.

Now it gives you that, plus two different background designs to make the face extra funky!

I usually switch my watch faces frequently, but have been quite stuck on this one for some time now.

Download the watch face today, it rocks!


Can We or Should We?

Having worked with developers for years if you ask them “Can we make the product or application do ‘so and so’ (hereafter referred to as ‘xyz’)?”  The answer is almost always “YES”.  However, if the question is “Should we do xyz?”  The answer is sometimes “No”.


Let me explain.  Let’s say a sales person is talking with a potential customer and is asked “Does it do xyz?” They are merely inquiring about the features or possibly looking for an excuse for not buying the product.  The salesperson rushes back with a “We have got to have xyz!”.  It does not mean that this customer (or indeed any customer) will purchase the product.

Here is where the “Should We” question should be asked.

  1. Is the proposed change mutually exclusive with any other feature the product currently provides? If so, you might be upsetting or losing an existing customer. I have seen cases where xyz was implemented disrupting the current client base.  When the developers are brought in to ‘fix it’ they said “we implemented xyz, we thought that is what you wanted”
  2. Will the proposed change really bring in additional business?
  3. Will it impact system capacity?
  4. If there are no negative impacts by adding this as an option, you should consider making the change.
  5. But lastly, don’t just Do It because it can be done.