Undelete App to find accidentally deleted activity

It wouldn't be so bad from a user's POV, but I'm thinking more of the dev/business side.

You'd be shocked how long it takes to fully complete a "five-minute" feature IRL. It might be five minutes to write the code, and 5 weeks (*) to have meetings, decide on acceptance criteria, test, etc. (* A bit of an exaggeration but not too far off).

And after all of that, there might still be bugs. We've all seen various bugs in Garmin products, especially with new watches. (All products have bugs of course, but the point is that every new feature brings the potential for new bugs.)

A simpler answer may be a two step delete.

When delete is selected, the user is prompted with "are you sure you want to delete this? (yes/no)"

it would be much harder to accidently delete something.

But we already have a confirmation prompt for "Discard Activity", which is what half of this discussion is about.

We've all seen that with touchscreen watches like 630 and VA3, rain can trigger both the initial discard and the confirmation prompt.

For touchscreen watches I would make confirmation a gesture like swipe which is hard to trigger accidentally, if it isn't already.

flowstate said:

You'd be shocked how long it takes to fully complete a "five-minute" feature IRL. I

No, I would not be shocked. It's my life.

I suspect that one reason there are "so many" bugs is because the software isn't "modern". I suspect the code base is really old ("brittle") and written when space was at a severe premium. If that's the case, they might have to change unrelated stuff to add/fix features in other places.

flowstate said:

We've all seen that with touchscreen watches like 630 and VA3, rain can trigger both the initial discard and the confirmation prompt.

One of the reasons I prefer buttons.

jim_m_58 said:

One of the reasons I prefer buttons.

Same. Pretty hilarious to see the VA3 reduced to 1 physical button, and the VA4 come back with 2 buttons as Garmin realized its mistake.

I totally agree with you, except I'd say space is still at a premium. Even with modern non-music/non-mapping Garmin watches, data fields still have a measly 32KB of available RAM.

I'd agree that there's probably a lot of design issues with Garmin's stuff, and I'd guess it has to do with both the age of the codebase and lack of resources. I can empathize because I've worked at places where I wanted to change literally everything but there wasn't the political will nor the technical resources to do so.

I do appreciate the baby steps taken to try to modernize things, like moving from Eclipse to VS Code.

The space for IQ apps is a different thing (but it might be related).

It's not just "the age of the codebase and lack of resources".

There isn't any company doing what Garmin does with their watches (the other devices are really just watches in a bigger size).

The thing that comes nearest is the Karoo (which is basically just a small Android phone).

I don't think it's possible (yet) to have the same functionality in an Apple or Android watch.

flowstate said:

To be fair Discard is at the very end of the list.

for me it's actually at the beginning of the list as I have to press twice the up key to get to the recovery hr menu ;)