Getting Help & Getting in Touch
Shiny is spread across more than twenty repositories, which makes “where do I post this?” a genuine question. This page answers it.
The channels
Section titled “The channels”GitHub Discussions
Questions, design feedback, and "which library should I use?"
The org-wide forum, shared by every Shiny library. Best for anything that spans more than one repo, or where you are not yet sure whether you have found a bug.
What to expect: Answered by maintainers and other users. No response time guarantee.
Discord
Quick questions and realtime chat
Shiny lives in the MAUIverse Discord alongside the wider .NET MAUI community — good for a fast sanity check, sharing what you are building, or a conversation that would be slow over issues.
What to expect: Casual and realtime. Chat scrolls away, so anything worth keeping belongs in Discussions or an issue.
GitHub Issues
Bugs, crashes, and concrete feature requests
Each library has its own repo, so an issue needs to land in the right one. The picker below maps what you are using to where it lives.
What to expect: A repro (or a failing sample) is what turns a report into a fix.
Sponsorship & commercial
Priority attention, consulting, private work
Shiny is maintained in the open. Sponsorship funds that work; ShinySoft Technologies handles consulting, private support, and anything that cannot be discussed in public.
What to expect: Sponsors are prioritised. For commercial enquiries, see ShinySoft.
Where should I post?
Section titled “Where should I post?”Match what you have on the left to where it goes on the right.
| What you have | Where it goes |
|---|---|
| Something crashes, or behaves differently than the docs say | An issue in that library’s repo — find it below |
| “How do I…?”, “Which library should I use?”, “Is this the right approach?” | Discussions |
| A quick sanity check, or you’d rather just talk it through | Discord |
| A feature idea that isn’t fully formed yet | Discussions first — open an issue once it firms up |
| A feature request you can describe concretely | An issue in the repo that would implement it |
| Something wrong, missing, or unclear in these docs | An issue or PR on shinyorg/documentation |
| A security issue | Do not open a public issue — see Security below |
| Private, commercial, or contractual questions | ShinySoft Technologies |
| You want to keep this maintained | Sponsor |
File an issue in the right repo
Section titled “File an issue in the right repo”Every library lives in its own repository, and an issue filed in the wrong one tends to sit there. Pick what you’re working with:
shinyorg/shinyBluetoothLE, BLE Hosting, Locations, Wi-Fi, Network Discovery, Jobs, Local Notifications, Push, HTTP Transfers, MAUI & Native Hosting, Configuration, Contacts, Calendar, Data Sync, Screen Recording, Live Activities
Or browse the full list
| Area | Repository |
|---|---|
| Shiny Core — device & background services | shinyorg/shiny |
| Mediator | shinyorg/mediator |
| Extensions — DI, Reflector, Serialization, Stores | shinyorg/extensions |
| UI Controls (MAUI & Blazor) | shinyorg/controls |
| DocumentDb | shinyorg/DocumentDb |
| Spatial & Geofencing | shinyorg/geospatialdb |
| HTTP Server | shinyorg/httpserver |
| MAUI Shell | shinyorg/mauishell |
| Speech & AI Conversation | shinyorg/speech |
| Face, Voice & Document Intelligence | shinyorg/recogintelligence |
| OBD | shinyorg/obd |
| Music | shinyorg/music |
| Health | shinyorg/Health |
| Aspire — Orleans & tunnels | shinyorg/aspire |
| Firebase — Firestore & FCM | shinyorg/firebase |
| Push (server side) | shinyorg/pushextensions |
| MSBuild Permissions | shinyorg/msbuildpermissions |
| Localization Generator | shinyorg/localizegen |
| MAUI for tvOS & macOS | shinyorg/mauiplatforms |
| Project templates (dotnet new) | shinyorg/templates |
| AI Skills | shinyorg/skills |
| This documentation site | shinyorg/documentation |
What makes a report actionable
Section titled “What makes a report actionable”Most reports that stall do so for the same handful of reasons. Include:
- Package name and version —
Shiny.BluetoothLE 4.1.0, not “the latest”. - Platform and OS version — iOS 18.2, Android 15, and whether it’s a simulator/emulator or a physical device. Several of these libraries wrap platform APIs that genuinely differ between the two.
- The .NET / MAUI version and your target framework.
- What you expected and what happened, with the full exception and stack trace if there is one.
- A repro. A small failing project is worth more than any description. If you can reproduce it against one of the samples, say which one and what you changed.
Security
Section titled “Security”Please don’t report security vulnerabilities in a public issue or on Discord. Use GitHub’s private advisory flow on the affected repository (Security → Report a vulnerability), which reaches the maintainers without disclosing the problem first.
Contributing
Section titled “Contributing”Fixes and improvements are welcome across every repo. If the change is substantial, open a Discussion or an issue before you write it — it’s the cheapest way to find out whether the approach fits before you spend the evening on it.
Building something with Shiny? It can be listed on Apps & Samples.