ResidentAxis
Sign in Request a pilot

Feature

Mobile experience

The same product on a phone. Managers get an adaptive layout today; the native release is being validated for pilot use before store submission.

Request a pilotProduct overview

The problem

Mobile is usually a resident app and a promise.

Managers walk units with a clipboard because the manager experience was never built for a phone. Vendors get a login they cannot use in a basement.

  • Inspections are done on paper and typed in later.
  • Maintenance photos live in a camera roll.
  • Owners wait for a monthly PDF instead of opening a portal.
  • Push notifications go to nobody because there is no app.

The workflow

One codebase, every screen

  1. Responsive for every role

    Phone-width layouts for the manager surfaces too: kanban becomes a list, tables become cards, controls meet 44px touch targets.

  2. Native release preparation

    A Capacitor configuration and native security design support the upcoming iOS and Android release; native projects and store submission are still in preparation.

  3. Biometric unlock

    Face ID / fingerprint unlock of the stored session issues a short-lived bearer.

  4. Camera and files

    Photos attach to work orders and inspections through the same MIME-checked, size-capped, checksummed upload pipeline.

  5. Push and deep links

    Device registration and a push channel; payment returns and signature links validated against an allow-list before the app navigates.

Illustrative resident view in the native shell. Store listings are being prepared; the apps are not yet published.

Capabilities

What is built, what needs configuration, what is planned

Each row is a real capability in the current build. Labels are derived from the codebase and its test suites, not from a roadmap deck.

How to read the labels

Built
Implemented in the current build and covered by its test suite.
With configured integration
Implemented; a live outcome requires a provider you configure (keys, contract, or credentials).
Pilot
Implemented in part and enabled per pilot customer with tuning.
Planned
On the roadmap. Not sold or promised today.

  • Responsive web app for every role

    Built

    Phone-width layouts for manager, owner, resident and vendor surfaces, including kanban-to-list and table-to-card adaptations.

  • Native iOS and Android shell (Capacitor)

    Pilot

    Configuration, secure token storage, refresh tokens, biometric unlock and deep-link validation are built; native projects and store listings are in preparation.

  • Push notifications

    With configured integration

    Device registration and a push channel exist; delivery needs FCM / APNs credentials.

  • Biometric unlock

    Pilot

    Face ID / fingerprint unlock of a stored session with a short-lived bearer.

  • Camera capture for maintenance and inspections

    Pilot

    Photos attach to tickets and inspections through the same upload pipeline (MIME allow-list, size cap, checksum).

  • App Store and Google Play listings

    Planned

    Submission is prepared, not yet made.

By role

What each party gets

Property managers

Walk a unit, run the inspection, dispatch the vendor — from the phone.

Residents

Pay, request, sign and message from an app that unlocks with their face.

Vendors

Assigned work with photos and status updates from the field.

Configuration and pilot notes

Before you rely on it

Things that are set up per operator during a pilot, or that depend on a provider you contract.

  • Native apps are in preparation for the Apple App Store and Google Play; they are not yet published. The web app is installable as a PWA today.
  • Push delivery requires FCM / APNs credentials configured per deployment.
  • Universal Links / App Links require the association files served from the app domain.

Honest status

What “mobile” means today

We would rather say “responsive now, native in review” than put a store badge on a page before it is true.

  • Responsive web app for every role — built
  • Native shell configuration, token storage, biometrics — built
  • Push channel — built; delivery needs credentials
  • Store listings and privacy labels — prepared
  • Store publication — not yet

Questions about this area

When will the apps be in the stores?

The readiness package (listings, privacy disclosures, screenshots plan, review account) is prepared; publication follows native build verification and store review. We do not announce dates we cannot keep.

Can residents use the mobile web app in the meantime?

Yes. The web app is responsive and installable to the home screen. Native biometrics, camera capture and push are being validated as part of the mobile pilot release.

Related

Connected areas

Maintenance & vendors

Work orders, dispatch, vendor portal, inventory, violations.

Learn more

Resident portal & payments

Balances, receipts, card/ACH via Stripe, Zelle queue, messaging.

Learn more

Move-in, inspections & deposits

Guided inspections, key-release gate, disposition from the diff.

Learn more

See mobile on your portfolio.

A pilot starts with a discovery call and your CSV exports. We reply within two business days.

Request a pilot Talk to us