Indeed. tombr pointed that out above.
We're not going to do two separate apps as that is a nightmare, but we will continue to evaluate the value of 1Browser moving forward.
I realize you won't be changing anything, and I respect that, but just know that I've been a happy 1Password customer for several years and I'm now looking for an alternative. You run your business as you see fit, obviously, but you are definitely losing a certain amount of customers as a result of these choices.
Thanks for the feedback. We're really not happy about the sitaution here either, but our hands are tied. We're put in the position of choosing between:
We lose customers either way. We're still evaluating which is the lesser of the evils.
Or: 3. Pause new feature development for a while, and factorise your code base so that you can easily maintain and QA a separate version without the browser (but sharing most of the codebase) so that you can genuinely call it "1Password for Families"!!
Sorry for being snarky, but I am resentful of the amount I have cumulatively paid for this and, now that my children are of an age to use it, they can't.
We're not going to offer two separate 1Password for iOS apps. We've tried that in the past, and it simply creates too much confusion for customers (development issues completely aside). I'm sorry but that route is off the table.
I empathize with your plight and I'm hopeful that we'll be able to find a better solution in the future. For now, Ask to Buy is the only option we can offer.