A public view of what recently improved, what is being refined now, and what is planned next for the media tracker.
OmniTrackr has moved beyond a simple private list. The latest release work focuses on making the public side useful before signup while keeping the logged-in tracker safe, fast, and familiar for existing users. Visitors can now read practical guides, compare tracking options, preview a sample library, understand privacy controls, and browse public reviews that users intentionally share.
Guides now explain movie, TV, anime, game, music, book, statistics, export, template, and review workflows in crawlable pages.
Public reviews are supported by clearer category filters, review guidelines, quality prompts, and minimum-content safeguards.
Advertising and privacy pages explain where ads may appear, how Google ads use cookies, and why private account areas stay separate.
Recent work tightened CSP handling, removed unsafe inline requirements, improved metadata, and kept generated API docs out of search results.
Current priorities are deliberately practical. The goal is to make OmniTrackr easier to understand for a first-time visitor while preserving the workflows existing users already rely on.
Current work also emphasizes content quality. Public pages should answer real tracking questions instead of acting as empty search pages. Category guides, review guidance, comparison pages, and demo content are being expanded so visitors can learn something useful even before they decide to register.
The next set of improvements is aimed at reducing setup friction. A media tracker is most useful when people can bring in existing lists, clean up old backlogs, and see progress without rebuilding everything by hand.
Longer-term ideas stay focused on portability, control, and useful context. OmniTrackr should help users remember why something mattered, not just store a title and rating.
Because OmniTrackr is already live, roadmap work has to protect existing accounts and media libraries. Public-content updates should not require destructive migrations, reset user settings, remove saved entries, or change private/public review decisions without the user's intent.
Recent verification covers account flows, authentication, CRUD endpoints for each media category, import/export, friend and privacy behavior, statistics, public reviews, SEO routes, static security checks, and content-security-policy behavior. That testing focus keeps growth work tied to the real product instead of only the marketing pages.
Roadmap ideas are evaluated against two questions: will this make everyday tracking easier, and can it ship without putting existing user data at risk? A feature that looks impressive but complicates privacy, exports, or account stability is less valuable than a smaller improvement that users can trust immediately.
Public-page work follows the same rule. A new guide should answer a real tracking question, link to related resources, and stay useful even if the visitor never creates an account. That keeps the site from becoming a collection of empty search pages and gives returning users a clearer place to find product changes.
For the current release, that means prioritizing review quality, stronger public examples, clearer privacy and advertising disclosures, and regression tests that protect the live tracker while the public content surface grows.
A roadmap helps users see that OmniTrackr is maintained and gives new visitors a reason to come back. It also explains the product direction: a practical, privacy-aware tracker for many kinds of media rather than a thin single-purpose list. That matters for people deciding whether to trust a new tracker with their history, ratings, reviews, and private notes.
The roadmap is not a promise that every idea will ship in exactly this order. It is a transparent product note about what the app is optimizing for: useful public resources, portable user data, safer sharing, stronger review quality, and a calmer advertising approach.
See what has already changed in the changelog, preview the demo library, or compare OmniTrackr with other tracking methods on the comparison page.