DEV Community: Ifeoluwa Banmeke

How I Built and Deployed a Campus Marketplace (FlexStore) as a Solo Dev: Architecture & Lessons Learned

Ifeoluwa Banmeke — Fri, 24 Jul 2026 08:41:59 +0000

Let’s be real: as a student and solo developer, building products isn't about configuring Kubernetes clusters or orchestrating enterprise microservices. It’s about staring at a very real, very annoying campus problem, opening your code editor, and figuring out how to ship a working solution before your next exam.

For me, that problem was student commerce. Buying a textbook or selling a gadget on campus was entirely fragmented—buried deep inside WhatsApp status views, scattered across chaotic group chats, or trapped on legacy classifieds that felt like they were built in 2008.

So, I built FlexStore: a lightweight, web-based campus marketplace designed to make peer-to-peer student trading actually feel seamless.

Here is a breakdown of how I designed the architecture, the tech stack choices that kept my sanity intact, and the lessons learned shipping it solo.

1. The Engineering Requirements

Before writing a single line of code, I mapped out three non-negotiable constraints:

Mobile-First is Mandatory: 99% of students are browsing on their phones while walking to lectures. If it isn't lightning-fast on mobile data, it's useless.
Zero-Latency Communication: Building an isolated, in-app chat system that students have to log into separately is a recipe for low conversion.
Lean Infrastructure: Zero budget means leveraging modern BaaS (Backend-as-a-Service) layers to skip writing repetitive server boilerplate.

2. The Tech Stack & Architecture

To move fast without sacrificing scalability, I leaned into a modern, developer-friendly stack optimized for rapid iteration and performance.

Frontend & Architecture: Built around a Progressive Web App (PWA) mindset. Utilizing a fast build setup with Vite alongside framework routing (Next.js) allowed for instant client-side transitions and optimal asset delivery.
Backend & Database: Supabase handled the heavy lifting. Instant authentication, a robust PostgreSQL database, and real-time subscription capabilities meant I could spin up secure user roles and dynamic product feeds in hours instead of weeks.
AI-Assisted Workflow: As a solo dev, AI acted as my virtual co-pilot—speeding up component scaffolding, handling edge-case debugging, and letting me focus purely on user experience logic.

The Architecture Highlight: The WhatsApp Bridge

Instead of building a heavy internal chat system, I implemented a WhatsApp Bridge.

When a student clicks on a listing they like, the app dynamically constructs a pre-filled WhatsApp message containing the item details and routes them straight to the vendor's DMs. It completely eliminates push-notification infrastructure overhead while meeting users right where they already hang out.

// Example: Dynamic WhatsApp redirect payload generator
const handleWhatsAppInquiry = (item, sellerPhoneNumber) => {
  const message = encodeURIComponent(
    `Hi, I saw your listing for "${item.title}" on FlexStore priced at ₦${item.price}. Is this still available?`
  );
  window.open(`[https://wa.me/$](https://wa.me/$){sellerPhoneNumber}?text=${message}`, '_blank');
};

3. Making It Discoverable: SEO & Performance

A great product sitting on an unindexed domain helps nobody. To ensure FlexStore gained organic traction across campus searches, I baked SEO straight into the core architecture:

** Dynamic Open Graph Tags:** Ensuring that every time a product or store link is dropped into a WhatsApp group chat or Twitter thread, it renders a gorgeous, media-rich preview card.
Structured Data (JSON-LD): Giving search crawlers clear schema definitions for products, categories, and pricing.
Asset Caching: PWA service workers caching critical shell assets so repeat visits load instantly, even on terrible campus Wi-Fi.

4. Hard-Earned Lessons from the Trenches

PWA > Native Apps for Campus Tools: Forcing students to download an APK or visit an app store adds friction. A well-optimized PWA that installs straight from the browser is the ultimate growth hack.
Lean Into Existing Habits: Don't reinvent user behavior. By routing transactions through WhatsApp instead of a custom chat engine, I saved weeks of backend work while improving user trust and conversion.
Ship Before You're Ready: Perfection is just procrastination in disguise. Pushing an MVP live, breaking things, and fixing them based on real peer feedback teaches you more in a week than building in a vacuum for six months.

Final Thoughts

Building FlexStore reinforced a core belief: a single developer armed with the right modern tooling, AI assistance, and an obsession with a real user problem can build production-grade software that rivals entire teams.
If you're an indie hacker or student staring down a project idea: stop overthinking the stack, build the core loop, and just ship it.

Curious about the Supabase schema, the PWA caching strategy, or how the WhatsApp redirect handles payloads? Drop a comment below!

Dev Breakdown: What Google I/O 2026 Means for Your Stack 💻🛠️

Ifeoluwa Banmeke — Tue, 19 May 2026 16:42:57 +0000

