The ServeWay™ Roadmap
ServeWay™ Ministry Management Software was built for the everyday work of small and mid-size churches: check-in kiosks that print name labels, a Wall Calendar for the whole church, live streaming through OBS to MUX.com, YouTube, Facebook, or Vimeo, member texts and emails through Twilio and Brevo, Tithe.ly giving, and an optional WordPress plugin that brings member pages to your church website.
Where we are today: ServeWay™ is a Windows 11 desktop application, and it’s currently in beta. Churches using the beta are helping us shape every release.
Where we’re headed: We want ServeWay™ to reach more of your people on more of your devices, without losing the reliability and simplicity your staff and volunteers count on. This page explains what’s coming, what isn’t (yet), and why.
We don’t promise dates on this page. Plans are grouped as Now, Next, and Later so you can see the direction honestly while we focus on getting each step right.
What about phone apps?
This is one of the first questions we hear, so here’s a straight answer.
ServeWay™ does not offer native iPhone or Android apps right now. Here’s why:
- Church staff work happens at the office PC and at the kiosks. Running check-in, printing labels, managing the calendar, sending notifications, and running the live stream all happen on Windows computers at the church. That’s where ServeWay™ puts its effort.
- App stores add cost, review time, and maintenance. Each app store has its own developer fees, review process, and rules, and every iPhone and Android update can mean more testing and fixes. That’s two more platforms to build, test, and support.
- Staying focused keeps quality high. We’re a small team. Keeping our focus means fewer bugs, faster support, and features that actually work on Sunday morning.
What members can use today, and what’s planned
- Your church website works on any phone. With the ServeWay™ WordPress plugins, your church website’s member pages open in any phone browser. No app download needed.
- Texts and emails already reach members’ phones. ServeWay™ sends member notifications by text message (Twilio) and email (Brevo), so people get reminders and updates on the phone they already carry.
- Planned: “install” your church’s member pages like an app. We’re planning a feature that lets members add your church site’s member pages to their phone’s home screen, where it opens with its own icon like an app. This kind of web app is called a progressive web app. It may also support push notifications on phones and browsers that allow them.
- Native apps in the future? Maybe. We’ll consider native iPhone and Android apps down the road, based on what churches tell us they need.
Mac and Linux
Many churches ask whether ServeWay™ will run on a Mac, and a few ask about Linux. Mac and Linux support is on the long-term roadmap (see the technical section below). Here’s what the numbers tell us, and why Windows came first.
What the data shows
We looked for solid, church-specific numbers on which computers churches use. We couldn’t find a large, current, church-specific survey of Windows vs. Mac vs. Linux. So below we say which figures come from churches and which are proxies: general computer-use data that gives useful context but isn’t specific to churches.
Church-specific (small and dated):
U.S. desktop web traffic, September 2026 (StatCounter proxy data; see table and source below).
Proxy: all U.S. desktop and laptop web traffic (not church-specific):
| Desktop operating system (U.S., September 2026) |
Share |
| Windows |
64.5% |
| macOS (StatCounter reports “OS X” 17.7% + “macOS” 8.7%) |
26.4% |
| Chrome OS |
5.4% |
| Linux |
3.7% |
(Source: StatCounter Global Stats, Desktop OS Market Share, United States, monthly data for September 2026, retrieved Oct. 5, 2026. StatCounter measures page views on websites that use its tracking code, not devices sold or owned. Its U.S. Linux figure jumped for a few months in mid-2026 (17.8% in August 2026) and then fell back to 3.7% in September, so we use the most recent month and treat single-month spikes with caution.)
Proxy: small and mid-size organizations (not church-specific):
- In a survey of 900 IT decision-makers at organizations with up to 2,500 employees (U.S., U.K., and Australia, conducted Nov. 2024), the average device mix was Windows 56%, macOS 27%, Linux 20%. Windows was down from 63% six months earlier, and macOS was up from 24%. (Figures are as reported. Organizations can use more than one platform, so they don’t need to add up to 100%.) (Source: JumpCloud, SME IT Trends Report Q1 2025, published Jan. 2025)
What this means for churches
- Windows is still the most common desktop platform in every source we found. That’s why ServeWay™ started there, and it fits the touchscreen check-in kiosks and label printers that many churches use.
- Macs are a real and growing part of the picture. In the general data, macOS is roughly a quarter of U.S. desktop traffic and about a quarter of small and mid-size business devices.
- Many church media booths run on Macs. Church-tech writers note that ProPresenter, the popular worship presentation software, runs on both Mac and Windows, but the common advice in church-tech groups is “get a Mac,” and most tutorials and templates assume a Mac. (Sources: ChurchTechToday, “Choosing the Right Computer to Run ProPresenter”; Learn of Christ, “ProPresenter Review 2026”) So a lot of churches have Windows PCs in the office and a Mac in the booth.
- Linux is a smaller group, but it’s growing in some organizations, and supporting it comes almost free with the approach we’re taking.
The bottom line: supporting Mac (and Linux) will let ServeWay™ run on whichever computer your church already has, whether it’s in the office or the booth.
Technical section: how we'll get to Mac and Linux
This section is for church IT volunteers, tech directors, and anyone curious about what’s under the hood.
Today’s architecture
ServeWay™ is written in C# on .NET as a Windows Forms (WinForms) desktop application, with a MariaDB or MySQL database. Like many WinForms apps, a lot of business logic lives right inside the forms’ code-behind: button click handlers that validate input, query the database, and update the screen all in one place. That works well on Windows, but WinForms only runs on Windows, and logic tied to a form is hard to reuse or test.
Where we’re going: MVVM on Avalonia UI
Avalonia UI is an open-source, cross-platform UI framework for .NET. One C# codebase can produce desktop apps for Windows, macOS, and Linux. Avalonia is built around the MVVM (Model-View-ViewModel) pattern:
- Model: the data and business rules (members, check-ins, events, gifts).
- View: the screen layout, written in XAML (AXAML in Avalonia).
- ViewModel: plain C# classes that hold a screen’s state and commands. They know nothing about buttons or windows, so they can be unit-tested and reused on any platform.
A phased approach, with Windows working the whole time
We won’t stop and rewrite everything. Each phase ships, and the Windows build keeps working at every step.
- Separate the logic from the forms. Move business logic and data access out of form code-behind into services (for example, check-in, calendar, notifications, giving, and streaming services) and repositories for database access. Add dependency injection so components are wired together instead of hard-coded.
- Introduce MVVM gradually inside the current WinForms app. Create view models for existing screens and bind WinForms controls to them where it makes sense. The forms become thin, and the logic becomes testable. The WinForms Designer stays in use for the Windows version during this whole period.
- Abstract platform-specific features behind interfaces (see the list below), with a Windows implementation first and macOS/Linux implementations added later.
- Port screens to Avalonia. Build Avalonia views on top of the same view models and services, screen by screen. Kiosk and check-in flows, the Wall Calendar, and admin screens can each move on their own schedule.
- Test and release on each OS. Run automated tests (unit tests on view models and services, plus UI tests where practical) and hands-on testing on Windows 11, current macOS, and mainstream Linux distributions, with real kiosk hardware and printers, before calling any platform ready.
What stays the same
- C# and .NET. Same language, same runtime, and a shared codebase.
- Your database. Same schema and the same data in your MariaDB or MySQL database. Moving to Avalonia won’t require moving your data to a new database. (Separately, PostgreSQL support is planned as an extra database option. See Now / Next / Later.)
- The same features. Check-in and label printing, the Wall Calendar, OBS streaming to MUX.com/YouTube/Facebook/Vimeo, Twilio and Brevo notifications, Tithe.ly giving, and the WordPress plugins.
- Cloud integrations. Twilio, Brevo, MUX.com, Tithe.ly, and WordPress are reached over the network, so they work the same way on any operating system.
Platform-specific pieces to replace or abstract
| Area | Today (Windows) | Plan |
|---|
| Office documents and exports | Microsoft Office COM interop (Windows-only) | Replace with cross-platform .NET document libraries (for example, for spreadsheets and PDFs) behind an export service, so no Office install is needed |
| Printing and label printers | Windows printing APIs and Windows printer drivers | A printing interface with per-OS implementations; support label printers through each OS’s print system or the printer’s native command language where available |
| Touchscreen kiosks | Windows touch input and calibration | Use Avalonia’s built-in touch/pointer input; handle calibration and kiosk lockdown per OS, with a documented setup for each |
| OBS streaming | Windows install paths and process control for OBS | Detect OBS per OS, and prefer OBS’s WebSocket control interface over file paths so it behaves the same everywhere |
| Settings and configuration | Windows Registry and Windows-specific folders | Move to JSON-based settings files in each OS’s standard app-data location, with a one-time migration from the Registry |
| File paths, fonts, and shell integration | Windows path conventions and Windows-only APIs | Use .NET’s cross-platform path and environment APIs; review every Windows-specific API call |
| Installer and updates | Windows installer | Native packages for each OS (for example, a signed and notarized Mac app; common Linux package formats) |
The WinForms Designer isn’t going away yet
Until each screen is ported to Avalonia, the Windows version keeps using WinForms and the WinForms Designer. Churches on Windows will keep getting updates and fixes during the transition. The switch to Avalonia on Windows happens only after a ported screen is tested and works as well as the original.
Now / Next / Later
Tell us what matters to your church
This roadmap is shaped by the churches using ServeWay™. If a feature would make Sunday morning (or Monday at the office) easier for your team, we want to hear about it.
Roadmap items are plans, not promises, and may change based on feedback and testing. Statistics on this page were retrieved on October 5, 2026, from the sources linked above.