Flirexa / Customer apps

Enterprise application package

Let customers connect with an app tied to their account and device slot

The standard Flirexa application package covers Android, Windows, and Linux. It uses the operator's portal authentication and device model so access remains attached to the right customer, server, subscription, and configuration.

View EnterpriseSee the customer portal

Platforms

The clients share a service contract, not an identical shell

Android

A touch-first application for account login, device registration, region selection, connection state, and subscription-aware access.

Windows

A desktop application with independent Windows-side authentication and connection logic, tied to a Windows device slot rather than reusing a phone identity.

Linux

A console application for Linux users. It intentionally follows terminal workflows instead of imitating a desktop GUI that the product does not ship.

Identity and delivery

Application publishing still belongs to the operator

Enterprise includes the standard client package. Publishing under a specific company identity requires the operator's store accounts and signing identities.

  • Android release uses the operator-controlled package and signing key
  • Google Play may require an AAB, declarations, testing track, and store listing
  • Microsoft Store requires the reserved package identity and a trusted signing path
  • application updates must preserve package identity and signing continuity
  • branded assets and a fully branded build can be scoped separately
  • private signing keys must never enter source control or customer messages
EnterpriseStandard Android, Windows, and Linux application package included
BusinessApplications can be purchased separately, though Enterprise is the intended value path
iOSPlanned, not currently part of the standard released package
BrandingPortal-side identity and custom application distribution are related but separate operational concerns

Questions

Customer application boundaries

Are the apps a replacement for the customer portal?

No. They use the customer account and configuration APIs. The portal remains the browser experience for subscription, payments, devices, billing, and support.

Can one phone and one PC share a device slot?

They should not. Each physical installation should register its own slot so revocation, server assignment, and configuration identity remain correct.

Are custom branded apps included automatically?

Enterprise includes the standard package and the panel's white-label controls. A fully branded store build, listing, signing workflow, and custom assets can require a separate agreement.