Sharp Open Systems Architecture, abbreviated OSA, is the platform that lets a Sharp MX or BP-series multifunction device run office applications on its panel. The platform launched in 2003 alongside the first MX-series chassis and has reached version 6.5 in the 2026 release. Through OSA, the Sharp panel becomes a thin client for cloud storage, Microsoft 365, Google Workspace, accounting software, ERP scan workflows, healthcare ID capture, and custom-developed apps. This guide explains the architecture stack, the API surface, the app library Spanish offices see most often, the developer workflow for custom apps, and how OSA reads against rival panel platforms.
The tile-based home screen the office user touches. Synappx, Microsoft 365 sign-in, Google Drive shortcut, custom app icons sit here.
The OSA app code itself. JavaScript, HTML5, and CSS that defines the panel screens, button flows, and integrations.
The documented APIs apps call to scan, print, fax, access user identity, write to network folders, or trigger device functions.
The web server inside the device that serves the OSA framework, hosts app code, and brokers between the panel and the engine board.
The print engine controller. Handles paper path, toner, fuser, scanner. OSA never directly accesses this layer; it asks layer 02 for engine functions through documented requests.
Sharp publishes a documented REST and SOAP API set that covers every panel-side function an app can invoke. The most-used APIs across the Spanish app catalogue are listed below. Each row carries the API name and a one-line description of what an app can do with the call.
App tells the engine to scan, with resolution, format, colour mode, paper size, single or duplex. Returns the scanned file as a stream or as a URL on the embedded server.
App submits a PDF, TIFF, or PCL stream to the engine for printing. Supports duplex, stapling, hole-punch, and finisher options on the BP-series.
App composes a fax with destination, cover sheet, content from scan or upload, and submits to the fax queue.
App reads the panel-side user identity, including Active Directory username, group memberships, and any custom attribute mapped through the directory connector.
App writes a file to SMB, FTP, SharePoint, OneDrive, Google Drive, Dropbox, or Box. Sharp ships connectors for the major destinations; custom connectors run through the SDK.
App declares a screen layout in HTML5 and CSS. Sharp panel renders it inside the OSA frame. Touch events come back through the panelUI event bus.
App writes its own event into the device audit log alongside the engine events. Useful for compliance reporting on app-mediated jobs.
App reads toner level, paper level, jam status, and recent service codes. Used by fleet-management apps and by Synappx Manage.
Sharp publishes an app marketplace that runs to roughly 80 vetted apps in 2026. The selection below covers the apps that appear on more than 40 percent of Spanish OSA deployments. Each card shows the app name, category, and a one-line use case.
One-tap scan to Google Drive, SharePoint, OneDrive, Dropbox, or Box. Pre-loaded on every MX-series unit.
Scan to email with the signed-in user as sender. PDF, PDF/A, TIFF, JPEG output formats.
Intelligent capture with classification, extraction, and routing to ECM. Top-three app on Spanish corporate deployments.
Card-release printing, per-user quotas, audit log. Dominant in education and public sector.
Cloud or on-premise pull-print release. Common on Spanish distributed-office fleets.
Cost recovery, scan billing, and project codes. Used by Spanish law firms and accountancy practices.
Direct scan into DocuWare cabinets with metadata. Spanish corporate document management deployments.
Scan in Spanish, output in 30+ languages. Pricing per page; sold through Sharp channel.
Scan a Spanish DNI or healthcare card on the platen; OCR strips identifier fields and routes to EHR. Used by Spanish clinics.
Map office workflow, panel screens, API calls.
Install Sharp OSA SDK, sample apps, simulator on a developer laptop.
Code app screens, wire APIs, test in simulator.
Submit JAR to Sharp for signing. Required for production deployment.
Push signed app to fleet via Sharp Net Admin console.
Spanish dealers including fotocopiastrebol partner with a handful of local development shops that handle custom OSA development on behalf of corporate customers. The typical build runs 6 to 16 weeks depending on the integration depth, with budgets between 6,000 EUR for a simple scan-routing app and 35,000 EUR for an ERP-integrated capture workflow with classification.
OSA competes with five rival panel platforms: Kyocera HyPAS, Canon MEAP, Konica Minolta OpenAPI, Ricoh Smart Integration, and Xerox ConnectKey. Each platform has roughly the same goal: turn the multifunction panel into a thin client for office workflows. The table compares the five against the OSA reference.
| Platform | Vendor | App language | App count | Spanish ecosystem strength |
|---|---|---|---|---|
| OSA | Sharp | HTML5 + JS + REST/SOAP | ~80 vetted | Mid · strong in education and public sector |
| HyPAS | Kyocera | Java + JAR signing | 120+ vetted | Strong · broadest in private sector |
| MEAP | Canon | Java + iWAM | ~90 | Strong · large enterprise presence |
| OpenAPI | Konica Minolta | HTTP + SOAP + WS | ~60 | Mid · grew through Workplace Hub push |
| Smart Integration | Ricoh | Cloud-hosted apps + Smart Workflow | ~50 | Mid · @Remote integration story |
| ConnectKey | Xerox | HTML5 + REST | 120+ | Strong · cross-sold with Xerox managed contracts |
From the Spanish dealer base, three scenarios come up where OSA carries a clear advantage over the alternatives. The first is education, where the Sharp-published Teaching Assistant app pairs with the OMR scanning hardware to mark assessment sheets at scale; no rival platform ships an OMR app of comparable maturity. The second is healthcare, where the Sharp ID Capture app handles Spanish DNI and Tarjeta Sanitaria cards with field extraction tuned for the Iberian format; rival platforms cover the same workflow with third-party apps that demand more setup. The third is hybrid meeting rooms, where OSA pairs natively with Sharp BIG PAD displays and Synappx orchestration; no rival platform integrates with a touch-display product line at the same depth.
OSA also loses ground in two specific scenarios. The first is per-app pricing transparency: Sharp lists partner-app pricing through dealer quotes rather than published list, which slows the procurement cycle for smaller offices used to web-priced marketplaces. The second is developer community size: the OSA developer pool sits behind Kyocera HyPAS and Xerox ConnectKey in raw size, so the supply of available Spanish-language SDK help is thinner. Offices with strong in-house development teams notice the gap; offices outsourcing all custom work to a Sharp partner shop see less impact.
OSA ships pre-enabled on every BP-series device sold since 2019. On older MX-series units, OSA may be licensed but switched off; the Sharp dealer can enable it from the web admin UI in five minutes given the licence key. Once enabled, the device exposes the OSA app drawer on the panel, and the admin can push apps from Net Admin or install them directly through the panel for testing.
For Spanish buyers placing OSA in the wider Sharp story, the MX series overview covers the print engines that run OSA on the panel; the Synappx integrations guide covers the orchestration layer that builds on top of OSA. For broader app-platform context across the Japanese majors, the Kyocera HyPAS marketplace guide covers the strongest rival platform in the Spanish market.