Skip to content

Need an account for an about faking location? #6

Description

@xmicro

I don't know if it's just me, but it just seems very weird why a module that hooks into our Google Play services and Google Maps needs us to sign up with email and password. The whole point of changing your location means that you don't want your original location to be viewed (by the app being spoofed or anyone, including the app doing the spoofing itself), so what possible legitimate reason could there be that requires personal information to sign up? (If there is one, I'm genuinely curious. But metrics aren't a valid answer because you could get download metrics easily with a site that supports download counters, etc.) I get that we could use a throwaway email/password, but presumably not everyone is doing that. (And you even have a "login with Google" button that further encourages users to give out their personal information.) For an app to which the user must already give so much good faith that their privacy and constant location access will be respected, especially for one that's closed source according to another post, it's very hard to ask for even more identifying information on top.

I wish I got the chance to try this app because it looks genuinely interesting, but that's just way too many red flags for me unfortunately. Hopefully if things change, such as an option to skip sign up, or the project goes open source, then I'd be willing to try it.

This isn't intended to be in bad faith either; it's just a genuine concern to me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions