Didn’t know about Cranko! Ordered my copy. Keep up the great work!
Heiko Behrens
Creator of
Recent community posts
Those devlog updates are always a highlight for me, thank you so much for so many detailed insights!
Your paragraph about the hassle of trial and error when iterating on animations inspired me to work on a tool during our last company hackathon: With Playdate AntiMirror you can at least stream and review in real-time your desktop content on the Playdate. It's not quite the animation engine you were describing (I am thinking if "Rive for Playdate"), but I hope this is of some value for you!
Nice find, thank you for reporting! I have ideas how it came to it and how to address it, but proofing that it was fixed will be time-consuming 🪫
EDIT: hopefully fixed with as part of rework of screen updates for button support.
I just uploaded a new version with the following changes:
- 🆕 no more autolock of the screen for watchfaces (currently, Intrinsic Gravelty will lock. Later, games will too)
- ↗️ various power optimizations so that rendering (or processing for Pebble apps) only happens when a watchface needs to update (e.g. once per minute/second depending on their use of TickTimerService)
- 🆕: correctly propagate Playdate's battery level and 12h/24h clock mode to the corresponding Pebble APIs
- Note: while Pebble's BatteryStateService would allow watchfaces to show charge + plug state, Playdate's equivalent API is seemingly only available for Lua apps. I created a request on the DevForm about this.
EDIT: It seems as if the battery will still not last for even 24h despite my efforts to reduce the refresh rate to 1.0 FPS doing minimal logic only and no redraws. I will try to optimize further, but right now you can only use this as a desk clock when also connected to power.
Great feedback, thank you! Yes, using Playdate as a desktop/night stand when showing Pebble watchfaces is certainly something I would like to support – ideally even with the upcoming https://play.date/stereo-dock/.
The SDK certainly allows for this, but right now, Gossan refreshes unconditionally at 30FPS and would burn through its battery in no time. I captured this in my backlog and will distinguish between interactive apps (aka games) and passive experiences (watchfaces and demos).
