I'm building a media management app, that is probably best described as netflix for your personal media collection, and similar to plex (but supports low end machines, no streaming yet) - AND it's going to be completely free and open source. I've decided to use themoviedb as a basis for this application to make it easier for people to build out their collection, while maintaining various lists that can be subscribed to.
This is the general setup of the app, from install to everyday running, with some questions I have, too.
At install, should the app request that the user creates their own themoviedb account with an API key? I don't know if it makes sense that potentially hundreds of users would be making requests through one API key, but I am more than comfortable doing this. Should I be setting a request header that identifies my app (ie. X-TMDBAPP: myappname/mywebsitename.com)?
On first run, the user is prompted with:
Daily use:
The nice thing about doing it this way is that users don't have to have a huge collection of videos to have a good selection, it encourages people to buy digital copies, and most of all, makes their media very accessible.
So I guess most of my questions are related to the install process and caching. I noticed a bit of the clause in the API agreement that stated that cache should really only be when necessary - I don't want users to be making a ridiculous amount of requests every action a user does, because that would also violate the terms and agreements for the API.
Ne možete pronaći film ili TV seriju? prijavite se da biste ga napravili.
Want to rate or add this item to a list?
Not a member?