Design & Build an Exceptional Anime / Movie / TV Tracking App

`https://graphql.anilist.co` Use real: - anime titles; - artwork; - characters; - creators; - studios; - metadata; - relations; - recommendations; - other useful AniList information. Do not spend most of the bounty building backend infrastructure. The focus is the **frontend product experience**. Mock user-specific data where necessary. --- # Required Product Surfaces You must implement all of the following as parts of one coherent product: 1. Public Landing Page 2. Logged-In Home 3. Anime Detail Page 4. Advanced Search / Filter / Discovery 5. User Statistics They should not look like five unrelated design exercises. Navigation, components, interaction language, typography and visual identity should remain cohesive throughout. --- # 1. Public Landing Page Create the public-facing experience for someone who has not signed in. The landing page should immediately communicate that this product is about: - tracking what you watch; - discovering what to watch next; - understanding your own taste; - exploring media in a more enjoyable way. Do **not** make a generic SaaS landing page. A large headline followed by three icon cards and a testimonial section is unlikely to score highly. The product itself should become part of the marketing. Consider creatively using: - real posters; - user lists; - viewing progress; - recommendations; - taste profiles; - statistics; - discovery interactions; - animated product previews; - interactive media collections. The landing page should already demonstrate some of the personality and interaction quality of the application. --- # 2. Logged-In Home Design the main experience users see after signing in. This is not just a dashboard. It should feel like the place users naturally begin every session. Assume the user already has a meaningful media library. At minimum, it should elegantly handle: ## Currently Watching Users should be able to immediately understand: - what they are watching; - how far through it they are; - what they can watch next; - when relevant new episodes arrive. Episode progress should be easy and satisfying to update. For example: `7 / 12 episodes` could be represented in a much more interesting way than plain text. ## Recommendations Show personalized recommendations. Avoid simply placing every recommendation into the same card grid. Think about different recommendation contexts such as: - because you loved a particular title; - something outside your usual taste; - highly rated titles you somehow missed; - new releases; - shows from favourite studios; - shorter things to watch; - seasonal recommendations; - recommendations based on particular themes or tags. The recommendation engine itself can be mocked. The **experience around recommendations** is what matters. ## Other useful information Use your judgment. The home could potentially include things such as: - upcoming episodes; - recent activity; - friends' activity; - seasonal media; - recently completed titles; - favourites; - milestones; - recommendations; - quick stats; - interesting discoveries. Do not turn the page into a wall of widgets. Prioritize what genuinely improves the experience. --- # 3. Anime Detail Page Design a complete page for an individual anime. Use **AniList as the functional benchmark for information completeness**. You are expected to inspect AniList yourself, explore a real anime page, inspect the AniList API, and determine what information and interactions belong on a serious media-detail experience. We intentionally do **not** provide a checklist of fields. Part of the challenge is researching the domain and deciding: - what information matters; - how information relates to other information; - what deserves prominence; - what should be secondary; - how users should move through large amounts of content; - how tracking actions should work; - how related content should be explored. The finished page should feel at least as **informationally complete** as AniList while being substantially more thoughtful in its presentation and navigation. Missing meaningful information available through AniList will be penalized. Do not simply copy AniList's existing layout. We care heavily about how you solve the information-density problem. A giant vertically stacked encyclopedia page is not automatically a good solution. Consider whether information could be navigated through: - contextual sections; - persistent navigation; - subviews; - interactive relationships; - progressive disclosure; - expandable surfaces; - spatial transitions; - connected media structures; - other original approaches. These are suggestions, not requirements. Research the domain and design the best solution you can. Use an anime with **substantial data** so the interface has to deal with a realistic amount of information. Choosing an unusually sparse title to avoid difficult design problems will score poorly. --- # 4. Advanced Search / Filter / Discovery This is an important part of the challenge. We want a **serious media discovery system**, not a search box followed by a handful of dropdown menus. Look at AniList's filtering capabilities to understand the level of functionality users expect. Then design a significantly better experience around them. Users should be able to explore a very large catalogue through combinations of criteria. Potential filtering dimensions include things such as: - title search; - media format; - release year; - year range; - season; - airing/release status; - genres; - tags; - inclu