Most microscope suppliers stop at the hardware. We go further — branded mobile apps, measurement suites, embeddable SDKs and the ISP tuning that makes the image worth having in the first place. Built by the same team that designed the sensor chain, not bolted on afterwards.
A complete Android APK or iOS application carrying your identity: icon, splash screen, UI kit, capture workflow, measurement tools and export options — packaged and ready for your distribution channel or the stores.
Windows and macOS applications for the bench: calibrated measurement, multi-window compare, timed and batch capture, annotation and export — white-labelled end to end, or built new around your workflow.
For teams with their own product: device control, live streaming, still capture and the measurement engine exposed as documented APIs — so your developers embed imaging without touching firmware.
The service most suppliers cannot offer: sensor and ISP parameter tuning — exposure, white balance, denoise, sharpening, colour science — until your images are clean and repeatable, not just occasionally impressive.
Every engagement ends with the same thing: files you can install, submit or ship — not a demo link and a promise. Scope is fixed in the written brief; the table below is what a typical cross-platform programme delivers.
| Android | Signed APK + Play-ready AAB — your keystore, icon, splash and store assets |
| iOS | IPA build, notarised for App Store submission or enterprise distribution |
| Windows | Signed installer (EXE / MSI, 64-bit), silent-install option for fleet deployment |
| macOS | Signed and notarised DMG / PKG — universal binary for Apple Silicon and Intel |
| Linux | DEB / AppImage packages for lab and industrial workstations |
| Web | Browser application (HTML/JS, optional WASM pipeline) — capture and measurement, no install |
| SDK / API | DLL · SO · Apple framework · Android AAR · npm package, with sample code and integration guide |
| Image quality | ISP tuning profiles locked per product SKU, plus the tuning report behind them |
| Documentation | Build instructions, API reference, licence inventory and maintenance notes |
| Contract terms | IP ownership, source escrow, warranty and 12-month maintenance — agreed before development starts |
Software engagements fail on ambiguity, not difficulty. Ours start with a written brief and a prototype you can put your hands on, then move through milestones you can see — builds, not status emails.
You resell our hardware under your name and need the app to match — same product on the shelf as your competitors, a different experience inside it.
Consultation forms, zone definitions and patient-file exports built to your clinical process — deployed identically across every location.
Your product needs eyes. You take our SDK, keep your UI and codebase, and ship imaging as a feature of your own system.
Whatever the contract says — and we write it down before development starts. Options include full IP transfer of the custom application to you, a perpetual licence, or source escrow. The imaging core itself typically remains licensed; the layer built for you is yours by agreement. No surprises at handover.
Sometimes. If your devices use a standard camera class (UVC), an SDK integration is usually straightforward. Proprietary protocols need evaluation — send the model and a sample if possible, and we will answer honestly about feasibility.
Selectively and transparently. We track licence obligations per project — copyleft components are avoided in proprietary deliverables unless you explicitly accept the terms. The licence inventory ships with your handover pack.
A white-label reskin of our proven imaging app is the fast path — typically a few weeks from brief to store-ready packages. A fully custom workflow application runs on milestone schedules set at the brief. We quote a specific timeline after the prototype gate, not before we understand the problem.
Yes. We hand over packages that install cleanly under your own Apple or Google developer account, with the store assets prepared — or we can handle submission on your behalf. One honest caveat: if the app is intended for clinical diagnosis, the regulatory obligations (for example medical-device or data-protection rules in your market) sit with you as the publisher. We support that work with technical documentation, but we will not pretend it disappears.
Describe the workflow — an engineer from the software team replies, not a sales script.
We verify every new contact. Enquiries are checked against a real company name and website before we quote — that is why we ask for your company details below. Marketing, SEO and web-design pitches are declined; genuine buyers get a reply within one business day.
