Exploring the Skills & Opportunities in Frontend, Backend & Mobile Dev

The Spaces brought together a host (Abisala) and four practitioners—Akan (Akano), Adifolarin Michael, Obuzoma Esther, Favour, and Joseph—to mentor aspiring software engineers on choosing and thriving in backend, frontend, and mobile development. Speakers shared candid journeys (from movie-inspired curiosity to degree rejections and cross-discipline transitions), stressing mentorship, relentless curiosity, and community as accelerators. They clarified roles: backend as the logic, data, security, and API engine (Esther’s kitchen analogy); frontend as user-facing engineering that demands continuous upskilling; and mobile as building for Android/iOS with strong market pull, especially via cross‑platform frameworks like Flutter/React Native (Joseph). Practical guidance covered building standout portfolios aligned to job needs, self-assessment to pick a path, exploring before niching, and delivering business value beyond code quality. Challenges—debugging, sleepless nights, infrastructure limits, and mental strain—are common but surmountable with resilience and focus. In Q&A, they addressed timelines to first earnings, no‑code to code transitions, specialization, and the money-versus-passion trade-off. The panel closed by highlighting tech’s upside: remote flexibility, global networks, FX-denominated income, and entrepreneurial leverage, while urging candidates to commit, keep learning, and use mentorship well.

Court 8 Boot Camp Mentorship Webinar – Summary Notes

Who spoke

• Host: Abisala (TechRush, mentorship series facilitator)
• Akan (aka Akano): Senior Software Engineer (7+ years), backend-focused
• Adifolarin Michael: Mobile Developer (4+ years)
• Obuzoma Esther: Software Developer, backend-focused (5+ years)
• Joseph: Mobile Developer
• Favor: Front-end Developer
• Audience participants with questions: Paul, “NFC guru,” Ann, Jason, Taiwo, Richard, and one “digital candidate” (AI/ML)

Why each speaker chose their path and how they started

• Akan (backend)

  • Early spark: curiosity ignited by The Matrix and a fascination with the “machine world.”
  • Early exposure: school IT internship; began with Excel VBA, then front-end, but found design/UI work draining.
  • Transition: shifted to backend where problem-solving and “red lines” (errors) matched his preferences.
  • Defining moment: finding a mentor who modeled deep CS/math thinking and using theory to solve real work problems; solidified backend focus.
  • Core principle: never lose curiosity—across roles and seniority. Curiosity drives learning beyond the obvious and differentiates you.

• Adifolarin (mobile)

  • Entry via detour: original university plan fell through; pivoted into Computer Science.
  • Exploration: started with Python “without visible output,” then moved to front-end for visual feedback.
  • Mobile moment: internship project required a mobile app; volunteered to learn and build it. The first Play Store/App Store release was a breakthrough (“felt invincible”).
  • Path since: bounced briefly back to front-end (freelance) but returned to mobile after a referral; has stayed mobile-focused.

• Esther (backend)

  • Full‑stack training initially; gravitated to backend based on personal fit.
  • Reasoning: enjoys logic, calculations, analysis; found front-end creative/design work less engaging except for API integration.
  • Fit advice: creatives who enjoy visuals may thrive in front-end/mobile; those who love logic/problem‑solving may prefer backend.

• Joseph (mobile)

  • Non-CS background: Quantity Surveying graduate.
  • Initial driver: ambition to build tools for his industry; self-taught from PDFs, then pivoted to tech for better opportunities (notably during COVID-19’s remote-work boom).
  • Defining points: lack of mentor and community slowed growth; learned by failing and iterating. Later focused on in-demand frameworks (Flutter) after market research.
  • First job: portfolio alignment—had built a learning app similar to the employer’s product; this fit landed him the role before NYSC.

• Favor (front-end)

  • Long-standing affinity for computers; tried backend (Java, Kotlin, Python) but wanted immediate visual feedback.
  • Chose front-end to “see” results of code quickly and to work with design and interactivity.
  • Challenges: power and hardware constraints (borrowed laptops), learning path confusion without early mentorship. A mentor’s inspiration reignited focus during low points.

