I’m thinking about the “auth token issue” in final products or products one might want to sell.
Some of this has been discussed here, but I feel “sharing my project” doesn’t really solve the issue.
Let me try to describe where I see this issue:
1- you create a product (whatever it might be) with a Blynk supported board
2- to sell it, you need your customer to setup an account in Blynk and clone your project (from the project’s QR code for instance)
3- once the project is cloned in the customer device, you can ask them to provide you with the project auth token
4- When you get your hands in the customer’s auth token, you can flash it in the hardware you are selling them
5- they can now buy this “customized to their phone” (so to say) product, since their phone is linked to the product
This seems a bit painful since there is a back and forth between you and your customers in the sense that your customers need to create an account in blynk, clone the project, give you their auth token and then you can flash the thing (the product) and give it to them. Now that I think of it, you could create the blynk account for your customers and have them change their password to alleviate a bit the pain.
Sharing may not fix this issue since when I sell them the device, I don’t want to have anything to do with it. For instance, I noticed that if I share a project and I stop it in my phone, my friends/family see the project stopped.
Imagine I delete this particular project by mistake, I would need to call customer X, have him send me back the product to re-flash it with a new auth token from a new project. Ouch.
Am I missing something?
Would there be a way (an API?) of getting auth tokens for pre-provisioning projects with them in case this proves to alleviate the problem described?