I want to make an app for a collection of users. They are all essentially “customers”, and I have their names, phone #s, email, etc. in a database. For those that I can convince to load this app on their phones, I want to connect that app to what is essentially their “account” on my backend server. I specifically do not want them to have to start the app, enter some account ID, password, etc. When the app starts up, it needs to connect to the backend server in a way that lets me uniquely identify the customer.
Most ideal, the app starts up and is able to send an HTTP request that includes some uniquely identifying piece of information (can I get at and transmit the phone#?) so that the backend knows who it is and can send back custom ID info that the app can use on all future interactions.
Second best, I transmit a unique URL (includes token identifying that unique user) to their email address, they tap on it in their phone, and somehow it gets that info to the Corona app so it has it next time it starts up (no idea if that kind of cross-app data sharing is available via Corona).
It’s really the initial “stamping” of that app with a customer ID of some sort that is the only trick. It would have to work with iPhone, Android, and (being in Microsoft’s back yard) Windows phone would be really nice. I’m initially trying to avoid push notifications, both because I don’t want the server-side complexity for a demo app, and because I fear it would quickly get abused, causing customers to uninstall the app. But, if that were the only way to go for the lowest-friction experience, I would have to look at that route (but I think I read that the push plug-in doesn’t support Windows phone, which is a minus).
Can someone give me a handwaving overview of what my options are to accomplish something like this?