iOS Shortcuts (notifications, quiet time, watch prefs, launch app) by asyba · Pull Request #119 · coredevices/mobileapp

asyba · 2026-02-15T04:15:14Z

iOS support for Shortcuts.
Some possible actions that could be used, for example using Focus modes.

I also added some classes but not implement, to support the equivalent in Android in the future using the Tasker plugin or others.

asyba · 2026-02-15T04:16:13Z

    single { CoreConfigHolder(defaultValue = CoreConfig(), get(), get()) }
    single { CoreConfigFlow(get<CoreConfigHolder>().config) }
    singleOf(::ModelManager)
+    singleOf(::CactusTranscriptionService)


I have to add this because it was crashing the app when installing, maybe its a bug not yet discovered.

cc @crc-32 - I guess this is in experimentalmodule, but references from common code?

asyba · 2026-02-15T13:58:34Z

cc @sjp4

ericmigi · 2026-02-15T20:42:53Z

really cool! Really useful

saltedlolly · 2026-02-15T21:38:04Z

Awesome. I was hoping for Shortcuts support at some point! Thanks for adding it!

Would it be possible to add a timeline pin from a shortcut?

asyba · 2026-02-16T04:01:49Z

Added timeline shortcuts
thanks @saltedlolly good idea.

saltedlolly · 2026-02-16T10:58:15Z

Thanks for adding Timeline support. I can't wait to try this out.

A couple more Shortcut ideas:

Get Watch Battery level (%)
Set Motion Backlight (enabled/disabled)
Get Watch Details (watch model, firmware version, serial number, uptime.
Get Watch screenshot
Set Watch alarm (not sure if this would be possible)
Set Watch timer (also not sure if possible)
Get step count

asyba · 2026-02-16T13:42:14Z

@saltedlolly I'm interested to know what you would use these cases in a real-life situation.
Battery level, Watch Details, step count. Most of them you can see it in the mobile app.

saltedlolly · 2026-02-16T15:24:17Z

@asyba Off the top of my head...

For battery life, perhaps you want to chart battery usage over time with a shortcut that runs ever few hours and logs the current battery to a Google Sheet. Useful to keep track of how battery life deteriorates over time.

For Motion backlight, you could have a shortcut that disables the motion back light at certain times of day, or over night. Or when battery gets low. (by running a Shortcut ever 6 hours, that checks the battery first, and then performs other actions if the battery is low)

Get watch details, could be useful to identify which of your Pebble watches you are currently using, before running the rest of a Shortcut. It would make it possible to run a shortcut on a particular watch only. (if you own more than one Pebble watch)

Get screenshot. Perhaps you want to capture regular data from a particular app each day, or create a tiled image of all the watchfaces you have installed, by screenshotting each of them.

Set alarm/timer on watch, there are loads of potential use cases, too many to list. I'm sure you can think of some!

Get step count. Ideally, you would want to be able to query the total step count for a particular day (e.g. yesterday), as well as the current running count for today, so far. You could use this to log your daily step count to some external source. Perhaps to a spreadsheet or journal app like DayOne.

Just some ideas.

asyba · 2026-02-17T15:08:10Z

did some refactor and added: battery, backlight, watch name, screenshot and step count.
For alarm/timer is not possible I think, maybe in the future when more "Index" code is added can be done.
cc @saltedlolly

saltedlolly · 2026-02-17T15:21:04Z

@asyba This is amazing. Thanks for adding it.

My only request concerns the health stats.

Would it be possible to query the total_steps_yesterday, or better yet include a date input with the query (default to today), to get the step count for a specific day? This way you could run a daily query to log your daily step count to a Google Sheet or something. That would really useful.

And perhaps the same for sleep duration, sleep start, and sleep end. Querying the latest values from last night/this morning. Or querying for a specific date?

If you want to keep a log of this stuff over time, it would be really useful.

ericmigi · 2026-02-17T18:23:28Z

that will be better exposed as a health API, which is in progress

sjp4

General questions:

Should these be documented as an "API", or is that not really shortcuts work?
Should they always be enabled, or would users want to enable/disable access to this stuff?

sjp4 · 2026-02-28T21:49:31Z

+}
+
+@available(iOS 16.0, *)
+struct PebbleShortcutsProvider: AppShortcutsProvider {


Does this code need to be in swift, or was it just easier to to write in swift? Our policy is basically that it should be in kotlin unless the only way to do it is in swift (or to put it another way, as much in kotlin as is possible). I don't have much context on how shortcuts work (or the ability to thoroughly review swift code), so any context would be useful

No, is not possible to do it with kotlin, its specific swift.
I improve it by moving some methods/code to kotlin but this is as much that can be done.

in this section func perform() is wheere each shorcut action calls kotlin code (IOSDelegateShortcuts.shared).

sjp4 · 2026-02-28T21:56:37Z

+        /**
+         * Returns the [RemoteTimelineEmulator] from the LibPebble Koin context.
+         */
+        fun getRemoteTimelineEmulator(): RemoteTimelineEmulator = koin.get()


RemoteTimelineemulator shouldn't be exposed like this (it's internal to libpebble) - we should add new methods to the libpebble API (probably here) if the ones already exposed don't do the job

