Home/ Questions/Q 8189321
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T03:14:22+00:00

I have read the other posts about password protecting your application, but my situation

  • 0

I have read the other posts about password protecting your application, but my situation is a little different.

I still want password protection, but I want to create the passwords myself, and then once a password is used, no other user can enter it.

Lets say I have a list of passwords (hamAndCheese, hamAndCheese1, hamAndCheese2). If 1 person downloads the app from the app store and enters hamAndCheese, I want that password to be “broken” if another user tries to enter it.

Also, once a user enters the password once, I don’t want them to have to enter it again. (Im less worried about this part, more about the part described above).

Should I just make a list of passwords? How do I eliminate them once they have been used?

Thank you

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1. You could make a time-dependent password.
      you generate a list of passwords, and the viability of the pw is only a few days. This makes reduces the risk that your passwords will travel after the time they are useful

    2. Second option is a webservice that you built, and that validates the password over the internet

    3. As stated before by tux91 – sounds like it could be used to generate a revenue stream outside the appstore, leaving big bad apple without it’s 30% cut of your revenues

    • 0