Hardware
Merchant Kiosk & Backoffice Platform
Senior .NET DeveloperThis project is relevant for clients who need hybrid desktop/web applications or operational systems tied to local hardware.
Overview
This project combined a Windows kiosk client, browser-based merchant portal, local peripheral integration, file/media processing, and ASP.NET MVC back-office features.
My role focused on making local hardware workflows work reliably with a web portal and backend API.
What The Platform Needed
The platform needed to support merchant onboarding and regulated operational workflows:
The main challenge was bridging a web experience with local Windows devices while keeping the client resilient enough for kiosk-style deployment.
- A browser-based merchant portal running inside a Windows shell
- Camera recording during transaction workflows
- Scanner capture and upload
- PDF printing
- Media transcoding and upload
- Offline-tolerant advert playback
- Self-update and restart behavior
- Back-office management screens
- API communication with token handling
My Backend And Desktop Work
I worked on a WinForms client using CefSharp to host the portal and expose JavaScript-to-.NET bridge methods. Those bridge methods triggered camera, scanner, printer, upload, advert, and update workflows.
I also worked on ASP.NET MVC back-office features with EF6, dependency injection, validation, and operational screens.
Key work included:
- WinForms shell around Chromium/CefSharp
- JavaScript bridge for web-to-device workflows
- Camera recording and ffmpeg transcoding
- WIA scanner integration
- PDF printing with PdfiumViewer
- FTP upload with resume and file-size verification
- REST API communication with token handling
- Offline advert caching and playback logging
- Disk-space guard, cache cleanup, and single-instance behavior
- Self-update/restart flow for deployed kiosk clients
Technical Highlights
- Desktop stack: C#, WinForms, CefSharp, WIA, PdfiumViewer
- Backend stack: ASP.NET MVC, EF6, SQL Server
- Media: camera capture, ffmpeg, FTP upload, file verification
- Device workflows: scanner, printer, browser-to-native bridge
- Operations: offline cache, update flow, logging, disk-space protection
Why This Project Is Relevant
This project is relevant for clients who need hybrid desktop/web applications or operational systems tied to local hardware.
It is useful for clients who need:
It shows practical experience building software that has to work outside a normal web-only environment, with real devices, local files, network issues, and operator workflows.
- Windows desktop development
- Kiosk applications
- Hardware/peripheral integration
- ASP.NET MVC legacy systems
- File/media upload workflows
- FTP or local file synchronization
- Self-updating desktop clients
- Back-office application development


