When storing a new bookmark so that a user can resume a video they have left half watched, I've written a function which checks whether the user has reached an arbitrary maximum number of bookmarks and, if so, deletes the oldest bookmark before saving the new one, so as to not waste huge amounts of registry space with if the user happens to leave every video in the app unfinished.
These registry entries include the deep linking video GUID, info about when the bookmark was saved in UNIX epoch format, and—obviously—the point at which the user stopped watching the video. The latter two are saved in a single string separated by a delimiter character, which I split up using the ifStringOps Tokenize function when I'm processing the data from the registry.
Currently I have the max number of bookmarks set to 7, which seems to me like it generates a list that's small enough not to be overwhelming (the "resume–able" videos are displayed in a "Keep Watching" category on the home grid), while still being large enough to not be entirely useless.
My question is this: I know that there are memory/storage differences between different Roku devices, so would it be beneficial to vary that max bookmarks number depending on the device/model number on which the app is running? In other words, is there any reason to set maxBookmarks to, say, 4 on model number 1XXX and 2XXX, 7 on 3XXX and 4XXX, and 10 on 5XXX? Or am I overthinking this, and the amount of device storage space I'd use on the function itself would cancel out the negligible benefits of doing this anyway?