done, found another way. thanks

sjp4 · 2026-02-28T22:37:26Z

+ * For now these are placeholders (no-op) but provide a clear extension point
+ * for future integrations (e.g. Tasker plugin, Android Shortcuts, etc.).
+ */
+class AndroidPebbleAppActions(


If we add anything similar on android it will be part of PebbleKit 2.0, so I think it's unlikely we'd re-use this interface directly. That being said, i'm thinking it's probably best to keep it entirely within the iosMain code tree for now (i.e. no androidMain implementations needed)

okay. I removed the androidMain implementations, there are still commonMain files let me know if those should be move to iosMain tree.

I think we should move those to iosMain

asyba · 2026-03-01T14:07:29Z

@sjp4

No, they don't need to be documented as APIs. You define (PebbleShortcuts.swift) actions like forms, toggles, etc., and present them in a way that can only be used from the operating system's app shortcuts. You can combine them with other shortcuts from third-party applications or the system itself, and then it offers options to execute them as an icon, share action, automatic trigger, etc. It doesn't let you do anything that isn't documented in that structure.
According to the AppIntent documentation, configurations that determine the visibility of an intent are explicitly defined as static var (isDiscoverable).
Because the Shortcuts app extracts these metadata at install/compile time statically, we cannot dynamically hide or show the intents from preferences.
However, we could add a toggle in the settings, to prevent the execution of the shortcuts (throwing an error or showing a dialog), but still this intents are show as possible in the apple iOS Shortcuts.

asyba · 2026-03-24T15:45:49Z

@sjp4 ready for re-review

asyba commented Feb 15, 2026

View reviewed changes

asyba force-pushed the ios-shortcuts-actions branch from d37f592 to 9372109 Compare February 15, 2026 04:30

asyba force-pushed the ios-shortcuts-actions branch from 9372109 to 1185084 Compare February 16, 2026 03:23

asyba force-pushed the ios-shortcuts-actions branch from 1185084 to 1cf01d6 Compare February 17, 2026 14:05

iOS Shortcuts (notifications, quiet time, watch prefs, launch app)

a70c101

asyba force-pushed the ios-shortcuts-actions branch from 1cf01d6 to a70c101 Compare February 17, 2026 14:45

saltedlolly mentioned this pull request Feb 18, 2026

New Icons: Apple Shortcuts pebble-dev/iconography#62

Merged

sjp4 reviewed Feb 28, 2026

View reviewed changes

asyba force-pushed the ios-shortcuts-actions branch 6 times, most recently from 9e46fc9 to 73dda83 Compare March 1, 2026 21:59

asyba requested a review from sjp4 March 1, 2026 22:10

iOS Shortcuts (notifications, quiet time, watch prefs, launch app)

5ed81f7

asyba force-pushed the ios-shortcuts-actions branch from 73dda83 to 5ed81f7 Compare March 24, 2026 15:22

sjp4 approved these changes Mar 26, 2026

View reviewed changes

sjp4 merged commit ac55f0b into coredevices:master Mar 26, 2026
3 checks passed

Conversation

asyba commented Feb 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

asyba commented Feb 15, 2026

Uh oh!

ericmigi commented Feb 15, 2026

Uh oh!

saltedlolly commented Feb 15, 2026

Uh oh!

asyba commented Feb 16, 2026

Uh oh!

saltedlolly commented Feb 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

asyba commented Feb 16, 2026

Uh oh!

saltedlolly commented Feb 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

asyba commented Feb 17, 2026

Uh oh!

saltedlolly commented Feb 17, 2026

Uh oh!

ericmigi commented Feb 17, 2026

Uh oh!

sjp4 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

asyba commented Mar 1, 2026

Uh oh!

asyba commented Mar 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

saltedlolly commented Feb 16, 2026 •

edited

Loading

saltedlolly commented Feb 16, 2026 •

edited

Loading