MFA Authenticator

I’m an indie developer who’s obsessed with two things: security and good design. For years, I’ve bounced between every MFA tool on the market—official ones from big tech, open-source alternatives, even niche options built for power users. And every single one left me frustrated.

Let’s be real: Most MFA apps suck. Not because they don’t work—they do their job of keeping accounts secure—but because they’re built like afterthoughts. Clunky UIs, confusing workflows, visual designs that look like they were last updated in 2015, and zero attention to how real people actually use them. I found myself avoiding setting up MFA for new accounts because the tools were such a hassle. That’s a problem—security shouldn’t feel like a punishment.

So I did what any indie hacker would do: I built my own. A MFA app that’s easy to use first, secure second (though let’s be clear—security is non-negotiable). A app that doesn’t make you feel like you’re navigating a spreadsheet to copy a 6-digit code. A app that looks good enough that you won’t mind it living on your home screen, right next to your favorite apps.

Here’s why I decided to build it—and what I learned about building a tool that people actually want to use, not just “have to” use.

The Problem: Mainstream MFA Apps Treat Users Like Tech Experts (We’re Not)

I’ll start with a confession: I’m a tech-savvy developer, and even I struggled with most MFA tools. Let’s break down the pain points that pushed me to build my own:

• Visual chaos: Most MFA apps are a jumble of text, tiny icons, and no hierarchy. Trying to find the code for your email account when you’re in a hurry? Good luck—everything blends together. Buttons are too small, colors clash, and there’s no joy in using them. It’s like someone designed them with the mindset of “function over form” taken to an extreme—where form was completely forgotten.

• Confusing workflows: Ever tried to add a new account to an MFA app, only to be met with a wall of options? “Scan QR code,” “Enter secret manually,” “Import from another app”—but no guidance on which one to choose. Or tried to back up your codes, only to be confused by encrypted files, recovery phrases, and cloud sync toggles that aren’t explained. These tools assume you know the difference between TOTP and FIDO2, but most people don’t—and they shouldn’t have to.

• Ignoring user habits: We use our phones with one hand. We need quick access to codes. We forget where we stored our recovery codes. Yet most MFA apps force you to tap three times to get to a code, don’t let you pin frequently used accounts, and bury backup options in a settings menu that’s impossible to find. They’re built for “how it should work,” not “how people actually use it.”

The worst part? These tools are supposed to make us more secure—but their poor design makes people avoid using them. I’ve talked to friends who skip MFA because “the app is too confusing,” or who use the same recovery code for every account because they can’t be bothered to navigate the backup process. That’s the opposite of what MFA is supposed to do.

The Solution: Build for “Usability First, Security Always”

When I started building my MFA app, I set two non-negotiable rules: it had to be beautiful (not just “not ugly”) and so easy a non-tech user could use it. Security was never compromised—but it was never allowed to get in the way of a good user experience.

Here’s how I approached it:

1. Design that feels intentional (not afterthought)

I spent weeks on the UI—something most MFA developers seem to skip. I used a clean, minimal color palette (no neon greens or harsh blues) that’s easy on the eyes, even in low light. I added clear hierarchy: frequently used accounts are pinned to the top, with larger icons and bolder text. Codes are big enough to read at a glance, and a single tap copies them to your clipboard (no more long-pressing or navigating menus).

I also added small touches that make a big difference: subtle animations when you copy a code, a dark mode that’s actually designed (not just inverted colors), and a home screen widget that lets you access your most used codes without opening the app. These aren’t “extra” features—they’re the things that make people want to use the app, not dread it.

2. Workflows that follow how people actually use their phones

I simplified everything. Adding a new account? The app defaults to scanning a QR code (the most common use case) but still lets you enter a secret manually—with clear instructions for people who don’t know what a “secret key” is. Backing up your codes? One tap to export an encrypted backup to your cloud storage of choice, with plain-language explanations of why backups matter.

I also added features that solve real pain points: pinning favorite accounts, searching for accounts by name, and a “recovery code vault” that lets you store all your recovery codes in one place (encrypted, of course) so you don’t lose them. These features aren’t revolutionary—but they’re things that mainstream MFA apps have ignored for years, because they’re focused on “security” over “usability.”

3. Security that’s invisible (until you need it)

Here’s the thing: Good security doesn’t have to be obvious. My app uses AES-256 encryption for all local storage, supports TOTP and FIDO2 phish-resistant push auth, and has no cloud sync by default (though you can enable it if you want). But none of this is thrown in your face. You don’t have to toggle 10 different security settings—everything is enabled by default, and the app only asks you to make a choice when it matters (like whether to back up your codes).

I wanted security to be a background feature, not a barrier. You use the app to get your code, and it keeps your data safe without you having to think about it. That’s the sweet spot.

What I’ve Learned as an Indie Building a “Boring” Tool

MFA isn’t a “sexy” niche. It’s not a new social app or a AI tool that goes viral. It’s a utility—something people use because they have to, not because they want to. But that’s exactly why it’s worth building well.

As indie hackers, we have an advantage over big tech: we can care about the small details. Big companies build MFA tools because they have to—they’re checking a box for security. We can build them because we use them, and we hate how bad they are. We can iterate fast, listen to users, and make something that feels human.

Since launching the beta, the feedback has been overwhelming. People are saying things like, “I actually look forward to using MFA now” and “This is the first MFA app I’ve kept on my home screen.” That’s the win—not millions of downloads (yet), but building something that solves a real pain for real people.

What’s Next?

I’m still iterating. I’m adding Wear OS support (for people who want to get codes on their watch), improving the backup process, and listening to beta testers to fix small UX quirks. I’m not trying to take over the world—just build a MFA app that I’m proud to use, and that other people will be proud to use too.

If you’re tired of clunky, ugly MFA tools, I’d love for you to check out the beta. And if you’re an indie hacker building a “boring” utility tool—keep going. The world needs more tools that are built with care, not just with checkboxes.

Security doesn’t have to be a chore. It can be beautiful, easy, and even enjoyable. That’s the mission—and I’m just getting started.

— Bandit Lab, Indie Developer | A Better MFA App