01 / Service
New POS app on .NET MAUI
A retail, restaurant or field POS app built in .NET MAUI from the start, planned around the devices you chose.
.NET MAUI POS apps that talk to your hardware.
Our POS apps take payments on PAX, Clover and MagTek devices, print on Star receipt printers, and scan with Zebra and Chainway handhelds. We write the C# layer between each device SDK and your screens. Our senior engineers work US business hours.
3 payment brands we work with:
PAX, Clover, MagTek
PAX, Clover, MagTek
2 apps a UWP app and an iOS app
in one .NET MAUI codebase
in one .NET MAUI codebase
The POS hardware our .NET MAUI apps talk to.
Device not listed? Bring the model and the SDK name to a feasibility call.
Payment terminals [pax · clover · magtek]
POS apps that run on PAX and Clover payment terminals. Phone and tablet apps that use MagTek card readers over Bluetooth or USB, on Android and iOS.
Receipt printers [star · built-in]
Receipts print on Star printers, or on the printer built into the payment terminal. Your screens call one C# print service.
Barcode scanners [zebra · chainway · camera]
Zebra and Chainway rugged handhelds with built-in scan engines, and camera scanning on phones and tablets.
POS tablets and platforms [android · ios · windows]
Android terminals and handhelds, iPhones and iPads, and Windows PCs, from one .NET MAUI codebase.
What .NET MAUI POS app development covers.
02 / Service
Payments in your existing .NET MAUI app
Your .NET MAUI app needs card payments. We add the PAX, Clover or MagTek SDK to the checkout screens you already have.
03 / Service
Printers and scanners
Vendors often ship printer and scanner SDKs only for Android or iOS. When they do, we write the native SDK binding for .NET MAUI. Then we write the C# service your screens call.
04 / Service
Xamarin or UWP POS to .NET MAUI
Your POS runs on Xamarin.Forms or UWP. We move it to one .NET MAUI codebase. See our Xamarin and UWP to .NET MAUI migration services, or the Google Play and App Store deadlines for a Xamarin POS app.
A restaurant POS we moved to .NET MAUI.
Instead of redesigning how the app moves between screens, we kept the UWP navigation inside .NET MAUI.
01 2025–2026
A UWP restaurant POS and its iOS app, moved to one .NET MAUI codebase.
NorthStar's Order Entry was two apps: UWP on Windows and a separate iOS app. We moved it to one .NET MAUI codebase on .NET 10 that builds for iOS, Android and Windows. Their team kept adding UWP features the whole time, so we kept view models close to the originals.
2 apps
one .NET MAUI codebase
85%
view models reused
~8 months
migration, three phases
.NET MAUI.NET 10C#UWP migration
Need a POS app that talks to your devices? Bring the device model and the SDK name.
Can you support my device?How POS hardware fits in a .NET MAUI app.
The screens are usually the easy part. Most of the work is in the device SDKs.
PAX and Clover app development in .NET MAUI
Clover devices and PAX's Android terminals run Android apps. So a .NET MAUI app can run on the terminal itself and call the Clover SDK or the PAX SDK from C#.
Payment terminal integration in .NET MAUI
Your app can also run on a phone or tablet, with a MagTek card reader connected over Bluetooth or USB.
In both cases your app sends the amount and gets back a result, such as approved or declined. We write the C# layer between the SDK and your checkout screen. Many payment SDKs ship only as an Android or iOS library, and .NET MAUI needs a binding to call them. That is our native SDK binding service for .NET MAUI.
Receipt printers in a .NET MAUI POS app
A separate receipt printer, like a Star Micronics printer, connects over Bluetooth, USB or the network, depending on the model. Some payment terminals have a printer built in, and the terminal's SDK prints on it. Each printer SDK formats receipts in its own way, so we put printing behind one C# service your screens call.
Barcode scanners on rugged handhelds
Zebra and Chainway handhelds have a built-in scan engine, and each vendor sends scans to the app in its own way. Phones and tablets can use the camera. We put these differences behind one scanning service, so your screens work the same on every device.
One codebase, with a build per device family
Screens, business rules and data stay in one C# codebase. Hardware code sits behind interfaces, with one implementation per device family. When a vendor needs its own app build, we make a separate build from the same code.
Restaurant POS apps on iOS, Android and Windows
A restaurant POS often runs on more than one kind of device: a Windows station, a tablet and a handheld. .NET MAUI builds all of them from one C# codebase. Our migration tracker for NorthStar's Order Entry counted 143 UI items in scope: 18 pages, 47 views and 78 dialogs.
Testing on the real device
An emulator can't read a card or print a receipt. So our senior .NET MAUI experts test on the device models you ship. If your POS app works but is slow on a low-cost terminal, see our .NET MAUI performance optimization work.
From one device question to a working POS app.
One SDK on one device first, then the full build.
01 ───
Feasibility call
Bring the SDK name and the device model. We tell you what we know and what we still need to check.
SDK + model
02 ───
Binding spike
Fixed scope: one SDK bound and running in a sample app on the real device.
One device
03 ───
Build or migrate
A new POS app, hardware added to your .NET MAUI app, or a Xamarin or UWP POS moved to .NET MAUI.
Your codebase
04 ───
Test on devices and roll out
We test payments, printing and scanning on each device model, then prepare the release builds.
Real hardware
Questions about POS apps and hardware.
Q.01
Both work with .NET MAUI. The POS app can run on a Clover device or a PAX Android terminal and call the payment SDK there. With a MagTek card reader, the app runs on a phone or tablet and connects to the reader over Bluetooth or USB.
Q.02
.NET MAUI builds for Android, iOS, Windows and Mac from one C# codebase. For a POS, the devices decide. Clover devices, PAX Android terminals and the Zebra and Chainway handhelds we work with all need the Android build. MagTek card readers work with Android and iOS.
Q.03
Yes. We add the printer or scanner SDK to your app behind a small C# service. If the vendor ships only an Android or iOS library, we write the binding first. See how we bind a vendor SDK to .NET MAUI.
Q.04
Yes. We have moved Xamarin.Forms apps to .NET MAUI. In one of them, the original binding code was lost, so we rebuilt the iOS and Android bindings for a third-party SDK. Start with moving a Xamarin POS app to .NET MAUI.
Q.05
For payments, printing and scanning, yes. The binding spike ends with the SDK running in a sample app on the real device. Bring the device model to the feasibility call.
Which device does
your POS app need to talk to?
// reach-us
contact@lemonlabs.mx +1 (779) 232-9848 Av. de los Diamantes 53–9
Residencial Esmeralda Nte.
28017 Colima, Colima, México