mikunj / ookami Goto Github PK

Please add feature read manga.

Currently this is done by loading in more data if it's an iPad, but for cases such as iPad Pro (12.9 in), only half of discover view is filled.

Currently when you launch the app, there's a delay and then the entries just 'pop' in. Instead of this it's better if the entries fade in to view.

At the moment, we only display English, Japanese and Romanized titles in media view controllers.

MediaTitle object has a LanguageKey enum in it which is being used to get these titles. This should be scrapped in favour of automatically finding the locale string name.
E.g en => "English", ja_jp => "Japanese".

We want to do this because, later Kitsu may pass back multiple different titles with different locales and we should be able to show that to the user without manually adding them to the enum. This also means we don't have to keep updating the app to add more codes.

We can use NSLocale which is already built in. Not sure how it would display, since if you pass in 'ja_JP' it will return "Japanese (Japan)" and that may look weird in the media view itself.
http://nshipster.com/nslocale/

Please add support ios 8.0

• Add quick update widget
• Update media pages to include franchise, characters & reviews (and everything else that is on kitsu)
• Library search
• Start and End date fields in entries
• Sort library by progressedAt rather than updatedAt
• Change Top/Best of 2016 to 2017 in trending (only show top of last year if it's the first season in the year)
• Change default display in discover. At the moment it shows top anime/manga of all time but it gets repetitive to look at.
• Add sorting in discover
• Fetch library entry when viewing anime/manga. This is so that if an error occurs while fetching a users library, the entry can still be fetched when going to a specific anime/manga page

The library entries for SilverHikari do not load fully. They have 2635 entries in their plan to watch list yet only 719 manage to load into the app. This may be an issue with kitsu api or the app itself.

This may be related to another similar case where a users (NeKoRare) completed/planned list won't load and that is due to the api giving an internal error.