Special ProjectsIn progressIntense Violet theme

WatchTime

WatchTime is an offline-first media-tracking application built around .NET MAUI and layered application services. It organises films, TV series and anime, tracks season and episode progress, and supports catalog browsing and personal watchlists. Local persistence is separated from online metadata sources so users can continue managing their libraries without a constant connection.

C#.NET MAUIXAMLSQLiteTMDBOMDb
WAWatchTime
C#Main technology
224Tracked files*
171.cs files
24.xaml files
01 · What it does

What the application does

Capabilities evidenced by project documentation and source structure; some behaviours require platform configuration.

01

TV series, anime and movie collections.

TV series, anime and movie collections. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02

Episode and season watch-progress management.

Episode and season watch-progress management. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

03

Offline-first local database and application use cas

Offline-first local database and application use cases. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04

External catalogue/ratings lookups with TMDB and OMD

External catalogue/ratings lookups with TMDB and OMDb integration. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

05

Personal library search, filtering and imported meta

Personal library search, filtering and imported metadata. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Technical structure

How the system works

Technical architecture drawn from the repository and supplied documentation.

01

Application use cases orchestrate catalog and progress operations.

02

Infrastructure layers separate local storage from online metadata providers.

03

MAUI screens bind to view models for supported platforms.

01 · Input or user action

The workflow starts with the corresponding user choice or data entry. TV series, anime and movie collections. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

02 · Application processing

The relevant component must interpret the input, apply the project rules and coordinate any necessary storage, network access or computation. The documentation below identifies where that responsibility appears in the source when it is evidenced.

03 · Result and feedback

The resulting screen, calculation or stored record should reflect the processed state. Offline-first local database and application use cases. This capability is documented in the project material; the detail page distinguishes its intended user experience from the supporting implementation and any configuration needed to run it.

04 · Boundaries and verification

This page describes the documented behaviour, not an independently verified live deployment. Runtime configuration, permissions, test data or connected services may still be required.

PROJECT WALKTHROUGH

Modules & engineering details

How the major parts fit together and what each part contributes.

01

Personal media library

Films, anime and TV shows are organised into a searchable collection rather than a passive history list. Items can carry watch states, ratings or personal organisation fields according to the platform.

02

Episode tracking

Seasons and episodes can be associated with progress, making it easier to resume shows and monitor completion.

03

Offline-first application design

The local data layer remains usable without immediate external catalogue access. Online metadata queries supplement the offline library when connectivity is available.

04

Layered .NET architecture

The repository separates domain records, application use cases, infrastructure services and MAUI presentation, helping keep catalog logic independent of the UI.

05

Cross-platform delivery

MAUI targets supported devices, while availability of installers and platform integrations depends on the builds actually published.

Ratings, provenance and refresh strategy

WatchTime documents separate tracking experiences for TV, anime and movies, with a local-first catalog enriched by outside metadata. Its rating logic deserves a dedicated technical explanation.

01

Rating priority and fallback

IMDb/OMDb ratings are prioritised when available; TMDB supplies a fallback. A later TMDB refresh should not silently overwrite a valid IMDb rating.

02

Smart refresh and history

The app documents a first full-library refresh followed by fewer repeated requests. IMDb data is normally rechecked around 30 days later, while missing or TMDB-only ratings may be queried earlier.

03

Episode progress and local records

Show progress through seasons and episodes separately from ratings, favorite characters, watchlists and user-created lists. Locally saved watch state remains accessible offline.

04

Metadata failure handling

Network or provider outages must not erase saved user progress. Explain source precedence and fallback status without claiming external providers are always reachable.

Documentation: GitHub repository / project specification. The content describes documented behaviour or plans; deployment readiness is not inferred.

03 · Explore

Project-specific preview

Illustrative library statesFictional titles · no external media data
Series A
6 / 10 episodes
Anime B
12 / 12
Film C
Watched
Visual studies · project-specific

Interface and system concepts

Independent illustrative views of the documented or proposed workflows. They are not connected to a running backend, and their values are not actual measurements.

Application concept · illustrative

Library and watched-status dashboard

Series AAnime B
Watching
Completed
Planned

A personal catalog groups films, anime and shows, while watch state, ratings and optional third-party metadata remain distinct from user-authored progress records.

ShowsWatchlistWatchedProgress
Workflow mockup · illustrative

Episode progression and schedule

1Seen
2Watching
3Next
4Later

A horizontal progress rail makes the next unwatched episode easier to identify without implying that playback or external provider synchronization is already available.

SeasonEpisode 2Episode 3Next episode
Planning panel · illustrative

Release calendar and reminders

Upcoming releasesThis week
23MON
Episode 08Series A
New
25WED
Episode 12Anime B
Planned
27FRI
FinaleSeries C
Reminder
Personal reminders · illustrative

An optional planning panel could help organize release days, reminders and pending entries while staying separate from watch history and ratings.

CalendarReminderUpcomingLibrary
04 · Source and design

Implementation examples and code walkthrough

Local-first catalog search backed by an optional remote provider

WatchTime.Mobile/WatchTime.Application/UseCases/Catalog/SearchCatalogUseCase.csGitHub code excerpt
C#
var localItems = await _mediaRepository.SearchAsync(query, cancellationToken);
var resultsById = localItems.ToDictionary(media => media.Id, media => media);
try {
    var remoteItems = await _remoteCatalogProvider.SearchAsync(query, cancellationToken);
    foreach (var remoteItem in remoteItems) {
        var media = await SaveRemoteResultAsync(remoteItem, cancellationToken);
        resultsById[media.Id] = media;
    }
}

Checking an episode watch record

C#

Tracking is expressed as a small application use case rather than logic inside a MAUI view.

WatchTime.Mobile/WatchTime.Application/UseCases/Tracking/GetEpisodeWatchStatusUseCase.csSelected source excerpt
public async Task<bool> ExecuteAsync(Guid userId, Guid episodeId,
    CancellationToken cancellationToken = default)
{
    var watchEvent = await _watchEventRepository.GetLatestForEpisodeAsync(
        userId, episodeId, cancellationToken);
    return watchEvent is not null;
}

Protecting local import size

C#

The importer coordinates local events and remote catalog lookup, with a defined CSV size limit.

WatchTime.Mobile/WatchTime.Mobile/Services/TvTimeImportService.csSelected source excerpt
public sealed class TvTimeImportService
{
    private const long MaximumCsvSize = 64L * 1024L * 1024L;
    private readonly SearchCatalogUseCase _searchCatalog;
    private readonly IRemoteTitleAliasProvider _titleAliases;
    private readonly IWatchEventRepository _watchEventRepository;
}

Code samples are excerpts or documented illustrations; surrounding project files, configuration and dependencies may be required to compile or run them.

06 · Technology

Programming languages & stack

C#
.NET 9
.NET MAUI
XAML
MVVM
SQLite
TMDB API
OMDb

Core technologies and integrations used or planned for this project.

File types identified: 171 .cs, 24 .xaml

07 · Reality check

Status, evidence & limitations

The project status is based on repository sources and supplied documentation. It may be updated as the project evolves. A published case study is not a certification of production readiness.
  • Features are based on the supplied README and code inventory; no end-to-end runtime certification is implied.
08 · Resources

Downloads & project resources

Installers appear only after a verified release is added to the public download directory. Unavailable builds are marked clearly.

↓Windows EXEComing soon↓Android APKComing soon
Source and platform support may change. An installer is not implied by the existence of source files.