Frontend, Backend, or Mobile App Development: Finding Your Path.

TechCrushHQ avatar
TechCrush.pro
@TechCrushHQSep 23, 2025

The Spaces brought together host Abishola and four practitioners—Lukman (front-end), Tobi (full‑stack with a backend focus), Adelene “Folarin” (mobile), and Suraj (software engineer)—to help beginners choose among front-end, back-end, and mobile. Speakers traced their paths, compared the tracks using vivid analogies (house wiring, warehouses/shops), and stressed deciding by temperament (visual design vs logic systems), market realities, and the power of practice. Core challenges highlighted were lack of mentorship, resource constraints, tutorial overload, and impostor syndrome. Actionable guidance included starting small, learning from official docs, building portfolio projects, and leveraging community. Q&A clarified UI/UX (design prototypes) vs front-end (code implementation), addressed the “saturation” myth (jobs exist for those who ship), shared impostor-syndrome coping tactics (proof-of-work, fundamentals), and mapped on-ramps to mobile (React Native, Flutter, Kotlin/Swift), noting front-end skills transfer well. Program logistics: a structured 12-week, live, community-driven bootcamp with capstone projects and the option to switch tracks. The session closed by urging participants to decide deliberately, join the communities, use recordings, and convert insights into consistent practice.

Webinar Summary: Frontend, Backend, and Mobile — Finding Your Path

Overview

  • Host: Abishola (facilitator of the scholarship webinar)
  • Speakers:
    • Lukman Zub — Frontend Developer (ConnectiQ; later references to SHQ)
    • Adelene (Folarin) Michael — Mobile Developer (Skytng)
    • Luatobi (Tobi) Sobi — Full‑stack Developer (backend‑heavy) at Glen Voucher
    • Suraj (Sebastian) Faintola — Software Developer (10+ years experience)
  • Objective: Help beginners decide among frontend, backend, and mobile development by sharing real career journeys, practical guidance, challenges, and actionable advice. The session also explained Tech Crush’s structured 12‑week bootcamp, community support, and the ability to switch tracks.

Key Themes and Guidance

Choosing Your Path: Frontend vs Backend vs Mobile

  • Common selection criteria:
    • Visual/Design affinity vs Logical/Systems thinking.
    • Desire for instant visual feedback vs comfort working behind the scenes.
    • Market realities in your region (evaluate what stacks are in demand locally).
    • Curiosity and the willingness to explore; you can switch after trying a track.
  • Analogies to clarify roles:
    • House analogy (Lukman):
      • Frontend = everything you can see and touch directly (paint, landscaping, room layout, light switches).
      • Backend = everything behind walls and under floors (electrical wiring, plumbing, foundation, structural integrity).
      • Mobile = specialized, portable "wing" of the house with unique constraints and touch interfaces.
    • Retail analogy (Tobi):
      • Frontend = the customer‑facing storefront/headquarter UI.
      • Backend = warehouse and logistics where core operations happen.
      • Mobile = a focused brand shop (portable subset of core functions) optimized for on‑the‑go use.
  • Decision approach:
    • If you’re artistic, enjoy colors, typography, and crafting interfaces with immediate visual results, frontend fits.
    • If you’re drawn to logic, systems, data flows, and “how things work under the hood,” backend fits.
    • If you want a “sweet spot” with instant interaction plus non‑trivial logic, and you recognize the world’s mobile‑first usage trend, mobile fits.
  • Master one foundation first:
    • Don’t jump into “full‑stack” prematurely. Anchor in your natural inclination (visuals vs logic), then expand to full‑stack later when you have a strong base.

Practice over Passive Learning

  • Across all speakers, a core rule: you only learn by building.
    • Watching videos alone leads to “YouTube Netflixing” without skill acquisition.
    • Read, practice, and solidify fundamentals chapter by chapter; don’t advance without truly understanding.
    • Build small projects first; starting too big (e.g., attempting a Jumia/UBA clone day one) stalls progress.

