tmarcc
"Everyone has a right to a wrong opinion."
A few comments:
- Bug (Android): With a new installation, the Profile/Car page currently is blank - just an endless spinning circle. I'm a new user, but was this the page that shows the amount of battery charge, the cabin temp, lock status etc? I did see it briefly, but the app spontaneously crashed. Perhaps the crash is related to the spinning circle / unrendered page.
- UX (Android): The back arrow on the upper left side of the setting screen is hard to tap.
- Privacy (real name): upon sign-up you require that folks provide their first and last name. Why do you require this of your users? It doesn't seem necessary for the functioning of the app.
- Privacy (authentication): You should consider allowing for your own authentication mechanism, such as login & password, beyond just Facebook or Twitter (in the Android version, I only saw Facebook as a sign-in option). Unless you want to encourage a "real names" policy w/your app, some folks may they want to associate this app with their account, if they have one.
- Private Trips: it's great that you have a toggle to make trips private, and a little instruction tip on how the setting works. You should be cautious about defaulting this to "on" though unless you provide clear notice to users. If you choose to default the setting to "on", then as part of the new user sign-up flow you should consider providing a short interstitial explaining that 1) the app shares trip data publicly by default, 2) they can change the option in "Settings", and 3) provide a checkbox right on the interstitial page allowing them to opt-in or out of that feature (you could leave the checkbox checked if you want).
- Privacy (account termination and deletion): unless all historical app data is stored on the phone, you'll want to create a mechanism by which users can cease using the app, terminate their account, and have you delete applicable personal data / personally identifiable information from your servers and/or cloud provider.
- Privacy (terms): Your FAQ on teslatracks.happyfuncorp.com is good start, but soon you'll want to make a privacy policy available to your users, accessible from 1) within the app and 2) from your homepage, covering the usual areas 1) what data is collected, 2) how the data is used, 3) with whom you share the data, 4) how the data is protected, 5) how users can delete that data, and 7) whom to contact with privacy questions.