Cantürk Çelikok
Desktop and cross-platform

Desktop applications that install easily and keep themselves up to date

Desktop software rarely loses users because of a missing feature. It loses them to a painful installer, an antivirus warning or an old version that never updates. A desktop product succeeds as much through distribution and updates as through the code itself.

I built Nerdesin as a Windows app that installs in minutes, without an account and without jailbreaking the phone. The installer, the auto-update flow and release distribution were designed as part of the product.

What you get

Installer

A one-click installer that doesn't ask for unnecessary permissions.

Automatic updates

The app downloads new versions in the background and updates at a convenient moment.

Code signing

Signed releases to reduce 'unknown publisher' warnings from the operating system.

Local hardware and file access

Safe communication with USB devices, local files or devices on the network.

Licensing and activation

Licence keys or account-based activation for paid products.

Error reporting

Errors on users' machines reach you anonymously.

Why desktop, and when web?

If the job can be done in a browser, a web app needs less maintenance. But if you need local hardware (USB, serial ports, printers), offline work or deep operating-system integration, a desktop app is the right choice. We make this call together on the first call, and I won't recommend desktop if you don't need it.

Updates are part of the product

When desktop software relies on manual updates, most users stay on old versions, which increases both support load and security risk. That's why the update server, release channels and rollback plan are designed from the very first release.

How we work

  1. 01

    Platforms and scope

    We settle the target operating systems, hardware access and offline needs.

  2. 02

    Prototype

    Critical hardware or system integration is validated first with a small prototype.

  3. 03

    App and distribution

    The interface, installer and auto-update are built together.

  4. 04

    Release

    A signed version ships and is refined using error reports from the first users.

Technologies I use

ElectronTypeScriptNode.jsWebSocket

Typical budget and timeline

TRY 65,000 – TRY 190,000

5–16 weeks · depends on scope

Estimate your own scope

Frequently asked questions

Can one app run on both Windows and macOS?
Yes, Electron ships both platforms from a single codebase. macOS distribution requires an Apple developer account and notarization.
Can the app work without an internet connection?
Depending on scope, yes. Offline parts and syncing once the connection returns are designed up front.
How are updates delivered?
A new version is uploaded to an update server; the app detects it and installs it in the background or after asking the user.

Other services