DEV Community: Eddy Lujan

Native Swift + Local AI 🧠📱

Eddy Lujan — Tue, 03 Feb 2026 13:58:26 +0000

Yesterday I showed my web stack, but today we go down to the metal. After my 9-to-6 job, I spent the night researching—and I managed to run Whisper (OpenAI’s AI) directly on my iPhone’s chip.

Why? Because I’m tired of the "Cloud Tax."

Most AI tools force you to:
Pay a monthly subscription.
Send your private audio to their servers.
Have a stable internet connection.

I broke that cycle.

✅ Airplane Mode (No WiFi/Data).
✅ Total Privacy (Nothing leaves the device).
✅ Instant Translation (Spanish → English).

0 APIs. 0 Subscriptions. Pure on-device processing.

Who else is fed up with paying to have their privacy compromised? Drop a “ME” if you’d use this for your meetings, studies, or private workflows!

Building in Public: How I Pivoted from Features to Validation 🚀

Eddy Lujan — Thu, 29 Jan 2026 16:29:17 +0000

I spent months building features almost every day.
Clean code. Real infra. Everything working.

But I made a classic developer mistake:
I built first… and asked questions later. 🚨

As a developer, my default mode was:

“Just add one more feature.”

Admin panel.
Payments.
Webhooks.
Integrations.
More modules.

Technically solid. Business-wise? No real validation 😅

After ~8 months, I realized the problem wasn’t the code.
I was trying to validate:

an e-commerce platform
a SaaS product
my own internal system

…all at the same time.
No focus = no signal.

So instead of throwing everything away, I reframed it.

I stopped thinking “product”
and started thinking “execution engine.”

The admin panel + modules became my way to:
build → test → learn → kill fast 🧪

From now on, I’ll use this setup to:

Explore small ideas
Ship tiny micro-SaaS
Validate before scaling
Share what works (and what doesn’t)

Less ego. More feedback.

This isn’t a launch.
It’s a reset.

If you’re a dev who loves building but struggles with validation, you’re not alone.

Building in public from here 🚀

Building in Public: How I Pivoted from Features to Validation 🚀

Eddy Lujan — Thu, 29 Jan 2026 12:04:22 +0000

I spent months building features almost every day.

Clean code. Real infra. Everything working.

But I made a classic developer mistake:
I built first… and asked questions later. 🚨

As a developer, my default mode was:

“Just add one more feature.”

Admin panel.

Payments.

Webhooks.

Integrations.

More modules.

Technically solid. Business-wise? No real validation 😅

After ~8 months, I realized the problem wasn’t the code.
I was trying to validate:

an e-commerce platform

a SaaS product

and my own internal system

…all at the same time.
No focus = no signal.

So instead of throwing everything away, I reframed it.

I stopped thinking “product”
and started thinking “execution engine.”

The admin panel + modules became my way to:
build → test → learn → kill fast 🧪

From now on, I’ll use this setup to:

explore small ideas

ship tiny micro-SaaS

validate before scaling

share what works (and what doesn’t)

Less ego. More feedback.

This isn’t a launch. It’s a reset.

If you’re a dev who loves building but struggles with validation, you’re not alone.

Building in public from here 🚀