Please let us know what you think, ask questions, all that jazz. We're still in the process of learning and making changes, so all feedback is super helpful.
- Laura (Grasshopper Founder)
Please let us know what you think, ask questions, all that jazz. We're still in the process of learning and making changes, so all feedback is super helpful.
- Laura (Grasshopper Founder)
We think there's a bug that's hitting some folks on Play Store that's related to an old manifest from our Beta 9 months ago... but we don't require those permissions anymore. Or at least we shouldn't. If you do see something when you actually try to download it, could you reach out to grasshopper-support@google.com? We're trying to find instances of this occurring and trying to convince the Play Store team it needs to be fixed :-/
This isn't a great experience for us or other developers, so I'm escalating internally. Thanks again for the report.
Why?
It might be possible for us to convince the powers-that-be to use another form of authentication, but for right now, we're sticking with just Google Auth.
Privacy best practice is to know nothing, or as little as possible, about the user.
If storing progress is required, and local device storage is not sufficient, a minimalist online setup is the desirable solution.
An automatically generated user id and a simple user-progress table should be enough. GCloud has all the required parts ready to go.
In any case this whole thing should come after the user has had a chance to experience the product.
But that’s just me.
I ain’t no power-to-be ;)
Thanks for the feedback!
We need a user account to store your progress: what puzzles you've completed, what code you've entered in order to save progress if you didn't complete the puzzle yet, coding streaks, etc. We're not collecting information about your device (or any other personally identifiable information other than the Google Account we associate with your account).
It's been easiest for us to do this user account creation using out-of-the-box Google Authentication, so that's why we went down this route. Hope that makes sense!
Please remove the need to create an account or login anywhere. Or make it optional so that those who do want to login, can. I would prefer the default be to not create/login to any account and an optional login flow for others.
Thanks!
So I couldn't test it.
It's been easiest for us to do this user account creation using out-of-the-box Google Authentication, so that's why we went down this route. Hope that makes sense!
First, you should ask for an account creation only when the user have already started. As I said, I didn’t even see if it was interesting at all, because of the login wall.
Second, if there are no sensitive information collected, there is no need of using a mountain to hit the nail. A pseudo will be enough. No email needed. Not sure if it even need a password... You store the pseudo locally and you are done.
(I agree I’m a little bit oversimplifying, but you see the point)
Heather — Curriculum Manager for Grasshopper here :)
That's the simplified Haitian flag.
The small teaser image you're seeing is the Haitian flag: blue at the top, and red at the bottom (the white is simply the background color).
The aim of that puzzle is to change the bottom stripe from yellow to red; changing the Ukrainian flag to Haitian.
Hope this helps explains things :)