Community, Mentorship, and Resources

  • Mentorship and community are force multipliers:
    • Lack of mentorship delays growth; community provides accountability, answers, and morale.
    • Tech Crush advantage: live classes, direct tutor access (e.g., WhatsApp for questions), structured curriculum and capstone projects across tracks.
  • Resources strategy (Tobi):
    • Start with official documentation (e.g., Laravel docs, framework websites) to get a clear roadmap.
    • Use curated PDFs/books (e.g., from PDF repositories) for depth; static texts help retention.
    • Supplement carefully with YouTube; avoid drowning in unstructured content.
    • Always convert learning into code; small working artifacts will move you toward professional competency.

Persistence, Patience, and Bug‑Hunting Discipline

  • Expect slow chapters, repeated readings, and stubborn bugs; patience matters.
    • It’s normal to not “get it” after multiple passes—keep going.
    • Debugging is part of the craft; a single missing character can break things. Treat each fix as compounding experience.
    • Keep coding to avoid skill decay—long hiatuses force painful relearning.

Speaker Journeys and Insights

Lukman Zub (Frontend)

  • Entry: Introduced to coding by his developer brother; initially found coding hard (started around JavaScript) and didn’t commit.
  • Motivation: Personal financial instability and life events pushed him to take frontend seriously; sought mentorship and tackled multiple tutorials.
  • What frontend entails:
    • Implement designs into functional, fast, engaging browser experiences.
    • Core tooling includes HTML, CSS, JavaScript.
    • Self‑assessment questions: Do you have an eye for design/detail? Do you enjoy instant visual results? Are you passionate about user experience? Do you enjoy a fast‑paced environment where tools evolve rapidly?
  • Advice: Follow curiosity, build from basics to advanced, and ensure consistent practice. Create real projects; host them; showcase your capability.

Luatobi (Tobi) Sobi (Backend‑heavy Full‑stack)

  • Entry: Began with PHP around 2012 out of curiosity; paused during school; resumed ~2018 (Laravel); professional from ~2021.
  • Early constraints: Limited data/PC access, lack of mentorship, scattered resources.
  • Pitfalls: Trying to build giant products too early. Start small.
  • Path selection: Choose based on where your mind lives—visuals or logic. Master one stack; others become easier (like translating between languages once you know one deeply).
  • Market advice: Research regional demand; not every stack is equally active in every geography.
  • Extended backend opportunities: DevOps, security, data engineering, ML/AI, desktop apps—all often hinge on strong backend foundations.

Adelene (Folarin) Michael (Mobile)

  • Entry: Computer Science background; explored frontend, backend, product design/management, then settled on mobile after trial‑and‑error.
  • Mobile case for beginners:
    • High user preference for mobile experiences (banking, social apps, on‑the‑go tasks).
    • Mobile blends visuals with meaningful logic (device constraints, performance, cross‑device considerations).
  • Core guidance:
    • Just start; don’t overthink. Try a track for a meaningful period; you can switch if you don’t enjoy it.
    • “Money‑driven development” is valid, but tech is not a get‑rich‑quick scheme. Expect a runway, rejection, and the need to become top 1% in your field.
    • From frontend to mobile: Skills are transferable. If using React Native, ~60% of your JavaScript/frontend knowledge carries over.
    • Stacks overview: Kotlin/Java (Android), Swift/Objective‑C (iOS), React Native/Flutter (cross‑platform). For bootcamps, React Native is often chosen.

Suraj (Sebastian) Faintola (Software — 10+ yrs)

  • Entry: Started casually pre‑university; shifted courses (paramedical to CS); only later took programming seriously; used breaks to deepen fundamentals; began with console apps to focus on core programming logic.
  • Learning method:
    • Ensure you truly grasp each chapter before progressing—verify by coding.
    • It’s okay not to understand on first passes; keep iterating.
    • Build continuously to prevent forgetting; skills decay without practice.
  • Mindset: Determination and patience are critical. Many start; fewer persist to proficiency. Anyone can do this if they manage discouragement and stay the course.

Tools, Processes, and Collaboration

  • Frontend:
    • Implement UI/UX designs into interactive experiences.
    • Typical stack: HTML/CSS/JavaScript.
  • UI/UX vs Frontend (Q&A clarified by Lukman):
    • UI/UX Designers: Create prototypes, define typography, colors, spacing, images.
    • Frontend Developers: Translate prototypes into production code and interactivity.
    • They are complementary; design guides what frontend builds.
  • Backend:
    • Logic layers, data handling, APIs, authentication, transactions.
    • Think systems and invisible scaffolding behind the UI.
  • Mobile:
    • Native or cross‑platform apps with device constraints, performance, and UX tailored for touch and portability.

