Looking for 1 dev to build a simple identity-first login (no passwords)
Looking for 1 dev to build a simple identity-first login (no passwords)
I have a defined login flow that replaces passwords and codes:
Tap → confirm it’s you → you’re in
I’m not building a full system right now—just a working interaction that proves this flow.
I’m looking for one developer who can build a basic version of this (mobile/web prototype).
This replaces email/password + 2FA entirely.
If you can do that, comment or DM me.
Trending on Indie Hackers
This is right in our wheelhouse. We've built authentication flows and mobile/web prototypes before happy to take a look at your defined flow and build a working version of it. DM me.
Hi Omari let's get it done by tomorrow!
Claude/Codex?
Hi! Omari, I have around 8 years experience in full stack development and I can help you to implement this login flow. Can we discuss more detail?
This is an interesting direction — especially the “tap → confirm → in” flow.
One thing I’ve seen in similar concepts: even if the tech works, the whole thing can break if the first interaction feels even slightly unclear or unsafe to the user.
So validating the feeling of trust in the first 10–15 seconds is probably just as important as validating the flow itself.
I’m not a solo dev, but I work with early-stage products on turning ideas like this into simple working prototypes and making sure the flow actually feels intuitive before scaling it.
If helpful, happy to take a look at your current flow and share where friction might appear early.
You said the first 10–15 seconds can make or break trust — that’s exactly what I’m trying to lock in.
What would you need to see in that first interaction to feel like this is actually safe?
Good question — for something like this, the trust moment is very subtle.
For me, in the first 10–15 seconds I’d need to feel a few things:
First, I clearly understand what’s happening
“confirm it’s you” is a bit abstract — I’d want to instantly get what that actually means (device, biometric, email, etc.)
Second, why this is safe
Not just “secure”, but why I should trust this more than something familiar like passwords or 2FA
And third, what I’m NOT risking
Can I get locked out? What happens if something fails? Am I giving access to anything?
If even one of those feels slightly unclear, I’d hesitate — and that hesitation usually breaks the flow.
So it’s less about making it feel smooth, and more about removing even small uncertainty in that first interaction.
That makes sense — especially the hesitation part.
I think the gap right now is that “confirm it’s you” feels abstract when it should feel specific and controlled.
The direction I’m thinking is:
– Make it clear what is being used to verify you in that moment (without exposing the system)
– Make it obvious you’re not giving up control — you’re just confirming identity, not handing over access
– And make recovery feel predictable so there’s no fear of getting stuck
If you saw that clearly in the first interaction, would that remove most of the hesitation — or is there still something that would feel risky?
That direction sounds right — especially making the interaction feel more specific and controlled.
I think what would still matter (even if all of that is clear) is how it feels in the moment, not just how it’s explained.
For example, even if I understand:
“this is safe, I’m not giving access, recovery is predictable”
I’d still hesitate if the action itself feels like:
“one tap and I’m suddenly in”
That can feel a bit too instant for something security-related.
What usually helps is a small sense of progression, like:
“I see what’s happening → I confirm → I see the result”
Even something subtle like a short confirmation step or visible feedback can make it feel more trustworthy.
So I think it’s not just removing uncertainty, but also giving the user a sense of control during that moment.
Passwords are the obvious friction, but the real advantage is removing recovery, resets, and the entire “credential management” layer users quietly hate.
If the flow is truly “tap → confirm → in,” the product is not just faster login.
It’s a trust model.
That changes the bar:
not “is this easier than passwords?”
but “does this feel safer than them?”
If users hesitate for even a second on identity certainty, the whole thing collapses.
That’s the real surface to validate first.
Hi Omari. Our team can provide you with a developer to complete your tasks. Feel free to submit your request here