A Google user
- Flag inappropriate
- Show review history
Love this floating clock. Exactly what I needed. Customizable. Simple. Perfect!!! (Suggestion : maybe have option to do a background color instead of transparent by choice ?) Personally would love to have a solid black background, that's size is also adjustable independent of the time. Using on android phone, works 110% !!!!
4 people found this review helpful
Ronald Davis
It works, but adjusting the position to use with different other apps is extremely slow. It takes 2 1/2 minutes to move from top to bottom of the screen. "Keep the button pressed to go faster" doesn't work. Also, the optional outline is too thin to assist visibility against different backgrounds, with no option to adjust the thickness of the outline. The analog clock is drawn with lines too thin to see, and again no adjustment provided.
Shibby Entertainment
11 April 2024
Thanks for the feedback 👍 The app was written about 10 years ago when FullHD resolution was still the norm. It's no excuse but just an explanation of why things are the way they are 🙂 The analog clock was only a fun experiment. Since privacy / security policies get stricter by the year, I've been wanting to rewrite the app, but fail to find time.
Zain Ajam
- Flag inappropriate
- Show review history
I really love this app and is the only one of its kind to allow me access to the time at all times when watching TV. I've used this for many years. Started off using it on an android tv boxes in around 2013/2014 before official Android TV was a thing. Recently, the clock app has been crashing on my Nvidia Shield and the time just disappears and I have to relaunch the app to get the time back. Not sure what has changed in recent months.
2 people found this review helpful
Shibby Entertainment
17 July 2023
Hello, thanks for your feedback! I also have an Nvidia Shield TV and noticed too that recently the service gets killed. I have no idea why since neither the app nor the shield tv got updated, so current hypothesis is that play store policy is somehow killing it off on device scan or something :/ difficult to debug since it occurs very unpredictably