Mayorkun
banner
samuelayan.bsky.social
Mayorkun
@samuelayan.bsky.social
65 followers 12 following 520 posts
Product Designer | Software Developer | Specializing in iOS and Web Applications | Shipped 10+ Products | AI-Expert | AI-Powered creator | Ad Strategist | Scale your brand into 7 figures Portfolio: https://mayorkun.framer.website/
Posts Media Videos Starter Packs
Pinned
I’m a product designer who codes—or a dev who designs. Either way, I love turning ideas into clean, intuitive iOS and web apps.

Over the last few years, I’ve shipped 10+ digital products from scratch using SwiftUI, React, and a whole lot of coffee.
If you run your hustle on WhatsApp (fashion, food, hair, or anything in between), I’m testing this with a few early users.

Drop “PILOT” or DM me to join the free trial 💬

#buildinpublic #whatsappbot #AI #Nigeria #automation #smallbusiness #nodejs
🔜 Next up:

Hook into MongoDB for full data persistence

Generate live order summaries

Start pilot tests with 2–3 Lagos-based vendors
That’s what this project is becoming:
a WhatsApp storefront engine for small businesses.

No fancy tech setup.
Just chat -> order -> confirm.
🧠 Why this matters:

Every vendor knows that moment:

“Sorry, I forgot your order. Can you resend it?”

That tiny delay loses trust (and money).

Now imagine WhatsApp remembering every order, total, and customer, instantly.
At one point, my terminal yelled:

❌ ReferenceError: userCarts is not defined

😂 That bug cost me two hours and one cold drink.
But it taught me how to design resilient chat memory systems that’s what makes the bot feel alive.
Behind the scenes (for the techies):

-Node.js + whatsapp-web.js

- JSON-based persistent memory (logs survive restarts)

- Structure tracking: userId, action, items, total

- Safe file reads/writes to avoid data loss
🛍 Vendors can now:

- Add/remove items from a customer’s cart

- Auto-log every action (Add, Remove, Checkout)

- Recall past orders with “Show my orders”

- See totals, dates, and item summaries instantly

Yes, all from WhatsApp chat 🤯
💡 So far I have built something powerful:

a full cart + checkout system that works entirely inside WhatsApp chat.

No website. No dashboard.
Just WhatsApp.
🚀 Building My WhatsApp AI Assistant, Progress Update #1

Yesterday I shared how I started building a WhatsApp AI Assistant, a bot that helps real vendors manage orders, answer questions, and never miss a customer again.

Here’s what’s new 👇🏽
I’m building a WhatsApp AI Assistant from scratch for real vendors and small businesses, not tech demos.

It replies, takes orders, and hands off to the owner all inside WhatsApp.

Here’s how it started 👇🏽
Want to test the bot for your business?

👉🏽 Drop “PILOT” below or DM me.

Devs & founders I’ll post my GitHub + build breakdown soon.

#buildinpublic #AI #WhatsAppBot #SmallBusiness #Nigeria #NodeJS #Entrepreneurship
This bot won’t just respond.
It’ll convert.

It keeps customers engaged, collects orders fast, and frees owners to focus on what matters.

🚀 Next steps:

Finish order flow + DB

Launch 3 pilot tests (Lagos vendors first)

Public access later
I’m not building for tech bros.

I’m building for:
👗 Fashion vendors
🍰 Bakers
💇🏽‍♀️ Hairstylists
🍛 Restaurants
💼 Freelancers

The people already running their entire business on WhatsApp and just need a little automation help.
Next up:

- Order capture (collect name, item, quantity, address)

- Auto-save to database (MongoDB)

- Vendor dashboard

- AI that learns your brand’s tone + pricing style
My favorite moment last week:

“✅ WhatsApp client ready — session saved
📩 Incoming: “Hey bot, how are you?”
🤖 Replied: “I’m doing great! How can I help you today?”
What I’ve built so far 👇🏽

✅ WhatsApp client using Node.js

- AI replies (first Hugging Face, now Ollama, fully offline)

- Real-time message parsing & session saving

- Error logs + self-recovery when it breaks
So I decided to build something simple:

A bot that lives inside WhatsApp, answers questions, takes orders, and passes control back to the vendor when needed.

No app. No dashboard login. Just WhatsApp.
Most small business owners (especially here in 🇳🇬) run their entire business on WhatsApp:
messages, orders, deliveries, customer service…

But one problem keeps coming up 👇🏽

They can’t reply to everyone fast enough. Every “I’ll respond later” = a lost customer.
I’m building a WhatsApp AI Assistant from scratch for real vendors and small businesses, not tech demos.

It replies, takes orders, and hands off to the owner all inside WhatsApp.

Here’s how it started 👇🏽
When speed meets empathy, that’s when products feel alive.

What’s the one “works perfectly but feels wrong” moment you’ve had while building?

#ProductDesign #WebDev #iOS #AI #DesignThinking #DeveloperLife #BuildInPublic
That’s when it hit me that sometimes the bug isn’t in the code, it’s in the design decisions.

As devs, we debug code.
As designers, we debug feelings.

I’ve shipped 10+ products, but this balance still humbles me every time.
Have you ever built a built a feature that looked great in code, but felt off in use.
It passed every test, ran fast, and even had perfect CRUD logic…
but when you tried it as a user, it felt confusing.

Code: works perfectly Design: feels wrong
And if you want, I can share a small checklist I now run through before every release DM me or drop a comment.

#ProductDesign #WebDev #iOS #DeveloperLife #LessonsLearned
We all get burned by these “tiny mismatches”. If you’ve ever lost hours (or days) due to schema mismatch, contract mismatch, or dev/staging drift, would love to hear your worst story. Let’s laugh and learn together.
After fixing, the feature worked in staging, then production. Users got the updated CRUD flow without the nasty UI weirdness or missing data. And I got 2 new messages that week from people wanting help with exactly that kind of bug (developer to product designer overlap).
• Always sync schema changes & client contracts before deployment.
• Automate migrations / versioning.
• Add logs and tests specifically for field mismatch / contract changes.
• Do small, incremental changes instead of “big sweeps” in one commit.