Google I/O 2026 is officially live, and if you’re a developer, your roadmap for the rest of the year just got a lot more interesting. Google is drastically lowering the friction for embedding autonomous capabilities into apps, expanding into new runtime environments, and completely changing how we interact with mobile and desktop operating systems.

Let’s cut through the marketing fluff and look at the actual engineering shifts coming out of today’s keynotes.

1. Deep-Tier OS Integration: Android 17 & Gemini Intelligence

Android 17 isn't just an API bump; it's being fundamentally re-engineered as an intelligence system.

What's new:
Google introduced Gemini Intelligence. Instead of traditional sandboxed apps, the OS is moving toward an architecture where system-level AI agents can securely interact across application boundaries.

🛠️ The Dev Takeaway

If your app doesn't expose clean semantic schemas or deep-linking hooks for AI agents to interact with, it’s going to get left behind. We need to start building apps that are designed to be read and manipulated by autonomous agents, not just human eyeballs.

2. The Mobile/Desktop Convergence (Googlebooks & ChromeOS)

Google provided more technical details on the software stack powering their new Googlebook laptop lineup. The big architectural shift here is the convergence of ChromeOS and Android (widely discussed as a unified "Aluminium OS" pipeline).

For web and full-stack devs, this means:

System-level Gemini integration built directly into the Chrome architecture.
New capabilities for headless web automation, native page summarization, and secure, localized form-filling APIs.
Optimization push for Progressive Web Apps (PWAs) and Android apps running on high-performance laptop chips.

3. Android XR SDKs are Dropping

Spatial computing is moving into the mainstream developer workflow. Google showcased major updates to its Android XR initiative, specifically teasing high-efficiency pipelines for Gemini-powered smart glasses.

If you're building with Unity, WebXR, or native Jetpack Compose, the new XR extensions look incredibly promising for real-time multimodal data streaming and low-latency situational rendering.

💬 What should you build next?

The theme of this I/O is clear: Build for Agents.

Are you planning to dive into the new Android 17 developer previews, or are you looking to optimize your web apps for the new... The "Remy" Agent: The biggest buzz is around proactive AI agent capabilities (codenamed Remy). Instead of just answering prompts, this agent operates autonomously—handling background tasks like replying to your emails, organizing your calendar, and executing multi-step app workflows without needing constant user input.
Creative Upgrades: Major updates are rolling out for Veo (AI video generation) and Lyria (professional-grade music tool).

2. "Aluminium OS" & The Googlebook Era
In a massive structural shift, Google is bridging the gap between mobile and desktop by merging Android and ChromeOS into a lightweight substrate called Aluminium OS. This new OS is built from the ground up to natively run Android apps, cloud-based Chrome tools, and desktop-level Gemini agents seamlessly.
Hardware partners like Acer, ASUS, Dell, HP, and Lenovo are showing off premium Googlebooks—a brand-new laptop category built explicitly to host this AI-first operating system.
3. Android 17 & "Gemini Intelligence"
While Google gave a sneak peek of Android 17 last week, today's keynote dives deeper into how Gemini Intelligence acts as the phone's new core. Multi-Step Automation: The on-device AI can now create custom widgets on the fly and intelligently automate tasks across third-party apps.
_ Rambler Dictation:_ A highly sophisticated multilingual dictation tool that can smoothly polish voice-to-text, including natural "Hinglish" code-switching.
System Ecosystem: Seamless, native AirDrop-style compatibility is coming via an updated Quick Share, alongside an intuitive Material 3 design refresh.
4. Android XR & Smart Glasses Partnership
Google is finally pushing its augmented reality ecosystem into the consumer spotlight. They are demonstrating live, Gemini-powered smart glasses built in collaboration with Samsung and major lifestyle eyewear brands like Warby Parker and Gentle Monster. The focus here is on ambient, display-less audio/visual AI assistance (similar to a conversational co-pilot built directly into your frames).

5. Google Health Rebrand & Fitbit Air
The Fitbit app is officially being rebranded to Google Health. Google introduced the Fitbit Air, a new wearable designed to feed years of deep biometric data into a highly personalized Gemini AI Health Coach. For Developers: The Developer Keynote follows immediately after the main event, focusing on new Gemini APIs, automation toolkits, and SDKs for building within Aluminium OS and Android 17.

Is Vibe Coding a Scam? A Brutally Honest Take from an OAU Founder

Ifeoluwa Banmeke — Thu, 14 May 2026 15:25:20 +0000

If you’ve been online lately, you’ve seen the articles. Some people say Vibe Coding is the future of creativity; others say it’s just a fancy way to write bad code.

As a student at Obafemi Awolowo University (OAU), I’ve spent a lot of time thinking about this. I’m not a computer science major—I’m in Business Administration. But I love tech, and I’ve been using tools like lovable.dev to see what’s possible.

Here is my honest take:

I haven't launched a world-changing SME platform yet. I haven't automated the Nigerian market. Right now, I'm just a student with a laptop, a brand called ICEPAB Systems, and a lot of questions.