What each role actually does (beyond common assumptions)

• Backend development (Esther’s kitchen metaphor)

  • Analogy: Front-end is the dining area (what users see and touch). Backend is the kitchen where the food is prepared—the logic, data processing, and storage.
  • Responsibilities: data modeling and databases, business logic, security/safety (especially in fintech), and APIs that connect the UI with data and services.
  • Importance: without backend logic, the interface has little to no real functionality.

• Full‑stack development in practice (Esther)

  • Workflow:
    1. Design/Front-end: establish UI (or create it if no Figma is provided) to visualize user flows.
    2. Backend: implement the endpoints and business logic that power those flows.
    3. Integration: connect front-end to backend via APIs.
  • API metaphor: API is the waiter/waitress—takes the user’s order (front-end) to the kitchen (backend) and returns the cooked meal (data/response) for the user to consume in the UI.

• Mobile development (Adifolarin, Joseph)

  • Scope: build applications for mobile devices (Android/iOS); can start directly in mobile without front-end or backend first.
  • Why mobile matters: many users are mobile-first; interaction frequency is high; opportunities are strong, especially in mobile-first businesses.
  • Skill blend: benefits from front-end principles (UI/UX) and logical/architectural thinking.

• Front-end development beyond “making it pretty” (Favor)

  • Constant evolution: CSS approaches (floats → flexbox → grid); modern frameworks and runtimes (React, Angular, Vue, Next.js), server-side rendering vs client-side.
  • Advanced expectations: TypeScript, Tailwind, state management (Redux, Zustand), headless CMS, Web3 integration, 3D on the web (React Three Fiber/Three.js), performance, accessibility, and UX collaboration.
  • Differentiation: staying current, mastering patterns, and demonstrating breadth (and depth) across tooling, architectures, and user-centric thinking.

Career accelerators and recurring themes

• Curiosity and value (Akan)

  • Do not lose curiosity; it compels you to go beyond baseline course content.
  • Aim to deliver business value, not only “clean code.”
  • Tactic: study top-tier job descriptions (e.g., Google, Amazon). List unknowns and learn them to reach that bar.
  • Be the person who asks the hard questions and proposes improvements—the perceived “overdoer” who drives value.

• Mentorship and community (All)

  • Mentor impact: accelerates learning, prevents avoidable mistakes, clarifies path (Akan, Favor, Joseph).
  • Community benefits: collaboration, accountability, up-to-date industry signals (Joseph’s missed Figma experience highlighted this).

• Portfolios and projects (Joseph)

  • Strong portfolios are decisive in landing roles—build real, relevant projects that mirror target employers’ domains.
  • Don’t wait for your first job to start building; ship apps, polish, and document them.

• Persistence and mental health

  • Backend can be mentally taxing (Esther), front-end and mobile can be frustrating (everyone): expect sleepless nights and tough bugs.
  • External constraints (power, hardware, connectivity) are real; plan around them and pace yourself.
  • Your resilience and drive often determine how quickly you progress from learning to earning.

Choosing a path – advice for beginners

• Self-assessment first (Host, Esther)

  • Evaluate strengths and interests: visual creativity vs logic-heavy problem-solving; desire for immediate feedback vs comfort with abstract systems.
  • Attend the webinar series to hear multiple tracks explained; ask questions; then align choice with your profile.

• Explore, then focus (Favor; Host; Joseph)

  • It’s reasonable to sample tracks early (e.g., front-end vs mobile) to find fit.
  • Once you choose, commit and go deep; you can pivot later—skills often transfer across ecosystems.

• Mobile pathways (Joseph)

  • Platforms: native Android (Kotlin/Java), native iOS (Swift), or cross-platform (Flutter, React Native).
  • Recommendation for employability/coverage: start with cross-platform (Flutter or React Native) to serve Android + iOS (and with Flutter, web/desktop) and align with startup budgets.

Q&A highlights