Challenges and How to Navigate Them

  • Resource constraints (devices, data, time): Use cafes, shared resources; prioritize documentation; leverage community help.
  • Content overload: Avoid unstructured hopping; follow official docs; choose curated, static texts; apply by building.
  • Impostor syndrome:
    • It’s pervasive—even among senior engineers. Expect it.
    • Countermeasures: Build a portfolio of real, defendable work; master fundamentals; lean on community; remember it’s a fleeting feeling.
  • Persistence when stuck:
    • Bugs can be trivial yet time‑consuming; treat debugging as skill‑building.
    • Don’t conclude “tech isn’t for me” based on early struggles.

Tech Crush Program Highlights (Host’s Notes)

  • Structure: 12 weeks (3 months) of live, instructor‑led sessions.
  • Community: WhatsApp groups and Telegram for discussion, support, announcements.
  • Capstone: Cross‑track projects to simulate team collaboration; solid portfolio entries.
  • Switching tracks: Allowed—decide based on genuine interest, not transient excitement.
  • Recordings: Shared via X (Twitter) links and community channels for replay.
  • Access: Check your application confirmation email (move it from spam/promotions) to join communities.
  • Mentorship: Instructors are accessible (e.g., via WhatsApp) for Q&A; approach respectfully and professionally.

Q&A Highlights

  • UI/UX vs Frontend (Godsgift’s question):
    • UI/UX produces design prototypes and style guides; Frontend builds them in code.
  • Frontend job saturation:
    • There are jobs. Many claim “saturation” because many learners stop early or lack portfolios.
    • Build and showcase real projects; actively search (e.g., LinkedIn); demonstrate you “know your onions.”
  • Full‑stack starting point (Host to Tobi):
    • Start where your strengths lie (visuals vs logic). Master one thoroughly; add the other later.
  • Learning resources (documentation vs paid courses):
    • Much is free; documentation often suffices. Use PDFs/books for structure. YouTube is supplementary—practice converts knowledge into skill.
  • Overcoming impostor syndrome (Maranatha’s question):
    • It never fully disappears; don’t let it derail you.
    • Show your work; keep a record of wins; build fundamentals so you can defend your code without leaning on AI crutches.
  • Transition to mobile and money expectations (Moise’s questions):
    • If you have frontend/JS, React Native makes the transition smoother.
    • Mobile does not inherently pay more than frontend or backend. Income correlates with expertise, persistence, portfolio quality, and networking—not just the track.
    • Rejection is part of the process; stay the course and aim for top‑tier competency.
  • Mentorship access:
    • Live classes and WhatsApp access to tutors; respectful, professional engagement expected.

What Tech Has Done for the Speakers

  • Tobi:
    • Strong professional network and collaborative culture.
    • Autonomy and practical problem‑solving (automating personal workflows).
    • Financial returns alongside knowledge compounded over years.
  • Folarin:
    • A viable career path with tangible income.
    • Enhanced logical thinking and problem‑solving beyond programming tasks.
    • Ability to “talk to computers” across devices and use code to make everyday life more efficient.

Actionable Takeaways

  • Just start—don’t overthink. Try one path for a meaningful period (weeks to months), then reassess.
  • Practice is non‑negotiable. Build small, then grow. Portfolio beats promises.
  • Use official documentation as your primary guide; supplement with curated texts and disciplined video viewing.
  • Join a community. Ask questions. Seek mentorship. Stay accountable.
  • Expect impostor syndrome and persistent bugs—treat them as part of the journey.
  • It’s okay to be money‑motivated—pair that drive with patience, persistence, and excellence.
  • If you’re selected for the scholarship, maximize the 12 weeks: attend live sessions, build capstones, engage peers, and ship personal projects.
  • You can switch tracks—but do it for the right reasons and with a clear understanding of your strengths.

Closing Notes

  • The world is mobile‑first, but web and backend remain foundational—each track can lead to significant opportunities.
  • Tech is “blood money” only in the sense that it requires your sustained effort and focus; put in the work and it will make sense.
  • Use the community channels for recordings and upcoming webinars; stay focused, build consistently, and see it through.