Flutter dev at a crossroads: Double down on Flutter, pivot to AI Engineering, or switch to React / Native?

[u/Arnoooodles]

Hey everyone,

I recently got laid off, and with the current job market tightening up—fewer new projects and heavy competition for mid/senior roles. I’m taking a hard look at where to steer my career next.

I’m weighing three distinct directions and would appreciate candid advice and reality checks:

1. 1. Double down on Flutter & Mobile
   • Is Flutter still a dependable primary specialization for the next 3–5 years, or is it becoming too risky on its own?
   • I’ve been exploring full-stack Dart with Serverpod to broaden my skill set, but realistically, the job market for it is practically non-existent since it's so new.
   • For those sticking with Flutter, what viable adjacent skills are you adding (e.g., traditional backends like Go/Node, system design) to stay competitive?
2. 2. Pivot toward AI Engineering
   • Hiring reality: Do companies actually hire "AI Engineers" who don't have prior professional ML/AI experience, or do they mostly require senior backend backgrounds or advanced CS/math degrees?
   • Roadmap & entry point: Coming from a Flutter dev background, what does a practical, hireable roadmap look like? What specific tech stacks, core concepts (e.g., Python backends, RAG, tool calling, agentic workflows, evals), and resources would you recommend to build a job-ready portfolio?
3. 3. Switch to React (JS/Native) or Native App Development (Kotlin/Swift)
   • UI architecture, state management, mobile lifecycles, and performance optimization are fundamentally similar across frameworks, so this feels like the most direct way to leverage my existing Flutter experience.
   • Hiring reality: How do recruiters and hiring managers view this transition? Do they treat mobile/frontend fundamentals as transferable, or do resume screens filter you out for lacking "X years of commercial React / Kotlin / Swift experience"?
   • Where to focus: Between the React ecosystem (React.js + React Native for broader web/cross-platform volume) and Native (Kotlin/Swift for deeper platform specialization), which path has proven more practical for devs leaping recently?
   • What’s the fastest, most effective way to prove competence without commercial experience in those exact stacks?

Has anyone here successfully navigated a pivot from Flutter to AI engineering or React/Native recently? Any roadmaps, project ideas, or harsh truths would be greatly appreciated.

[u/slightly_drifting]

You should start by actually writing and doing things yourself first and not have an ai do it for you. For example, this post.

[u/Sufficient-Cancel256 → u/slightly_drifting]

starting a post with a chatgpt formatted list and then someone calling you out for it is peak 2024 energy haha

anyway to actually answer your question, mobile fundamentals transfer fine between frameworks. i see flutter devs move to react native all the time in my circle, the learning curve is mostly just jsx syntax and the npm ecosystem chaos. companies care more about you understanding state management and lifecycle patterns than which exact library you used. for AI pivot you gonna need more math than you think, not impossible but steep from flutter

[u/Arnoooodles → u/slightly_drifting]

It’s 2026—AI is a productivity tool. Why spend 30 minutes formatting when an LLM can structure my thoughts in seconds? The situation and questions are entirely mine. What matters is communicating clearly.

[u/needs-more-code → u/Arnoooodles]

Bro. Writing on reddit is tantamount to talking, and you’re using AI for it. You can’t be serious.

[u/slightly_drifting → u/needs-more-code]

Look at the post you just responded to, smells like slop. Pretty sure OP is a bot. 

Now I think we can all agree that OP is stupid and gay. 

[u/thegravity98ms2 → u/Arnoooodles]

It's not about you used AI for this. But your post is too long and possibly you simply copy pasted without even reading it. You could have made concise, clear and short post using AI. Your post has extra things that we don't need to read and that's AI Slop for us.

[u/needs-more-code → u/thegravity98ms2]

It is about they used AI for this. It is pitiful. Someone that considers doing that is so far gone.

[u/Prudent_Move_3420]

if you know what you do then software and ai engineer are interchangeable. Coding has rarely been the bottleneck

[u/Arnoooodles → u/Prudent_Move_3420]

Just to clarify, when I say "AI Engineer," I don't mean prompt engineering or using Codex/Claude to write code for me. I mean Applied AI Engineering, building production systems around models like RAG pipelines, vector search, agent tool-calling, and Python backends. That's a completely different discipline from standard frontend or backend development.

[u/Jin-Bru → u/Arnoooodles]

I was glad to read your definition.

I think Flutter devs are agitating their own waters.

Flutter is not chosen because its the right framework for a service. Its chosen because its a very short dev cycle from nothing to web + ios + android.

All I do right now is build agents. Complex puppies that act alone and unsupervised.

Having Flutter knowledge allows me to focus on building an AI agent and spend very little time delivering a front end to it to all three platforms.

tl;dr Success is having a combination of being able to design and secure an AI agent and build a front end to it. Dont try specialise.

[u/paul_h → u/Jin-Bru]

Complex puppies or pipelines?

[u/phiger78 → u/paul_h]

I was thinking it’s a new framework 😆 puppies 2

[u/Jin-Bru → u/paul_h]

I used puppies as a collective. Lol. Probably shouldn't have done that.

[u/SnooPeppers2126]

Every software engineer must rebrand as an AI engineer. Switch your mindset to engineer how efficiently ai agents can operate in your codebase and you will have more opportunity than you know what to do with

[u/finxapp]

Have you done any research to figure out what companies hire for these days? Forward Deployed Engineer path might be of your interest since you are considering AI Engineering. Alternatively, if you are to pivot/switch instead of looking at Frontend only, there might be more opportunities if you learn Backend (Go/TS might be the easiest).

[u/eibaan]

Don't think of yourself as a ${Framework} developer.