Possibility to close/dismiss NC more quickly?

[machinaeZER0]

In the current app, backing out triggers a "closing" screen - would it be possible to have whatever is going on at this point happen silently in the backend, so that the return to our watchface is that much faster?

Really no idea if this is possible, but figured it wouldn't hurt to ask! I've already forgotten how the legacy app approached this

[matejdro]

This is close to last app feature: If you have an app open on the watch (let's say, Timer) and you receive a notification, after closing NC, you will go back to that previous app. Without that, NC will always close back to the watchface, which is annoying as you will loose your context due to the interrupting notification.

It works by phone re-starting previous app, so there is no way to do this "silently in the background".

I could add in an option to disable this feature, but I'm wondering if it's worth it. Does the closing screen take a long time for you? For me it's almost always less than half a second.

[machinaeZER0]

That makes sense. Is it possible for NC to check whether there actually was a previous app that needs to be re-started, and use that to determine whether that process is needed? Hypothetically that feels like it would be the best of both worlds, but if not then your reasoning/implementation seems like a good one!

[matejdro]

It is possible to check, but, again I'm wondering if the extra effort is necessary. How long does the closing take for you?

[machinaeZER0]

About a second each time. If you don't think it's important you can close.

[ItsHarper]

It is possible to check, but, again I'm wondering if the extra effort is necessary. How long does the closing take for you?

Long enough to feel a little tinge of frustration every time (not complaining, just sharing my experience)