• Q (Paul): As a business owner (school company), which skill should I learn for the business?

  • A (Host): It depends on business goals. Options could include digital marketing for reach, product management for delivery, or tech skills aligned with your product. Assess competitors and your unique edge; skills should support those priorities.

• Q (“NFC guru”): No background in tech—what’s the right path from zero logic?

  • A (Host): Start with self-assessment and research. Use these webinars to understand each path; identify what resonates and where your strengths align.

• Q (Jason): No-code web (WordPress/Shopify/Wix) background; wants websites and apps. Which area to specialize in?

  • A (Joseph): Flutter is a strong option—one codebase for Android, iOS, and web; expedites portfolio building across platforms.
  • A (Host): Try mobile dev or front-end to confirm preference; it’s fine to explore then niche down.
  • A (Joseph, follow-up): There’s no “forever lock-in”; many developers pivot over time. Foundational skills transfer.

• Q (Taiwo): Torn between UI/UX (seems faster/easier) and front-end (perceived to pay more). New to tech; can I learn UI/UX, front-end, and backend together?

  • A (Favor): Money-only motivation can backfire—front-end now requires a broad, evolving skillset and real patience. Choose something you enjoy so you can persist through the learning curve.
  • A (Host): All tracks can lead to strong earnings, but you must build competence first. Passion helps sustain you until the opportunities land.

• Q (Richard): How long until I can make money? And is mobile dev “worth it” in 2026 vs web dev?

  • A (Host): No fixed timeline. Learn → build → apply → iterate. Many graduates convert capstone and team projects into internships and entry roles; earnings grow with experience.
  • A (Joseph): Demand for mobile persists; from his experience, mobile roles can pay more than web roles in some markets. Job markets fluctuate, but mobile remains viable.

• Q (Digital candidate): Is AI/ML a good choice as a newcomer?

  • A (Host): Yes, AI/ML is a strong domain. As always, align with your interests and readiness to commit.

What tech has enabled for the speakers

• Joseph

  • Freedom to work remotely and travel; global collaboration; earning in foreign currency (FX), which can dramatically improve local purchasing power.

• Akan

  • Networks with high-caliber people (mentors, international peers, local builders); a problem-solving mindset applicable beyond work; comfortable living; opportunities to mentor others.

• Esther

  • Leverage and flexibility: remote work suits introverts; entrepreneurship potential—tech enables building solutions and ventures (co-founding, pitching, fundraising) from anywhere.

Host’s guidance and program notes

• Mindset and commitment

  • Mentorship will be available, but self-drive is non-negotiable. Curiosity, extra effort, and asking good questions are differentiators.
  • Capstone projects are a keystone—students demonstrate real capability, collaborate across tracks, and build portfolio-ready work.

• Community

  • TechRush connects learners across Africa (Nigeria, Kenya, South Africa, Ghana, Cameroon, etc.), enabling peer support, networking, and shared growth.

• Practicalities

  • Watch for emails about curricula and community links (Telegram/WhatsApp). Webinars will continue, each focusing on specific tracks to support informed decisions.
  • Technical hiccups (e.g., networking issues during the session) mirror real remote-work realities—be prepared to navigate them professionally.

Key takeaways

• Curiosity and value delivery are career accelerants—learn beyond the syllabus and focus on business outcomes.
• Build a strong, relevant portfolio early—projects that mirror employer domains confer a decisive edge.
• Seek mentorship and community; both shorten the path and keep you aligned with industry trends.
• Choose a path that fits your strengths: logic-heavy (backend), visual/interactive (front-end), or mobile-first product experiences (mobile). Explore then commit; pivots are normal.
• Resilience matters. Expect challenges (tools, power, time, mental strain) and plan to overcome them.
• All tracks can pay well; progression depends on skill, output, and persistence. Mobile demand remains healthy; front-end expectations are increasingly sophisticated; backend underpins real product value.

Closing

• The session emphasized that while guidance and mentorship are provided, your progress hinges on curiosity, consistent practice, and delivering value. Watch for upcoming track-specific webinars, connect with the community, and treat capstones and side projects as your launchpad into internships and jobs.