-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Problem statement
The method used to generate passwords is easy to extend to different languages. I think either French or Italian would be good second languages; they are similar to English and those countries are top spenders in the App Store.
I'm not sure what the UX or payment model looks like for this. Should there be one app that has multiple languages in it, or multiple apps one for each language? Surely there should be one app?
But if there's only one app can we charge money for an in-app purchase for different languages? That doesn't make sense, what if English isn't your first language? I was hoping additional languages would be a source of revenue.
Once you do this...the size of the Rust shared library will be huge. Do we need to compress the wordlists then decompress when using them to generate a password?
Do we need to internationalize the app before adding a second language as a password word data source? I'm not sure.
Ordering
- Only do this once Ensure wordlist data generation is checked into repo and uses cirrussearch #2 is done. With Ensure wordlist data generation is checked into repo and uses cirrussearch #2 out of the way it'll be trivial to at least generate the wordlist data file for separate languages.
Acceptance criteria
- As a user I can generate passwords whose memory aids are based in a second different language, preferably French or Italian.
- The performance of the phone apps remains acceptable.