#Bringing back Dashboard in 2026

6 messages · Page 1 of 1 (latest)

wind edge
#

Way back in 2013 I wrote a Pebble watchapp called Data Toggle - it let you toggle phone WiFi and Mobile Data on/off to save power, which was something you had to do on Android back then. This evolved into Dashboard, which contained many more useful toggles and showed information on the phone like free disk space, operator info, battery level etc. It even used the Wakeup API to schedule events that could turn these toggles on and off automatically.

Sadly, in the years since, Google and Android have steadily clamped down on things Android apps can do, especially when in the background. I can understand this - a strong emphasis on security and permissions, and a lack of other use-cases that want to toggle WiFi or Hotspot without showing any UI. This means a lot of those require root, Device Admin, Accessibility settings etc to keep functioning. In fact, it's impossible to publish a new version to Google Play without upgrading the SDK level which breaks even more things! It has been open source and received a couple of contributions though.

But, given it was my favorite Pebble project at the time, I think it's time to try and bring it back! Probably not all of it, but enough to be useful. So, here's a roadmap:

  • ➡️ Investigate which features are still possible
  • ➡️ Re-learn Android dev (meaning Kotlin, modern standards etc)
  • ➡️ Build a minimal and functional prototype using PebbleKit Android 2
  • ➡️ Flesh out as much as possible with a lean and fast UI

I'll share progress here!

dim cipher
#

Holy peak

wind edge
#

Given that the two main toggles appear to now be impossible to be done from the background, I would temper expectations 👀

eager sorrel
#

Yeah I remember using it way back heart
I wouldn't mind device admin for an open source app.
Maybe you can make use of Shizuku, which enables system level API for regular apps

wind edge
#

Oh that looks interesting - seems to require users install another app. I wonder how much friction that would be.

gusty pumice
#

I use quite a few shizuku apps. You could potentially have optional support, where using shizuku would allow you to have extra things on the dashboard that wouldn't work otherwise, but if the user doesnt have it those options just aren't there

No idea if thats feasible for this use case though, Im not a developer, Ive just seen other apps use shizuku in that way