Skip to content
MTKSoftLabs
Independent software labEst. 2026India

We buildsoftware worthkeeping.

MTKSoft Labs is a software publisher. We build our own applications, release them on every platform they belong on, and license them directly to the people who use them — then keep supporting them long after version one.

01Philosophy

Software is judged in year two

Anyone can ship a first version. What separates a product from a demo is everything that happens after the announcement, and that is the part we design for first.

  1. 01

    A product is not a project

    A project ends at launch. A product has a second year, an OS upgrade, a store policy change, and a user who filed a bug on a device we do not own. We plan for that half.

  2. 02

    Native where it counts

    One core for the logic, and platform-specific behaviour wherever a user would notice the difference. Shortcuts on a Mac. The back stack on Android. Neither faked.

  3. 03

    Fast is a feature

    Startup time, scroll, and the delay before the first keystroke registers. These are not optimisations we get to later; they are the specification.

  4. 04

    Say what is true

    If a platform is not ready, this site says planned. We would rather set an honest expectation than collect a download that disappoints.

A machined matte-black aluminium block with a chamfered edge catching hard light, beside a single orange anodised washer.

Fig. 01 — tolerance is the whole job

02Current focus

What we are building right now

A matte black phone resting on a warm off-white desk in hard window light, beside an aluminium ruler.
AvailableIslamic Lifestyle & Reference

MTK Islam

Your Quran, prayers and everyday Islamic essentials in one place.

MTK Islam brings Quran reading, translations, prayer times, Qibla direction, daily duas and digital tasbeeh together in one place. Designed to make your daily Islamic routine simpler, wherever you are.

Platforms
1 of 2
Updated
3 Oct 2026
Downloads
1
  • iOS & iPadOSPlanned
  • AndroidAvailable
03Platforms

One core, six environments

The parts a user never sees are written once. The parts they touch every day are built to the conventions of the system they are on — because software that ignores its platform always feels borrowed.

Shared core
  • Product logic and data model
  • Design language and components
  • Offline behaviour and sync rules
  • Update, crash and diagnostics pipeline
  • 01

    macOS

    Ships as
    Notarised disk image, or the Mac App Store
    Respects
    Menu bar, keyboard shortcuts and window behaviour that match the rest of the system.
  • 02

    Windows

    Ships as
    Code-signed installer
    Respects
    Per-user install, high-DPI scaling, and an update path that does not need a support call.
  • 03

    Linux

    Ships as
    AppImage, .deb or .rpm
    Respects
    Respect XDG paths, ship no bundled surprises, and keep the binary portable.
  • 04

    iOS & iPadOS

    Ships as
    App Store
    Respects
    Gesture navigation, dynamic type, and layouts that hold from phone to iPad.
  • 05

    Android

    Ships as
    Google Play, or a direct APK
    Respects
    Back-stack behaviour, material motion, and a build that works on a mid-range device.
  • 06

    Web

    Ships as
    Runs in the browser
    Respects
    Works on a slow connection, degrades without JavaScript, and is keyboard-complete.
04How we build

Every stage produces something you can open

No month-long silences and no reveal at the end. Each stage has an artefact attached to it, and you see each one as it lands.

  1. 01

    Scope

    What it must do, who for, and which platform comes first.

    → Written spec

  2. 02

    Design

    Screens and flows at real device sizes, in the real type.

    → Reviewable screens

  3. 03

    Build

    Shared core first, then the platform edges that need to differ.

    → Installable builds

  4. 04

    Ship

    Signing, notarisation, store submission, download page.

    → Signed artefacts

  5. 05

    Maintain

    OS updates, store policy changes, real bug reports.

    → Published changelog

05Lab

Work that has not earned a name yet

Not everything we build is meant to ship. The Lab is where prototypes, tools and dead ends get written up — including the ones we abandoned, and why.

An overhead view of machined aluminium components, a steel caliper and a single orange anodised part arranged on a warm off-white workbench.

Fig. 02 — parts, before they are a thing

Nothing published yet

The first write-ups are in progress. We would rather publish one entry with a real finding in it than three that only describe an intention.

Prototypes
Ideas built far enough to judge
Internal tools
Things we made for ourselves first
Dead ends
Documented, so we stop repeating them
06What's next

Committed, not dated

Everything below is a platform we have committed to for a product that already exists. We do not publish dates, because a date is a guess and a download is a fact.

  • iOS & iPadOSMTK IslamPlanned
The catalogue

Every application we publish, on every platform we ship it to.

Some of our software is free. Some is a one-time purchase, and some is licensed by subscription. Whichever it is, the download, the price and the terms are on the product’s own page — no quote, no sales call.