I started working on a project called Flex Store a while ago, but life at OAU gets in the way. I haven't touched the code in weeks. And that’s the part no one tells you in those 'Vibe Coding' success stories. AI can help you build fast, but it doesn't give you extra hours in the day, and it doesn't replace the need to actually understand what you're building.

Is Vibe Coding wrong?
I don’t think so. But I do think it’s misunderstood. It’s not a 'get rich quick' button. It’s a way for someone like me—who understands business and design—to talk to a computer and see an idea come to life without getting stuck on a missing semicolon for three hours.

I’m still learning. I’m still testing the limits of what these AI tools can do. I’m not claiming to be an expert developer yet; I’m a Systems Orchestrator in training.

If you’re feeling speechless or confused by the tech hype, you’re not alone. Let’s stop talking about 'vibes' as magic and start talking about them as what they really are: a new way to solve problems.

I’m building ICEPAB one day at a time. No hype, just the work

The Vibe Coding Workflow: Building an SME OS in 48 Hours from a Dorm Room at OAU

Ifeoluwa Banmeke — Tue, 12 May 2026 17:23:38 +0000

After announcing my mission to pioneer Vibe Coding in Nigeria, the most common question I get is: "How do you actually build production-ready systems so fast?"
Being a Business Administration student at Obafemi Awolowo University (OAU) doesn't leave much time for traditional 6-month dev cycles. To build ICEPAB Systems, I had to master a new workflow.
The Stack: Orchestrating Intelligence
Vibe coding isn't "no-code"—it’s high-intent coding. My stack is optimized for speed and semantic clarity:
Next.js 15: For the robust React framework and server-side performance.
Tailwind CSS: To execute my "Glass Box" design language with precision.
Gemini 2.0 / AI Studio: My "Creative Partner" for generating complex logic from natural language prompts.
Vercel: For near-instant global deployment.
Step 1: The "Business Logic" Prompt
Because I study Business Admin, I don't start with "divs" or "buttons." I start with the business problem.
"Build a ledger system for a WhatsApp merchant that handles NGN (Naira) transactions and predicts restock dates using a linear regression vibe."
Step 2: The "Glass Box" UI
I believe tech should be beautiful and transparent. I prompt my UI to include:
Translucency: High-end blur effects to signify modern AI-native design.
Responsiveness: It must work on a budget smartphone in the hands of a market vendor.
Step 3: Deployment & Iteration
In the Vibe Coding world, "Done is better than perfect." I deploy to icepab.name.ng immediately, then use user feedback from my peers at OAU to "vibe" the code into its final form.
Why This Matters Globally
The world thinks AI will replace developers. I believe AI will empower a new generation of "Polymath Builders"—people who understand business, design, and code simultaneously. From my dorm at OAU, I'm proving that a teenager with a "vibe" and an LLM can out-build a traditional agency.
What should I 'vibe code' next? Let me know in the comments.
Tags: #career #productivity #nigeria #futureofwork

Beyond the Code: Pioneering the "Vibe Coding" Movement at OAU

Ifeoluwa Banmeke — Tue, 12 May 2026 16:47:35 +0000

My name is Banmeke IfeOluwa Elijah, known in the tech ecosystem as Clement IfeOluwa. As a Business Administration student at Obafemi Awolowo University (OAU) and the founder of ICEPAB Systems, I am officially documenting my journey as a Vibe Coder in the Nigerian tech landscape.
What is Vibe Coding?
In 2026, the barrier between "idea" and "execution" has vanished. Vibe Coding is the practice of orchestrating complex software systems using natural language and advanced AI agents (like Gemini 2.0 and Next.js 15). It’s about being a "Systems Conductor" rather than a syntax-focused programmer.
Why Nigeria Needs This Movement
Traditional development can be slow and expensive. By "vibe coding," I am building high-performance, localized solutions for the African market at a fraction of the traditional time. My current focus is bridging the gap between sophisticated SaaS architecture and the everyday reality of Nigerian entrepreneurs.
The ICEPAB Systems Portfolio
I am currently scaling two major pillars of my "Vibe Coding" philosophy:
OAU CBT Elite: A high-speed Computer-Based Testing platform designed to help OAU students master their curriculum.
Flex Store: A micro-SaaS ecosystem that empowers social commerce for WhatsApp merchants.
The Vibe-Led OS: My upcoming project—a full operating system for Nigerian SMEs that turns messy WhatsApp chats into structured business intelligence.
The "Glass Box" Philosophy
At ICEPAB, we don't believe in "Black Box" technology. Every system I build is designed with the Glass Box aesthetic—transparent, high-performance, and intuitive.
Let’s Connect
I am on a mission to be the youngest leader in Nigeria's AI-augmented development space. You can follow my builds and view my professional identity hub at icepab.name.ng