[johanznsdn]

Thanks for your feedback pvg!

The data is stored using 'chrome.storage'. So it's either stored locally if you aren't signed in to Chrome Browser or stored in the Google servers if you are signed in. So the sync happens using your Google account. (https://developer.chrome.com/docs/extensions/reference/stora...)

Concerning the 'lifetime' word, I get your point. I just wanted to highlight the fact that you only pay once for the premium features and that it's not a 'subscription business model'.

[pvg]

Isn't storage.sync limited to something tiny like 100 Kb? Or has that changed?

[johanznsdn]

You're totally right.

"In my opinion, it’s a pain to have recurring cost for small extensions/apps like Stringmark. But as @razemio said, it’s (most of the time) necessary when the service uses a backend. As I said, I want to avoid recurring cost and that’s why I decided to use chrome.storage. Also, as another comment and @razemio said here, the sync storage of Chrome is limited in size: ~100kb which is roughly 370 highlights in Stringmark because the text you are able to save is limited in size (~120 characters). Also, the local storage of Chrome is unlimited in size.

It means that you can have ~370 highlights that are synced through your devices. Honestly, I think that it is enough but you guys are right I should precise it in my website, I’ll update it ASAP!

@bruth that is the reason why the product will never go away since I don’t have backend costs!

In order to attenuate this sync storage size limitation I plan to add these features: Limit the number of highlights per list; Let the users decide to save a specific list locally or using chrome sync; Export lists by email and/or in various file format in order to free up space; Import lists easily

The other solution is to add another premium plan with a recurring cost and where I would use a database backend for these users so that they can really have ‘unlimited’ highlights synced.

Tell me what you guys think about these solutions!"