|
|
|
|
|
by yojimbo311
4424 days ago
|
|
I was really excited to try this out, but then I hit the requirement to provide contact information just to download the library. This is, for good or bad, always off putting to me. I don't consider the need to collect certain information bad in itself as long as it's reasonable or at least justified. In this case however, there's a distinct lack of communication as to why the information is being collected and that makes me wary (it's also fairly common recently so this isn't the only offender). I can make all sorts of my own assumptions as to why the developers would need that information, but after being bitten a few times by folks who have been a little less than transparent with their actual use of that information I'd prefer not to rely on my own assumptions. Some feedback based on my experience (take with a healthy dose of salt): - The quickstart menu item is the only one that takes you away from the main page which interrupts the experience when using this particular style of pagination. The way back to the main page from the quickstart page is also not particularly obvious (just a back arrow within the logo would be sufficient). - A big red flag is the counter counting how many gestures have been "tracked" leading me to believe that there's some sort of phone home going on which, all things being equal, doesn't make too much sense for a gesture library (unless some explanation is provided). - Another big red flag is no mention of why the need for a full name is required in addition to the email, or why the email is necessary for the download (It's mentioned that it will be sent to the email if the user scrolls down to the 2nd form, but not in the first "page"). - No obvious way to provide feedback is immediately available (I assume it's provided in whatever email communication is made or within the library itself). (edit formatting) |
|
Intercepting the traffic coming out of the app shows me its making api requests to http://api.parse.com — so, basically, I would imagine it's sending some kind of usage data (can't yet decipher the headers as I don't have time) back to Parse.com, which is allowing it to 'phone home'.
Also... this is happening with every motion gesture attempt.
sigh