Skip to content

App development

Native apps for the phone and the desktop.

Vuewer builds mobile apps for iOS and Android and desktop apps for macOS and Windows, connected to the same back end as your website. One senior engineer handles the design, the app, the API behind it, store review and every update after launch. Camerture, a Mac app we designed and built, works this way.

What we build

Apps worth installing.

Most ideas do not need an app, and we will say so. These are the ones that do.

Companion apps for a platform
Your customers already use your web platform. The app gives them the parts they need on the move, with push notifications and one account shared with the website.
iOS and Android
Field and operations apps
Checklists, inspections, scanning and photos for teams who work away from a desk, stored offline and synced once there is signal again.
iOS and Android
Desktop utilities
Small, focused tools that live in the menu bar or the dock and talk to hardware: cameras, files, printers. Camerture is one of them.
macOS and Windows
Internal tools on the desktop
Software your team keeps open all day, where a browser tab is not enough: keyboard driven, fast, and working with local files.
macOS and Windows
Your own product
From first version to the store, with accounts, subscriptions and the back end to run it, built so the next developer can take it over.
Every platform

01 Mobile apps

Native on iOS and Android.

Apps that feel at home on the phone they run on, connected to the same back end as your website.

booking app native

Book a class

November

Available times

12:00 Full
Confirm 10:30
The same app, native on each platform. Tap a day and a time.
  • Native feel on each platform

    Navigation, gestures and controls that follow each platform, not one design stretched over both.

  • One back end for every client

    The app, the website and the admin panel share one API, so a change lands everywhere at once.

  • Offline and push

    Work that survives a dead zone, and notifications people are glad to get.

  • Through review, onto the store

    Signing, store listings, review and staged releases handled, not discovered at the end.

  • Updates after launch

    New operating system versions tested before your users find the problem.

App development

02 Desktop apps

Mac and Windows, done natively.

Some software belongs on the desktop: close to the camera, the file system and the menu bar. Camerture, a Mac app we designed and built, works this way.

menu bar app native
Today 2:47 Tracking

Client portal

Invoice export

01:24:36

Synced just now ⌥⌘T
Lives in the menu bar and keeps time in the background. Pause it, or switch project.
  • Native Swift on the Mac

    SwiftUI and AppKit, so the app behaves like the rest of macOS instead of a web page in a window.

  • Hardware and system access

    Cameras, files, the menu bar and background work, with the permissions the operating system expects.

  • Signed, notarised, updated

    Code signing, notarisation and automatic updates set up properly from the first release.

  • Windows when your users are there

    Packaged and signed for installation and updates, with the same care as the Mac version.

  • Connected to your platform

    Accounts, licences and sync through your own API, not a third-party service you cannot leave.

App development

The stack

Native where it counts.

Chosen per project by what the app has to do and what it will cost to maintain, and written down before we start.

Apple
Swift and SwiftUI for iOS, iPadOS and macOS, with UIKit or AppKit where SwiftUI is not enough.
Android
Native Android apps that follow Material conventions for navigation, controls and notifications.
Windows
Desktop apps for Windows when your users are on it, packaged and signed for installation and updates.
Shared code
One codebase across platforms when the app is mostly forms and lists, and the budget matters more than the last details of polish.
Back end
Laravel APIs for accounts, sync, subscriptions and push notifications, shared with your website and admin panel.
Release
Code signing, notarisation, TestFlight, App Store and Google Play review, and staged rollouts.

What you get

Shipped, not just built.

An app is finished when it is on someone's phone and can be updated safely. Every project is delivered to that point.

Store accounts in your name
Apple and Google developer accounts, certificates and listings registered to you from day one.
A test build every week
TestFlight and internal test tracks, so you use the app on your own device while it is being built.
One API for every client
The app, the website and the admin panel share one documented back end.
Crash and performance reports
Crashes and slow screens reported from real devices, so problems are found before the reviews mention them.
Store review handled
Screenshots, privacy labels, review notes and the back and forth with the review team.
An update plan
New operating system versions tested before release, and dependency updates on a schedule.

When not to

When you do not need an app.

An app is a commitment to every operating system release that follows it. These are the reasons we talk people out of one.

A website would do
If people use it once a month, a fast mobile website is cheaper to build, needs no review and updates the moment you publish.
Nobody will install it
An app has to earn a place on the home screen. If the reason to open it is weak, the download numbers will say so.
The budget covers one platform
Two half-finished apps are worse than one good one. Start where your users are and add the other platform later.
Nobody will maintain it
Every operating system release can break something. An app without an update budget slowly stops working.

FAQ

Questions worth asking.

Do you build native mobile and desktop apps?

Yes. Mobile apps for iOS and Android and desktop apps for macOS and Windows, connected to the same back end as your website. On Apple platforms we write native Swift; Camerture, a Mac app we designed and built, is one example. Whether a project is native on each platform or shares one codebase is decided per project, by what the app has to do and what it will cost to maintain.

Do you handle App Store and Google Play releases?

Yes. Code signing, store listings, screenshots, privacy declarations and review are part of the project, and the apps are published under developer accounts registered to you, so they stay yours. Review time is planned into every release rather than discovered at the end.

Do you do design as well as development?

Yes. Interface and interaction design are done in-house, which is why nothing gets lost in a handover between a design agency and a developer.

Who owns the code?

You do, in full, on final payment. It lives in your repository, with documentation good enough for another engineer to pick it up. We do not build in dependencies on ourselves.

Do you handle maintenance after launch?

Yes, on an optional monthly retainer that covers dependency and security updates, monitoring, backups and a set amount of development time. Without a retainer we are still available hourly, just not on a guaranteed response time.

Field notes

Written about this.

Mobile and desktop apps 4 min read

Do you need an app, or a fast website?

An app has to earn its place on the home screen and costs more every year it exists. Five questions that show when a fast website does the job instead.

Mobile and desktop apps 5 min read

Native or cross-platform: how we decide

Native code for each platform or one shared codebase? The four questions that settle it, what each option costs to maintain, and where the back end fits.

Get in touch

We'd love to hear from you.

Do you have a question or need help with a website or web application? Whether you are starting from scratch, refining what you already have, or stuck on something complex.

Fill in the form and we'll get back to you as soon as possible.