Back to work

Live-operation product

SubTrack BH

A local-first Android workspace for operating a boarding-house internet subscription service.

Active development · Live operation2026Private source
SubTrack BH internet subscription manager logo
Verified project evidence from the current implementation.
Role
Founder & Lead Developer
Status
Active development · Live operation
Year
2026
Stack
Kotlin · Jetpack Compose · Room · Firebase · WorkManager · Ktor

01 · Context

The problem

Subscriber names, packages, payments, expiry dates, balances and reconnections become unreliable when managed through memory, messages or separate records.

The response

SubTrack BH centralises the administration of Leo’s active Starlink service, which currently serves 29 subscribers. Room is the local source of truth, with Firebase services supporting the project’s remote-service direction.

02 · Contribution

What I built

  • 01

    Modelled subscribers, rooms, plans, devices, payments, expenses, reminders and subscription windows.

  • 02

    Separated the admin and subscriber experiences into distinct Android applications.

  • 03

    Added accounting, reporting, backup, PDF and sync-oriented foundations.

  • 04

    Designed the product around the actual workflow of operating the service.

03 · Implemented evidence

Current
capabilities.

Admin and subscriber Android apps
Local Room persistence
Subscriber, plan and device records
Payment and subscription-window management
Reminders, reports, backups and PDF utilities
Firebase authentication and remote-service foundations
WorkManager background operations
PIN security and failed-attempt lockout

04 · Engineering

Hard parts,
clear decisions.

Consistent account state

Payments, package duration, balances, expiry and reconnection rules must agree across screens instead of relying on a manually edited status label.

Admin/subscriber boundaries

The subscriber app must expose only account-safe, read-oriented functions while financial writes and business controls remain in the admin app.

Offline-first financial records

Local operation is essential during connectivity problems, while future synchronisation must avoid duplicate or conflicting financial records.

05 · Reflection

What I learned

Local-first Android architectureBusiness-rule modellingRoom persistenceApp boundary and permission designOperational product development

Planned or still in development

  • Production Lenco payment integration
  • Provider webhook verification
  • Complete subscriber invoices and payment history
  • Expanded closing, reconciliation and asset-management interfaces

Private workspace inspected locally. Provider payments remain placeholders and are not presented as working.

Open to opportunities

Let’s discuss your role,
product or technical challenge.

Open to graduate software roles, internships, freelance projects, remote work, local business systems, startup partnerships and technical collaborations.

Start a conversation