[baddox]

Just a tip: the validation on the SMS phone number should really be a lot nicer. I tried AAAPPPNNNN (Area code, Prefix, Number) first, and it said I needed the international code. So I tried 1AAAPPPNNN and it still complained. So I tried 1-AAA-PPP-NNNN, and after getting the same message for the third time, I realized that the message was very literal, as in, I had to type +1-AAA-PPP-NNNN. Requiring a format that virtually 0% of people will type the first time isn't a great idea.

Humorously, the success message then says "Success! SMS sent to +1AAAPPPNNNN."

[DesaiAshu]

Hey, thanks for the feedback! We (MakeGamesWithUs) are just rolling out these landing pages and when building this we were not 100% sure the best way to implement the phone number validation. About half the people downloading our games are outside the US, so it seemed relevant to address international numbers. The dashes don't actually matter, but without forcing the '+' it wasn't clear how to figure out what country the number is from. If the '+' is optional, we could assume any 10 digit number is from the US, but I think this would cause problems for a few smaller countries. We could check your IP and prepend if the correct country code wasn't present in number, but my instinct says this would cause unforeseen issues. Alternatively we could simply give inline feedback (instead of the notification at the top) to specify you need the '+'. I agree it sucks that most people won't get it right the first time, but I'd also like to guarantee nobody gets a success message when the SMS wasn't sent to their number, any suggestions on how to fix this?

[darkmighty]

Parse this list: http://wikitravel.org/en/List_of_country_calling_codes to generate a dropdown menu where you choose you country and it puts an uneditable +XX beside the number.

Bonus #1: Most visited country default option

Bonus #2: Use IP geo to pick country

[Hello71]

Recommended UI: Have one of those gray placeholder texts in the input box saying "[phone]" or whatever format you require.

[dncrane]

> any suggestions on how to fix this?

Could you have separate input boxes for each segment of the phone number? (as in #2 here: http://www.lukew.com/ff/entry.asp?1015 )

[martin_]

Ashu! Your friends at iCracked would love to help... reach out to me anytime man! Rachel, I feel it'd be nice to have a visual indicator as I touch the screen, right now if you can press anywhere and it just seems unresponsive. Also, for a while I didn't realize you could move obstacles so the "get a hint" constantly resetting the level was a little confusing. Finally, undo occasionally crashes the app. Overall, great work!

[rachelpinsker]

Someone else also mentioned getting feedback when you touch the screen. That seems like a great idea and I'll try to update the app to respond to touches immediately.

And thanks for letting me know about your confusion. I'll try to update the tutorial so it's as easy as possible to figure out!

As for the crashes, I am aware of users encountering a few issues and I'll work on fixing those problems.

[rachelpinsker]

Thanks for the input. Sorry you had so much trouble.