Goodreads Developers discussion

Hello there,
I am currently in the process of writing my own Android app and I am in a bit of a predicament. This is going to be an app that will have lots of users (not monetized--will be entirely free), so I am a bit concerned as to how data can be gathered from the API without each non-developer user having to register a developer key. Is this possible? Could I use something like OAuth2 to get an access token for the API and make requests that way (i.e. make a request for a book with a passed ISBN)?

I just don't want users to have to go and make their own developer key. These users are likely not going to be technically inclined, so I don't want them to have to go through a bunch of tedious steps just so they can use the app I am making.

Also, is it allowed for users of the app to store book data (not book data strictly tied to their accounts) gathered from the API in a SQLite database?

there is info about storing data locally in docs.
and there is an oauth 1 api (with some troubles but nevertheless) you can use for users.

Andrew wrote: "there is info about storing data locally in docs.
and there is an oauth 1 api (with some troubles but nevertheless) you can use for users."
Thank you for the response.

I have since discussed my situation with the developers and have figured out a solution

I also need a book that I will learn that how to make an android application. Now, I have interest to make a rooting tool like kingroot app...

@Maya there are enough apps for obtaining super user access :P what's the point creating a new rooting app with the existing source code?

Ravi wrote: "@Maya there are enough apps for obtaining super user access :P what's the point creating a new rooting app with the existing source code?"

For the experience and knowledge, I'd imagine. I won't stand in her way!