Quote:
Originally Posted by sbaylor
Yes, password protection at the app and/or book set level has been on our internal nice-to-have feature list for a long time. But we hesitate to implement without sufficient user input.
I'm glad someone finally raises this password protection issue on this thread of discussion. Anyone else seconded?
Is an app level password protection sufficient? This clearly requires the least amount of work on our side.
However, if you want to let your young kids also enjoy reading on BookMaster, then you may want book set level protection.
Do you want to prevent your kid ust from opening a book or even from knowing the existence of the book (in the Library) in the first place?
More thoughts from everybody? Do you care to have password protection in BookMaster at all?
|
First of all, I love your app--BookMaster SE. It's already the best reader app by far among the two dozen reader apps I've tried since I acquired my first generation iPad. As you are openly soliciting feedback, I'll give my 2 cents.
Password protection is a nice-to-have feature, but it's definitely not a high priority item in my case. Having said that, I would like to offer a few suggestions here for your consideration. If this doesn't make sense to you, don't take it too seriously. I may not have thought through all the implications anyway.
1. An app-level protection should always be available in any usage model to be offered.
It should work kind of like the iPhone screen lock when you try to open the app.
2. Support a usage model where only a few books out of hundred or thousands of books are unprotected.
Sometimes I let kids read books (other than playing games) on my iPad. But I'm a bit worried that they may open my books and inadvertently mess up my notes, bookmarks and reading progress marks. I would rather restrict their access to the few books I'd encourage them to read, perhaps all in a book set specifically created for them. Thus, a model that protects all books by default with one switch and unprotects all books in one book set with another switch seems best for me in this case.
3. Only unprotected book sets can be switched to and displayed.
I don't mind others seeing all the book set names, but they don't need to see the book set contents.
4. All Exchange views as a unit can be blocked from access.
Since your app allows unrestricted Web Access, which is fine for its intended functionalities, App Store rates it as 17+. I'd like to see an option (under password control of course) to restrict access to Exchange views so that kids can't use the built-in browsers and can't download books. Otherwise, they may figure out how to download the very same books I block them from reading in the Library.
5. Use fingerprint authentication as an alternative to password for supported iOS devices.
This is more convenient sometimes. I can wait.
6. Come up with a design that somehow implements the above features and is still easy to use.
Take the time and don't rush.
Hope this is helpful!