@Tomas5 that will defo crash. It can be hard for computers as well and has 0 benefit storing 1s reso on 200px (or so for example) screen. You want to be storing max the pixels to show the data. And that is not much .

@sky-runner Great to hear that you’re considering complex ideas! I haven’t looked enough at the documentation. It would be great if it was possible to switch to the app data screen from another data screen on demand, for example when the app handles a lap button event. I understand that most apps should never grab the “focus” like that, but in may be useful in done cases when the app needs a user attention. Perhaps there is a way to do a notification - I haven’t looked yet. This is a level of control we do not allow – only a human may switch between different applications Apps are also constrained to only showing things when they are in focus so there are, for example, no pop-up notifications. You can notify that something needs the user’s attention via (possibly repeated) sounds with playIndication. Overall, with S+apps being limited to HTML templates and not having custom pixel level graphics, this API feels somewhat limited to me. The canvas element is somewhat restricted but available. You can see some of what it’s capable of with apps such as HexHunter in the store, or the FowlPlay example here. By the way, how much memory and storage an S+ app can have? We do not have official guidelines for this. The figures alternate between models and updates.

I tried to create a SuuntoPlus app for having some notes on my watch which I can review during the activity. I got this working in the simulator and on my watch. [image: 1773354028857-7d8d04b3-6192-4011-a280-3e624862799c-image.png] The notes are stored in an array and can be selected in the SuuntoPlus app with the up and down button. For test purposes, I stored the notes in the data.json file: { "notes": [ "Some important things that you don't want to forget.", "Things to do when you arrive at a certain location.", "Any other note that is important to you." ] } I declared the notes array in the manifest "settings": [ {"shownName": "Notes", "path": "notes", "type": "enum"} ] If this app is published in the store, how are people entering their own notes? Is this handled correctly by using the type “enum”? Or do I need to declare a fixed set of notes as string and add them to the array in code? Like this: "settings": [ {"shownName": "Note1", "path": "notes.note1", "type": "string"}, {"shownName": "Note2", "path": "notes.note2", "type": "string"}, {"shownName": "Note3", "path": "notes.note3", "type": "string"}, {"shownName": "Note4", "path": "notes.note4", "type": "string"}, ... ]