Kiosk Software Development

Kiosk software runs on three main hardware families: iPad enclosures (10.2" to 12.9" iPads in wall-mounted or floor-standing enclosures), Android touch panels (typically 10", 15", or 21" commercial-grade units from manufacturers like AOPEN, Elo, or Zytronic), and Windows-based kiosk enclosures (running Windows 10/11 IoT or Windows 10 Pro with Assigned Access). The right hardware depends on the use case: iPads are common for hotel check-in and event registration, Android panels for information directories and restaurant ordering, and Windows units for applications that require USB peripherals like barcode scanners, card readers, and thermal printers. We scope hardware alongside software so both work together.

On iOS, we use Guided Access to lock the device to a single application, disable hardware buttons, restrict touch zones, and prevent sleep or screen-off. On Android, we configure kiosk mode via Android Device Policy Manager (COSU profile) or a dedicated MDM solution like Hexnode or Scalefence, which pins the application and disables the home button, recent apps, and notifications. On Windows, we configure Assigned Access (single-app kiosk mode) so the device boots directly into the application and the user cannot reach the desktop, taskbar, or settings. In all cases, we also configure auto-restart on application crash so a software fault brings the kiosk back up within seconds without a staff member pressing a button.

A simple kiosk application with a single flow, no payment integration, and basic content management runs $15,000 to $25,000. Add payment hardware integration (Stripe Terminal, PAX device), receipt printing, and offline queuing, and the range moves to $30,000 to $50,000. A full kiosk suite with ordering, KDS integration, fleet management CMS, and remote monitoring across multiple locations runs $50,000 to $80,000 or more. Hardware cost is separate and depends on the enclosure, screen size, and peripheral devices. We scope every project against the specific hardware and flow requirements before pricing.

A single-flow kiosk application with no payment integration takes six to ten weeks from brief to production-ready build. Payment integration adds two to four weeks depending on the hardware and certification requirements. A full suite covering multiple kiosk types, a CMS for remote content updates, and fleet monitoring takes three to five months. The main schedule drivers are hardware lead time (commercial kiosk enclosures can have four to eight week lead times), payment hardware certification, and the number of edge cases and failure states to handle in the application logic.

Yes, and for most kiosk deployments this is a hard requirement. A kiosk in a hotel lobby or a retail floor cannot tell a guest to come back when the network is fixed. We build offline resilience into the application from the start: local transaction queuing so orders and check-ins are captured and synced when the network returns, read-only data cached locally so menus, room availability, and product data are available without a live API call, and graceful fallback screens that show the user what is happening rather than a spinner or error. For payment transactions, the handling depends on the payment provider: Stripe Terminal and Square Terminal both have offline payment modes with transaction limits and risk controls.

Hospitality is the most common: self-check-in kiosks in hotels, resorts, and short-term rental properties reduce front desk load and let guests check in at any hour. Retail uses self-checkout kiosks and product information directories. Healthcare uses patient intake kiosks for registration, insurance capture, and consent form signing, reducing front desk queues. Restaurants and food service use ordering terminals to increase average order value and reduce queue length at the counter. Events and entertainment use registration kiosks for wristband printing and attendee lookup. Airports and transport hubs use information directory kiosks. Each industry has specific compliance requirements: healthcare intake must handle PHI carefully, payment kiosks must meet PCI DSS requirements, and age-verification kiosks in some sectors must integrate ID scanning.