Desktop Apps
Business software for Windows and macOS that runs without a browser. It talks directly to receipt printers and barcode scanners, and keeps working offline.
Who this fits
- Shops and warehouses with receipt printers or barcode scanners the browser cannot reach
- Sites where work must not stop when the connection drops
- Companies where each PC holds its own Excel file and nobody knows which one is current
How far we take it
Included
- Signed Windows and macOS builds
- Device integration for receipt printers, barcode scanners, and similar hardware
- Local storage that keeps working offline and syncs when the connection returns
- An auto-update distribution channel
- Install guide and an internal rollout procedure
- Handover of code and signing certificates
Not included
- Code signing certificate fees
- Hardware purchases and driver licenses
- On-site installation on each PC and staff training
- Building the internal network or servers (see in-house infrastructure)
Build cost by scope
| Scope | Build cost |
|---|---|
| Start smallCore features only | ₩6M~11.6M |
| StandardTypical scope | ₩9.5M~16.5M |
| LargeMany screens, complex | ₩13.7M~20M |
These are example ranges. Once requirements are confirmed you get a fixed quote. Maintenance is billed separately as a monthly plan.
These figures are current as of August 2026. The latest ranges are on the pricing page.
How it runs
- 01
Discovery
We define the core user problem and align on scope and priorities.
- 02
Design
We design the structure and flows, validating fast with prototypes.
- 03
Build
We build maintainable systems with tests and code review.
- 04
Launch
We ship reliably with release automation and store submission.
- 05
Operate
We operate long-term with observability, logs, and metrics.
Frequently asked questions
Only the platform you actually use on site. One codebase produces both, so adding the other later does not mean rebuilding. Device integration does need checking per operating system, so tell us up front if you plan to use both.
It saves to the device first and uploads when the connection returns, so entry and printing keep working while you are offline. If several people edit the same records at once, we need to agree on conflict rules first. Those rules differ by workflow, so we decide them together.
Usually web is better: nothing to install and updates land immediately. A desktop app earns its place in three cases: you must drive hardware the browser cannot reach, it has to run without internet, or it reads and writes local files heavily. If none of those apply, we will recommend web.
No. We set up an auto-update channel, so the app fetches and applies new versions on launch. Only the first install is manual. The initial rollout and certificate renewal do need someone to know the steps, so we document them.
A vague scope is fine
Tell us where things stand and we will point to the scope you need and a rough size.