Comments, questions and suggestions for Night-clock app
5 views
Skip to first unread message
Sparks
Feb 26, 2024, 10:41:18 AM2/26/24
to night...@googlegroups.com
Hello,
I like the Night-clock (or is it Nightdream?) app a lot and I have the following questions and comments about it:
Picture display order: By far, the biggest problem for me is the order/algorithm for displaying the background pictures. It seems to be random, which would be ok if at least it was non-repeat. But as it is, there seems to be an enormous "biais" in the picture selection so that some pictures are displayed much more often than others. Some pictures even re-appear after 2 or even 1 other pict, while others are almost never seen. This is really bad in my opinion. A non-repeat random order would be a major improvement. Also displaying the pictures strictly sequentially, would allow for some kind of story telling option. My impression is that sequential (by file name for ex) should be easy to implement (?)
An IOS version would be nice: this is for personal reason because my iPad display is better quality than my Android one.
Move clock constantly: currently the clock moves only sometimes during picture change. For pictures of people, I think it would be better to move the clock/weather info constantly
Shorter image change time: when you have a lot of images to display, having a minimum 15 seconds wait between each is too much in my opinion. 5 seconds would make more sense to me...
Show calendar events: on special days of the calendar (xmas, birthdays, etc) I think it would be great if the app displayed the appropriate message. It could be simply the calendar entry title. To me this would be significantly more useful than the RSS ticker or the radio.
Automatic brightness mode: I don't understand this feature. Where is it ? It does not show up on my version. Is it related to the Android setting called Adaptive brightness? Or only some versions of the app have it.
That being said, I do love the app but I just think it could be improved with some of these features that don't seem very difficult to implement (but I know nothing about the implementation part)
Thanks
Sparks
I like the Night-clock (or is it Nightdream?) app a lot and I have the following questions and comments about it:
Picture display order: By far, the biggest problem for me is the order/algorithm for displaying the background pictures. It seems to be random, which would be ok if at least it was non-repeat. But as it is, there seems to be an enormous "biais" in the picture selection so that some pictures are displayed much more often than others. Some pictures even re-appear after 2 or even 1 other pict, while others are almost never seen. This is really bad in my opinion. A non-repeat random order would be a major improvement. Also displaying the pictures strictly sequentially, would allow for some kind of story telling option. My impression is that sequential (by file name for ex) should be easy to implement (?)
An IOS version would be nice: this is for personal reason because my iPad display is better quality than my Android one.
Move clock constantly: currently the clock moves only sometimes during picture change. For pictures of people, I think it would be better to move the clock/weather info constantly
Shorter image change time: when you have a lot of images to display, having a minimum 15 seconds wait between each is too much in my opinion. 5 seconds would make more sense to me...
Show calendar events: on special days of the calendar (xmas, birthdays, etc) I think it would be great if the app displayed the appropriate message. It could be simply the calendar entry title. To me this would be significantly more useful than the RSS ticker or the radio.
Automatic brightness mode: I don't understand this feature. Where is it ? It does not show up on my version. Is it related to the Android setting called Adaptive brightness? Or only some versions of the app have it.
That being said, I do love the app but I just think it could be improved with some of these features that don't seem very difficult to implement (but I know nothing about the implementation part)
Thanks
Sparks
Reply all
Reply to author
Forward
0 new messages