MyMFA

CHANGELOG

Versions and development history

How MyMFA evolves — from the first pilots to public releases.

← Back to home

MyMFA · iOS / Android

Current apps

MyMFA for iPhone and Android is available on the App Store and Google Play. Public and upcoming releases are distinguished below.

Android

1.2.1 (build 18)

Public version

Next release: 1.2.1 (build 48)
Awaiting store review

Open store ↗

Status verified:

Approval and update availability can differ between stores. A test build is not a public release.

Full changelog →

Development history

A summary of major changes. Earlier milestones are grouped by development period; feature availability depends on the installed version and connected service.

Android 1.2.1 (48) — submitted to Google Play

  • Signed build 48 was uploaded to the production track. Google Play checks are underway; public availability is not yet confirmed.
  • Improved monochrome GitHub and Ubisoft icon contrast in light and dark themes, with the build number aligned with iOS.

1.2.1 — clearer accounts and service icons

  • New home layout: search, TOTP accounts and MyMFA accounts. Additional options live in the menu; the QR scanner is available in the header.
  • Expandable account details, larger service icons and a TOTP validity countdown. Icons are cached on the phone and revalidated on later launches.
  • A shared online provider catalog identifies known services. Privacy information now covers icon requests.
  • Android 1.2.1 (18) is public. iOS 1.2.1 (48) is on TestFlight and awaiting App Store review. Android (48) is being prepared to align build numbers and improve icon contrast.

Account migration and the first public iOS release

  • Google Authenticator export QR import: multi-part scanning, preview and account selection before saving. Added version 2 export compatibility and clearer errors.
  • The guide distinguishes Google Authenticator TOTP transfer from setting up individual services again for Microsoft Authenticator. Its push and passwordless accounts cannot be transferred as TOTP.
  • The first iOS app passed App Store review. Android 1.2.0 (17) added import; the public iOS version subsequently advanced to 1.0.1.

Push notifications, appearance and backups

  • Apple APNs and Google FCM integration for MFA request notifications. Android 1.1.0 (16) added FCM; delivery also depends on phone permissions and settings.
  • Light, dark and system appearance; notification diagnostics and cleanup of completed requests.
  • Choose where to save an encrypted backup using the system picker, including cloud storage providers available on the phone.

Panel, multiple accounts and the AD FS pilot

  • QR phone pairing, multiple independent MyMFA accounts and pairing management in Panel. Separate controls for enabling and requiring MFA.
  • Approval screens provide the requesting service and account context, with technical information in details.
  • The AD FS federated sign-in pilot tested approval, rejection and expiration. This does not announce a general production rollout of AD FS or Exchange OAuth.

From the first pilot to mobile apps

  • MyMFA began with its own identity and website in Czech, English and German. Local TOTP and phone-based sign-in approval form the foundation.
  • Windows RDP protection pilot, MSI and GPO agent deployment and preparation of server registration with brokers.
  • Progressive iOS and Android testing, pairing, backup restoration and operation of three brokers.