Developing a watchface with implementing "unlock code" for a premium/VIP version in the "App Settings" - Help needed !!!

Hi Guys,

I would like to program a watchface where I can implement a sort of "unlock code" or "unlock key" in the app settings in Connect IQ. With this option I would like present a VIP version with a couple of more data fields or functions. Not a trail version (what will only work for apps and not watchfaces - what I have learned so far).

Although there are a lot of watchfaces in the IQ store with that "unlock key" and pay option, I could not find any ways or answers how to implement it in the "app settings" or program code as a developer.

Do you have any ideas or information how to do that? Nothing fancy and without any key generator or so. Just a necessary key in the app settings and one is good to go for more watchface options...

Thank you for your help and time answering my question!!

Every support is highly appreciated!

Kenny

0 BobMiles over 2 years ago

Well the easiest version (least safe) would be to check a string in onSettingsChanged against a hard-coded string and trigger a variable if it matches. Then in your code, only do the premium stuff if the variable is true.

As far as the app settings go, the premium options would be selectable to all users, but have no effect as long as the user didn't enter a valid code.

Of course, if somebody wants to be mean he can publish your premium code and people could get access without paying.

This is the lowest form of life version as far as I know. On the highest end would be a communication to a server where every user gets a unique code that is then checked and validated over the internet.

0 peterdedecker over 2 years ago

Bottom line is that you will need to implement something yourself.

One way is to implement an algorithm which uses the uniqueidentifier as input ( https://developer.garmin.com/connect-iq/api-docs/Toybox/System/DeviceSettings.html#uniqueIdentifier-var ), expose this info to the user, ask the info from the user, do a calculation on the input and then match the outcome with the expectation.

0 6789906 over 2 years ago in reply to BobMiles

Thank you very much for your response! Yes this is the way that I was looking for. Concerning the "mean" attitude of some people, I do not care. Those guys know how much work is in a watchface and....

Could you please give me a hint or a snippet/example how I could accomplish that? This is all a hobby and I am not a professional, so explaining it like for a rookie would be awesome!

Where to put the stuff (in which files) and how does it look like? Do you have a example code by chance?

Thank you very very much for your support and help!!

Kenny

0 6789906 over 2 years ago in reply to peterdedecker

Thanks to you both! I´d like to go with the lowest and most simple one...

0 BobMiles over 2 years ago in reply to 6789906

Hi Kenny,

I suggest you start developing your watchface with some settings. By the time it has a state where people would pay for it, I'm sure you know how to read app settings and compare two strings!

Look at the basic Garmin example that has settings!

All the best and a lot of fun coding,

Bob

0 waterkip over 2 years ago

My approach would be:

* generate a key
* use that key to generate a Premium API key based on some input from the user (eg device ID?)
* User enters that Premium API key
* You validate the input based on the key and the device ID
* If valid: enable premium settings
* if not valid: Don't.

You'll want: developer.garmin.com/.../Cryptography.html

0 6789906 over 2 years ago

Thank you guys for your support! Sorry for my delayed response. I have to work full time and this is just fun programming and a hobby.

I will try everything, when I have a little spare time, but the crypto-stuff, mentioned by waterkip, is too difficult for me, without more assistance or help.

Happy programming...