Ultra MAX 8.0.0
Everything already added to the development system for Ultra MAX 8.0.0, covering major workflow, reliability, visual and architectural improvements.
Major improvement
One Nuvio connection across the whole setup
Nuvio account state is now shared across the setup experience.
Users connect once, select the correct profile and continue without
repeatedly signing in or wondering which account is active.
- Explicit Change Account control
- Correct handling of public and numeric Nuvio profile identities
- Cleaner connection and profile status
- Collection pushing removed from Finalise and Generate
- Reduced duplicate controls across setup steps
Safety
Safer Nuvio collection syncing
Ultra MAX now compares the live Nuvio collection state with the
setup being prepared before anything is written. The process is
built to protect existing collections and prevent stale changes.
- Read-only comparison before writes
- Add Only mode
- Three-way Safe Merge
- Stale-plan detection
- Guarded whole-array writes
- Canary validation and exact rollback testing
- Clear added, skipped and protected counts
- Cancelled preset selection no longer commits changes
Improved
Fusion is cleaner and more dependable
Fusion creation, previewing and sharing now sit inside a clearer
workflow with stable collection identities and safer source
handling.
- Improved Fusion preview and sharing
- Stable folder and collection identities
- Cleaner source selection
- Better separation from standard collection syncing
- Improved Android navigation through Fusion screens
New
Multiple setup profiles under one token
A single Ultra MAX token can now hold several independent setup
profiles, making it easier to maintain different configurations
for devices, users or viewing styles.
- Fast profile switching
- Profile-specific catalogue choices and preferences
- Reduced state leaking between profiles
- Cleaner loading and editing behaviour
Catalogue system
More reliable catalogues and stronger compatibility
The catalogue layer has received extensive work across MDBList,
custom sources, legacy IDs, ordering, filtering and metadata
conversion.
- Built-in MDBList rows moved to the current MDBList API
- Fixed lists that appeared empty despite containing hundreds of titles
- Readable catalogue IDs with legacy compatibility
- Public MDBList search and custom MDBList rows
- Custom genre, provider, decade, actor, director and keyword sources
- Improved duplicate handling and catalogue ordering
- Better digital-release filtering
- Improved filtering consistency across multiple catalogue sources
Technical example
The “Must-See Mindfuck” row previously returned no content
because an older MDBList endpoint returned an empty response for
that specific list. The updated endpoint returns the full source
data and now produces a populated Ultra MAX catalogue.
Metadata
Improved anime and identity handling
Anime catalogues now have more deliberate metadata and ID handling,
with improved support for services that depend on original Kitsu
identities.
- Kitsu ID preservation support
- Unified and AniSync presentation modes
- Improved AniList and MyAnimeList integration paths
- Better anime row filtering behaviour
- Stronger TMDB, IMDb and Kitsu mapping safeguards
Improved
Cleaner stream results
Stream results are easier to scan and compare, with more consistent
formatting for quality, file information and debrid results.
- Consistent result titles and video information
- Clearer quality and file-size presentation
- Improved provider compatibility
- Stream resources hidden when no stream provider is configured
- Reduced unnecessary provider and API errors
Visual overhaul
A denser, calmer setup experience
Large cards, deep empty spaces and repeated inner boxes have been
reduced. The setup now makes better use of the screen while keeping
advanced controls available when needed.
- More compact cards and collapsed sections
- Reduced visual clutter and unused space
- Clearer hierarchy between important and advanced controls
- Improved confirmation overlays
- Better mobile and narrow-screen behaviour
- Cleaner account, profile and collection status areas
Security
Security and failure handling improvements
The platform has been hardened across authentication, configuration
handling, browser rendering and external API failures.
- Safer handling of sensitive values
- Improved input and configuration validation
- Reduced accidental state leakage
- Safer browser rendering and WebView behaviour
- Improved timeout, rate-limit and API failure handling
- Additional protection around collection writes
Technical
A more maintainable backend
Major backend responsibilities have been split into dedicated
services, reducing the size and risk of the central application
file.
Manifest service
Manifest route service
Config route service
TMDB preview service
Catalogue handler service
Shared Nuvio setup context
- Critical JavaScript files syntax-tested independently
- Manifest and catalogue routes tested after each extraction
- Incremental refactoring with backups and compatibility preserved
- Reduced reliance on one oversized backend file