Service App Available

Mobile and desktop applications

I build mobile and desktop applications that make proper use of the device without turning every platform into an entirely separate project.

Applications for Android, iOS, Windows, Linux and macOS, with a foundation shaped around the product and the device features it actually needs. Development from Galicia and remotely.

The right format

Not everything needs an app.

The first decision is not the technology, but where and how the product will be used. Sometimes a good installable website solves more at a lower cost.

01
Web or PWA

For immediate access from any device, centralised updates and features that do not depend on deep operating-system integration.

02
Mobile application

For frequent use on the move, camera, location, notifications, local data or an experience designed around the phone.

03
Desktop application

For working with files, local processes, peripherals, updates or intensive workflows on Windows, Linux and macOS.

The architecture

Share the foundation without ignoring the device.

A cross-platform solution can reduce cost and maintain consistency. When a feature needs specific integration, that part is treated as native rather than forced through an abstraction.

01 / Shared

A cross-platform foundation

For products that share an interface, data and rules across several systems and do not need a completely separate implementation for each one.

  • Less duplication across platforms and releases.
  • Consistent behaviour and design on every device.
  • A foundation that is easier to test, maintain and evolve.

02 / Specific

Native integration where it matters

For features that depend on the operating system, hardware or a level of performance that a shared layer cannot provide well.

  • Access to files, notifications, camera or system processes.
  • Behaviour adapted to the constraints of each platform.
  • Specific code only where it provides a real advantage.

How I work

From use case to installed application.

Platform, distribution and synchronisation decisions are made before release. Improvising them once the app is finished tends to be an expensive hobby.

  1. 01

    Define the usage context

    We establish who uses it, on which device, how often and what they must be able to do with or without connectivity.

  2. 02

    Prototype the workflows

    I organise screens and interactions to validate the main journey before investing in the most expensive integrations.

  3. 03

    Integrate and test

    I develop the application and test permissions, data, performance and behaviour on real devices and operating systems.

  4. 04

    Distribute and update

    I prepare installers, store releases or private distribution, together with a clear strategy for errors, versions and updates.

Real work

Applications and foundations designed for several systems.

VS Launcher brings installation and updates to the desktop; xvelte provides a shared foundation for building web interfaces and applications with Tauri.

Pantalla principal de VS Launcher cunha instalación de Vintage Story preparada para xogar
01
VS Launcher

Un launcher non oficial para instalar e manter varias versións de Vintage Story, separar mundos e mods e protexer cada partida con copias de seguridade.

Captura da páxina principal da documentación de xvelte
02
xvelte

Unha colección persoal de compoñentes, hooks, attachments, estilos e utilidades reutilizables para construír interfaces con SvelteKit.

Frequently asked questions

Reasonable questions before we begin.

Native or cross-platform application?

It depends on features, performance and target platforms. A shared foundation avoids duplicated cost when it suits the product; where a feature requires native code, I do not force it through an abstraction.

Do you also publish to app stores?

I can prepare builds, listings and the publication process. Apple, Google or Microsoft accounts should remain in the client's name and their fees are billed directly.

Can it work offline?

Yes, if the use case requires it. We need to define what is stored, how it synchronises and what happens when conflicting changes meet after connectivity returns.

How much does an application cost and how long does it take?

It depends on the platforms, native features, backend, integrations and publication process. I first define a useful version and prepare a phased estimate rather than pricing it solely by screen count.

Can you also build the backend or API?

Yes. If the application needs accounts, synchronisation, shared data or a management dashboard, I can build or integrate the required server-side work within the same project.

How are updates and maintenance handled?

It depends on distribution: official stores, a built-in updater or internal installation. I can handle support and new releases while keeping accounts and access under your control.

Contact

Shall we talk about your next project?

Got an idea, a website in need of a renovation or a computer that only works when the technician turns up? Tell me about it. I will explain clearly what can be done, whether it makes sense and what the next step would be.

Right now

Available for selected projects, collaborations and technical enquiries.

Usual response time
1–2 working days
Location
Salvaterra de Miño, Galicia