You are reading a single comment by @malaire and its replies.
Click here to read the full conversation.
-
There may be persistent vars in the future, but the relatively restricted nature of the device means that any app with a memory leak would effectively make the watch unusable ...
Such a feature should definitely have some kind of per-app limit for persistent data size. Perhaps a max size in bytes in
metadata.jsonor in settings?
malaire
Hi - I think the others have covered this just fine, but just to clarify:
In Bangle.js, everything is ripped down when you change apps. There is no way to store a variable that persists so the
killevent is the best option - if you write the same file to storage as before, the write will be ignored so it's not too bad.There may be persistent vars in the future, but the relatively restricted nature of the device means that any app with a memory leak would effectively make the watch unusable - and given the amount of time I spend supporting people who installed apps that broke their watch right now, I feel pretty confident that I'd regret adding it at the moment :)