Updating settings form "Connect" or "Garmin express"

Also, it may be that by the time you do some other app types, you'll be more comfortable with app settings, and you'll have them in the app from the start, so when you add something new for the store, you'll just need that with "do not approve" until you checked things out, and not need a placeholder app for testing.

I use "do not approve" very rarely these days. Hvaing a bunch makes the list that "The Approver" longer and more to go through each time he's approving apps in the store.

One trick I'm not sure is used by many, is that while you can check out things like app settings in the sim, there another step you can take before you submit something to the store. When you have a sideload on the watch, you can generate a .set with the sim, and copy that .set to the watch to see how things look on the real device. I find this useful for things like colors, if I'm doing something like custom fonts, or if it needs an api key, has user specific settings, etc. The sim isn't bad at this kind of stuff, but somethings you may want to check out some user specific things when recording an activity and not playing one back in the sim, etc...

Also, it may be that by the time you do some other app types, you'll be more comfortable with app settings, and you'll have them in the app from the start, so when you add something new for the store, you'll just need that with "do not approve" until you checked things out, and not need a placeholder app for testing.

I use "do not approve" very rarely these days. Hvaing a bunch makes the list that "The Approver" longer and more to go through each time he's approving apps in the store.

One trick I'm not sure is used by many, is that while you can check out things like app settings in the sim, there another step you can take before you submit something to the store. When you have a sideload on the watch, you can generate a .set with the sim, and copy that .set to the watch to see how things look on the real device. I find this useful for things like colors, if I'm doing something like custom fonts, or if it needs an api key, has user specific settings, etc. The sim isn't bad at this kind of stuff, but somethings you may want to check out some user specific things when recording an activity and not playing one back in the sim, etc...

Yeah, I read about the copying .set to the watch...

But testing by continuously connecting the watch, waiting for it to appear on the pc, copy files, disconnect, wait for the battery-charge icon to go away, test... Rinse and repeat. It's quite time consuming and somehow I don't feel comfortable plugging in and out the watch 50 times an evening ;)

I indeed assume in time I just know how it works and won't make too many stupid mistakes anymore. But at the moment, sheesh. It's also pretty tricky that the ide and simulator are pretty forgiving, the watches are not. Spent like a day trying to determine a fault after I added a few lines of code (with properties and settings), only to find out I probably accidentely deleted part of a variable name somewhere after which the emulator ran fine, but the watch crashed.

Anyway... it's nice to have some area for playing around some more while getting more into all this.

Thanks for all the tips and info, much appreciated!