Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Better feedback when closing a feature request

Replies are disabled for this topic. Start a new one or visit our Help Center.

I'm checking most of the requests related to Blaze (features, reported bugs) in the forum since I own the Blaze.
Most of them are quite good described (and explained why it is requested) and are really simple to implement.
Of course most of them is closed as not planned, not mather how many votes got (also with votes more than 500).

I'm not completly sure but it looks that there was less then 6 requests fullfilled.

I think it would be nice and friendly to get better explanation why the feature request was not planned.

 

Best Answer
0 Votes
1 REPLY 1

Examples:

1) Set the time on blaze without needing an internet connection. I can set the alarm but not the time. So the alarm is useless, the clock face is useless.

 

2) Set the brightness in more steps then it is now or lover the minimum brightness.

 

3) Customizing colors of the clock face.

 

4) More flexible time range for daily goals

 

5) Better (smarter) HR monitoring

 

6) Options for Screen-off

 

7) Show battery status in percents.

 

😎 Assign more functions to HW buttons

 

9) Customize which screens to show in the menu.

 

etc.

Best Answer
0 Votes