Jobs

Getting Started

GitHub
Downloads

Frameworks

.NET

.NET MAUI

Blazor

Operating Systems

Android

iOS

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, reference Shiny.Core.Blazor for IBattery/IConnectivity and (optionally) Shiny.Extensions.Stores.Web if you’d rather persist job state to localStorage than the default filesystem repository.

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
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; filesystem JSON repository
Blazor WebAssembly	Shiny.Jobs (+ Shiny.Core.Blazor)	Same in-process scheduler. No separate meta-package — reference Shiny.Jobs directly and bring in Shiny.Core.Blazor for battery/connectivity. Optionally use Shiny.Extensions.Stores.Web for localStorage-backed state.

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. You must register IBattery and IConnectivity yourself (e.g. from Shiny.Core.Linux or Shiny.Core.Blazor); a default JSON filesystem repository is added automatically.

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 and their state survive page reloads (via localStorage), but 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.Blazor 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

• NuGet Packages
• Project File
• MauiProgram.cs
• AndroidManifest.xml
• Info.plist
• PrivacyInfo.xcprivacy

Shiny.Jobs

Shiny.Hosting.Maui

Samples

• MAUI Sample