Jobs

Getting Started

GitHub
Downloads

Frameworks

.NET

.NET MAUI

Blazor

Operating Systems

Android

iOS

tvOS

macOS

Linux

Windows

Web

Shiny Jobs allow you to run periodic background tasks. On Android, this is powered by WorkManager. On iOS, by BGTaskScheduler. On Windows, by COM-activated background tasks. On Linux, macOS, Blazor WebAssembly, and any other plain .NET host, jobs are run by an in-process managed JobManager driven by a recurring timer — jobs only execute while the host process is alive. On Blazor WebAssembly, Shiny.Jobs is the only package you need.

Caution

Jobs are not scheduled at specific times. The operating system determines when to run them based on device conditions, battery, and usage patterns.

Jobs do not work on the iOS Simulator. You must test on a real device.

Platform Notes

Platform	Package	Notes
Android	Shiny.Jobs	WorkManager — true OS-managed background execution
iOS	Shiny.Jobs	BGTaskScheduler — OS decides when
tvOS	Shiny.Jobs	BGTaskScheduler — same as iOS, including the Info.plist setup. Does not run on the simulator
Windows	Shiny.Jobs	COM-activated background tasks; tasks fire while the process is running (no background-mode triggering yet)
Linux / macOS / Plain .NET	Shiny.Jobs	In-process managed JobManager on a recurring timer
Blazor WebAssembly	Shiny.Jobs	Same in-process scheduler. No separate meta-package — reference Shiny.Jobs directly; battery and connectivity come from Shiny.Core. Call await host.Services.UseShiny() after Build() so the scheduler starts.

Plain .NET / Linux / macOS

On these targets there is no OS scheduler — Shiny runs an in-process JobManager on a System.Timers.Timer (default every 30 seconds, configurable via JobManager.Interval, minimum 15 s, maximum 5 minutes). Jobs only execute while the host process is alive. AddJob registers IBattery and IConnectivity for you on Linux and Blazor WebAssembly. Plain .NET on Windows or macOS has no battery API, so register your own IBattery there. Job registrations are held in memory and rebuilt from your AddJob calls at startup — nothing is written to disk.

Windows COM activation

Windows uses COM-activated in-process background tasks. Call ShinyJobsBackgroundTask.RegisterComServer() once in your App constructor before any trigger registration, and declare a matching windows.comServer extension in your appx manifest.

Blazor WebAssembly

The Blazor implementation is not a true background job runner — it can only execute while the browser tab is alive. Jobs are re-registered from your AddJob calls on every page load, and nothing runs while the tab is closed. Service Worker / Periodic Background Sync cannot invoke C# jobs because the Service Worker has no access to the Blazor WASM runtime. For “wake the user when the app is closed” scenarios, use Push Notifications instead. For background HTTP specifically, use Shiny.Net.Http which uses Service Worker Background Sync in pure JS.

Features

• Cross-platform background job execution
• Runtime criteria (internet access, charging, battery level)
• Full dependency injection support
• Stateful jobs (persists state across runs)
• Foreground execution option

Setup

MAUIBlazor

Changed files

• MyApp/
  • ▸Delegates
    • MyJob.cs
  • ▸Platforms
    • ▸iOS
      • Info.plist
  • MauiProgram.cs
  • MyApp.csproj

Delegates/MyJob.cs

MyJob.csCopy

1using Shiny.Jobs;2​3namespace MyApp.Delegates;4​5public class MyJob : Job6{7    public MyJob(ILogger<MyJob> logger) : base(logger)8    {9    }10​11    protected override Task RunJob(CancellationToken cancelToken)12    {13        return Task.CompletedTask;14    }15}

Samples

• MAUI Sample