DEV Community: Safiullah Korai

How to Start Technical Writing as a Developer: A Practical Guide to Sharing What You Know

Safiullah Korai — Sat, 09 May 2026 18:04:29 +0000

I did not start writing because I loved writing.

I started because I was stuck.

There was a bug I could not solve. I spent hours searching, reading half-written blog posts, digging through outdated documentation, and scrolling endless forum threads. Eventually, I figured it out. But something stayed with me. The next developer should not have to struggle like this.

So I wrote my first article.

It was not perfect. It was not polished. But it helped someone. That one response changed everything.

I’m Safiullah Korai, some of you might know me as Shahzaib.

I am a Software Engineer and full-stack Flutter developer.

Over the past few years, I have spent countless hours building mobile applications, experimenting with architecture, and chasing that balance between simplicity and scalability. And quietly, almost without me noticing, writing became the thread that held the learning together.

Technical writing is not about being a writer first. It is about being a problem solver who documents the journey.

If you are a developer wondering how to start technical writing, this guide will walk you through it in a practical, honest way.

Why Developers Should Write

Before we talk about how, we need to talk about why.

I have explored this in more depth somewhere else. I wrote an entire article on the quiet, lasting reasons writing matters for a developer. Not fame or followers, but clarity, growth, and a career that compounds over time.

Technical writing is one of the highest leverage skills a developer can build.

If you want to sit with the why before jumping into the steps, you can read it here:

Why Every Developer Should Write

But for now, here is the short of it.

It forces you to think clearly. It exposes gaps in your understanding. It helps you build a public presence without chasing trends.

More importantly, it compounds.

One article can bring opportunities months later. A series of articles can define your expertise.

You are not just writing for others. You are building a long-term asset for yourself.

Step 1: Start With Problems You Have Already Solved

The biggest mistake beginners make is trying to write about advanced topics too early.

You do not need to write about complex system design or distributed architecture. You just need to write about something you recently learned.

Think about:

A bug you fixed A concept you finally understood A tool you recently explored A mistake that taught you something

Your first audience is your past self.

If your past self would have found your article useful, you are on the right track.

Image Idea Prompt

A developer sitting at a desk with multiple tabs open, looking confused, then a second frame showing clarity with a single clean document.

Step 2: Focus on Clarity Over Complexity

Many developers think writing needs to sound technical to be valuable.

That is not true.

The best technical writing is simple, clear, and direct.

Avoid unnecessary jargon. Break ideas into smaller pieces. Use examples wherever possible.

Instead of saying:

“State management is essential for scalable applications.”

Say:

“When your app grows, managing data becomes messy. State management helps you organize and control that data.”

Clarity builds trust.

Step 3: Use a Simple Structure

A good article is not random thoughts. It has a clear flow.

Here is a simple structure you can follow:

Introduction: Explain the problem and why it matters.
The Challenge: Describe what made this problem difficult.
The Solution: Walk through how you solved it step by step.
Key Learnings: Highlight what readers should take away.
Conclusion: Wrap up with a final thought or encouragement.

This structure works because it mirrors how developers think.

Step 4: Write Like You Speak

One of the biggest shifts you need to make is this:

Stop trying to sound like a textbook.

Write like you are explaining something to a friend.

Use natural sentences. Keep paragraphs short. Avoid overly formal language.

Instead of:

"This article aims to elucidate the implementation process..."

Say:

"In this article, I will show you how I implemented this."

Your writing should feel human, not robotic.

Step 5: Show, Do Not Just Tell

Technical writing is not about explaining concepts only. It is about demonstrating them.

Whenever possible, include:

Code snippets
Step-by-step instructions
Real examples
Screenshots or diagrams

This turns your article from theory into practice.

Step 6: Build a Writing Habit

Writing once is easy. Writing consistently is what creates impact.

You do not need to publish daily. Even one article per week is enough if you stay consistent.

Start small:

Set a weekly goal
Maintain a list of ideas
Write even when it feels imperfect

Consistency beats perfection every time.

Step 7: Choose the Right Platforms

Where you publish matters, especially in the beginning.

Here are some strong platforms for developers:

Medium
Hashnode
Dev.to
HackerNoon
Substack

Each platform has its own audience. You can start with one and expand later.

Publishing across multiple platforms can increase reach, but focus on quality first.

If you want to understand the differences more clearly, like what type of content fits where and how to pick your first home without overthinking it, I wrote a separate guide on exactly that. It is called...

Where to Write as a Developer

Feel free to read it now, or come back to it later.

Step 8: Learn Basic SEO

If you want people to find your articles, you need to understand basic SEO.

Focus on:

Clear, searchable titles
Relevant keywords
Structured headings
Descriptive introductions

For example:

Bad title:

“My Experience with Flutter”

Better title:

“How I Built My First Flutter App: A Beginner’s Guide”

Think about what someone would search on Google.

Step 9: Edit Ruthlessly

Your first draft is not your final draft.

Good writing is rewriting.

After finishing your article:

Remove unnecessary words
Simplify long sentences
Fix grammar issues
Improve flow

Read your article out loud. If something sounds awkward, it probably is.

Step 10: Accept Imperfection

Your first few articles will not be perfect.

That is expected.

You might feel:

Your writing is not good enough
Your ideas are too simple
Nobody will read it

Ignore that.

Every experienced writer started the same way.

The goal is not perfection. The goal is progress.

Step 11: Build Your Personal Brand

Technical writing is more than just sharing knowledge. It is also about building your identity.

Over time, your articles will reflect:

What you are learning
What you care about
What you specialize in

This becomes your personal brand.

When someone searches your name, your work speaks for you.

Step 12: Engage With Your Audience

Publishing is only half the process.

Engagement matters.

Respond to comments
Answer questions
Connect with other writers
Share your articles on social platforms

This builds a community around your work.

And community creates opportunities.

Step 13: Turn Writing Into Opportunities

Technical writing can open doors you did not expect.

It can lead to:

Freelance writing gigs
Speaking opportunities
Open source contributions
Job offers

Companies value developers who can communicate clearly.

Writing proves that skill.

Common Mistakes to Avoid

Let’s be honest about a few traps:

Trying to Be Too Advanced

You do not need to impress. You need to help.

Writing Without Structure

Unstructured content confuses readers.

Ignoring the Reader

Always ask: who is this for?

Overcomplicating Language

Simple writing is powerful writing.

A Simple Starting Plan

If you are still unsure where to begin, follow this:

Day 1: Pick a topic you recently learned

Day 2: Outline your article

Day 3: Write the first draft

Day 4: Edit and improve

Day 5: Publish

That is it.

Do not overthink it.

Final Thoughts

Technical writing is not reserved for experts.

It is built by learners.

Every time you solve a problem, you have something worth sharing.

The real difference between developers who write and those who do not is simple.

One group documents their journey.

The other forgets it.

If you start today, a year from now you will not just be a developer.

You will be a developer with a voice.

And in today’s world, that makes all the difference.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

Where to Write as a Developer: A Calm Guide to Choosing Your First Platform

Safiullah Korai — Sun, 03 May 2026 19:15:53 +0000

When developers decide to start writing, the first confusion is not what to write.

It is where to write.

There are too many platforms. Everyone recommends something different.

Some say start on Medium. Others prefer Dev.to. Some suggest owning your audience through Substack.

The truth is simpler than it looks.

You do not need the perfect platform.

You need a starting point.

I’m Safiullah Korai, though many know me as Shahzaib. I’m a Software Engineer and full‑stack Flutter developer, building real production apps, experimenting with architecture, and focusing on modern, scalable mobile solutions. Along the way, writing became a quiet part of my growth, and figuring out where to publish was one of my earliest stumbling blocks.

Each platform has its own audience, its own culture, and its own advantages. If you understand how they work, you can use them intentionally instead of randomly posting everywhere.

This article will help you do exactly that.

The Reality: Platforms Matter, But Not as Much as You Think

Before we go into each platform, there is one mindset shift you need.

Your growth will not come from the platform alone.

It will come from:

Consistency
Clarity
Relevance

A good platform amplifies your work.

It does not replace it.

So instead of chasing reach, focus on writing something useful. Then use platforms to distribute it.

Start With One Platform, Not Five

Many developers make this mistake.

They write one article and try to publish it everywhere at once.

Medium, Dev.to, Hashnode, LinkedIn, Substack.

The result is predictable.

No traction anywhere.

Instead:

Pick one platform
Learn how it works
Build momentum

Then expand.

Focus first. Scale later.

Medium: The Best Place to Start Writing

If you are starting from zero, Medium is one of the easiest platforms to begin with.

Why Medium Works

Medium already has an audience.

People come there to read.

This means you do not need to bring your own traffic in the beginning.

It also has strong distribution. If your article performs well, it can reach beyond your followers.

What Kind of Content Works

Beginner-friendly guides
Personal experiences
Clear, structured tutorials
Thoughtful reflections on learning

Medium readers value clarity and storytelling.

How to Leverage It

Write strong titles that match search intent
Focus on readability and structure
Use proper headings and spacing
Publish consistently

Do not try to game the algorithm.

Write something genuinely useful.

Dev.to: The Developer Community Hub

Dev.to feels different from Medium.

It is more community-driven.

More raw. More direct.

Why Dev.to Works

Developers are not just readers here.

They are participants.

They comment, share, and engage actively.

If your article resonates, you will get feedback quickly.

What Kind of Content Works

Practical tutorials
Code-heavy explanations
Real-world problem solving
Honest experiences

This is not the place for overly polished writing.

Authenticity performs better.

How to Leverage It

Use relevant tags (very important)
Engage with comments
Share your learning journey
Be consistent with topics

Dev.to rewards developers who show up regularly.

Hashnode: Build Your Own Developer Identity

Hashnode is where writing meets ownership.

It gives you a personal blog with your own domain if you want.

Why Hashnode Works

You are not just writing on a platform.

You are building your own space.

This matters long term.

Because you control your content and your brand.

What Kind of Content Works

Technical deep dives
Series-based content
Long-form tutorials
Personal learning journeys

Hashnode readers are more focused and technical.

How to Leverage It

Set up your custom domain early
Create content series
Build a niche (Flutter, backend, AI, etc.)
Treat it like your personal blog

Think long term here.

HackerNoon: High-Quality, Editorial-Driven Writing

HackerNoon is not like other platforms.

It has an editorial process.

Your article is reviewed before publication.

Why HackerNoon Works

It builds credibility.

Being published here signals quality.

It also reaches a professional, tech-focused audience.

What Kind of Content Works

Well-structured technical articles
Insightful industry perspectives
Case studies
In-depth guides

This is not the place for rushed content.

How to Leverage It

Follow their submission guidelines carefully
Focus on clarity and originality
Write complete, polished articles
Choose strong, relevant topics

Think quality over quantity.

Substack: Own Your Audience

Substack is different from all the others.

It is not just a publishing platform.

It is a relationship platform.

Why Substack Works

You build an email list.

That means you own your audience.

No algorithm decides whether people see your content.

What Kind of Content Works

Personal insights
Learning reflections
Weekly updates
Deep thinking pieces

Substack is more personal than technical.

How to Leverage It

Write consistently (weekly works well)
Focus on connection, not perfection
Share your journey honestly
Build trust over time

Growth is slower, but stronger.

Publishing Across Platforms: When and How

Once you are comfortable with one platform, you can expand.

But do it strategically.

Step 1: Choose a Primary Platform

This is where you publish first.

Step 2: Repurpose, Do Not Copy Blindly

Adapt your content slightly for each platform.

Step 3: Maintain Consistency

Do not abandon your main platform while expanding.

Step 4: Focus on Quality First

More platforms do not mean more impact if the content is weak.

A Practical Strategy You Can Follow

If you are starting today, this works well:

Week 1-4:

Write only on Medium or Dev.to

Week 5-8:

Start publishing the same content on Hashnode

Month 3:

Submit your best article to HackerNoon

Month 4+:

Start a Substack newsletter

This approach builds both reach and ownership.

Common Mistakes to Avoid

Publishing Everywhere Too Early

You lose focus and consistency.

Ignoring Platform Culture

Each platform has its own expectations.

Writing Only for Algorithms

Readers can feel it.

Not Engaging With Audience

Writing is not one-way communication.

Final Thoughts

Platforms are tools.

Not shortcuts.

They can amplify your work, but they cannot replace it.

Start small.

Pick one platform.

Write something useful.

Then keep going.

Over time, you will not just grow on a platform.

You will grow beyond it.

If you are still exploring why writing matters in the first place, I wrote a piece on that too: Why Every Developer Should Write.

And if you want a hands‑on guide that walks you through picking a topic, structuring an article, and hitting publish, How to Start Technical Writing as a Developer covers all the practical steps.

This article gave you the where to write. Those two give you the why and the how to write.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

The Gap Between Design and Development Is Finally Closing

Safiullah Korai — Mon, 13 Apr 2026 18:38:57 +0000

There has always been a quiet gap in software development.

Designers create beautiful interfaces in Figma.

Developers then try to recreate those designs inside Visual Studio Code.

And somewhere in between, things break.

Spacing becomes slightly different.

Components get renamed.

Colors change a little.

Buttons look right but behave wrong.

I’m Safiullah Korai (also known as Shahzaib), a Software Engineer and full-stack Flutter developer.. I work on real production apps, experiment with app architecture, and focus on building modern, scalable, and maintainable mobile solutions.

This problem has existed for years.

But something interesting just happened.

A New Loop Between Design and Code

Recently, GitHub introduced a new integration that connects:

GitHub Copilot
Visual Studio Code
Figma

Together.

Not as separate tools.

But as a continuous loop between design and development.

The key piece behind this integration is something called the Figma MCP Server.

With it, developers can now do something that previously felt impossible.

Code and design can now move both directions.

What This Actually Means for Developers

Imagine this workflow.

A designer creates a UI in Figma.

Instead of manually studying the design and rebuilding it from scratch, a developer can now:

✅ Pull the design context directly into their code using GitHub Copilot.

✅ Generate UI based on that design.

✅ Send the working UI back to Figma as editable frames.

✅ Let designers adjust the layout again.

✅ Pull those updates back into the code.

And the cycle continues.

Design → Code → Design → Code.

A real loop.

No More “UI Drift”

If you have ever worked with designers, you probably know this situation.

The design file says one thing.

The production app shows something slightly different.

That difference is often called UI drift.

It happens because design tools and development tools live in separate worlds.

Now those worlds are starting to connect.

Developers can work inside VS Code, while designers continue working inside Figma, but both are now connected through Copilot and the MCP server.

How the Figma MCP Server Works

The setup is surprisingly simple.

Install the Figma MCP Server
Connect your Figma account
Use GitHub Copilot inside VS Code

After that, Copilot can:

Pull design context from Figma
Generate UI code based on that design
Send rendered UI back to Figma as editable frames

Designers can then tweak the layout, spacing, or components.

Developers pull those updates again.

And the loop continues.

Why This Matters in the AI Era

We are entering a time where design tools and coding tools are slowly merging.

AI is no longer just helping developers write code.

It is helping connect the entire product workflow.

From design to development.

From idea to interface.

Tools like GitHub Copilot are no longer just autocomplete for code.

They are becoming bridges between creative work and engineering work.

And that changes how teams build products.

What This Means for Future Developers

If you are learning development today, something important is happening.

The role of developers is shifting.

You are no longer just writing code line by line.

You are working with:

AI assistants
design systems
automated UI generation
connected workflows

Understanding how tools connect together will become just as important as knowing a programming language.

A Small Thought Before You Go

I still remember when building UI meant staring at a design file and translating pixels into code manually.

That was the normal workflow.

But now things are changing.

Design talks to code.

Code talks back to design.

And the gap between the two is finally closing.

The real question now is simple.

What will developers build when this friction disappears? 👀

Inspired by the GitHub announcement about the Figma MCP Server.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

In the AI Era, The Real Skill Is Not Overthinking

Safiullah Korai — Tue, 10 Mar 2026 15:00:00 +0000

This article is 1st part of the Thinking in the AI Era series, where we explore clarity, focus, and building in a world full of digital noise.

A few years ago, choosing a skill felt simple.

You picked something.

You learned it.

You improved with time.

But today things feel different.

The moment someone opens YouTube, Twitter, or any tech blog, they see hundreds of opinions.

Learn AI.

No, build SaaS.

No, become a creator.

No, learn prompt engineering.

No, build startups.

No, learn Web3.

Within ten minutes, a beginner already feels confused.

Suddenly the problem is not lack of opportunity.

The problem is too many opportunities.

And somewhere in this noise, people begin to do something dangerous.

They start overthinking everything they think.

Hey, I’m Safiullah Korai (also known as Shahzaib), a Software Engineer and full-stack Flutter developer. I work on real production apps, experiment with app architecture, and focus on building modern, scalable, and maintainable mobile solutions.

This idea reminded me of a powerful concept from the book Don’t Believe Everything You Think by Joseph Nguyen.

The book explains something simple but life-changing.

Not every thought in your mind deserves to be believed.

And in the AI era, this lesson matters more than ever.

The Problem Is Not AI. It Is Our Thinking.

People often say the tech world is changing too fast.

New tools appear every month.

AI models improve.

Frameworks evolve.

Careers shift.

But the real challenge is not technology.

The real challenge is what happens inside our minds.

A developer today might think:

Should I continue learning Flutter?

Should I switch to AI engineering?

What if this skill becomes useless?

What if someone else is already ahead?

These thoughts keep appearing again and again.

Soon the person stops building anything.

They are not stuck because of lack of skill.

They are stuck because of too much thinking.

Overthinking Creates Problems That Do Not Exist

Our mind is very good at imagining problems.

It creates future scenarios that may never happen.

What if I choose the wrong path?

What if AI replaces this skill?

What if I fail?

But most of these are not real problems.

They are stories created by the mind.

The truth is simple.

Nobody knows the future.

Not developers.

Not experts.

Not influencers.

The only thing anyone can do is choose something and move forward.

The Internet Made Thinking Infinite

Before the internet became so powerful, information was limited.

You had fewer opinions.

Fewer tutorials.

Fewer career choices.

Now everything is available.

Thousands of videos.

Thousands of blog posts.

Thousands of opinions.

Tools like ChatGPT can answer almost any question instantly.

While this is amazing, it also creates a new problem.

Too much advice.

When you keep consuming advice all day, your mind keeps comparing every possible path.

And when every path seems important, none of them gets started.

Builders Think Less. They Build More.

If you observe people who actually succeed in tech, you will notice something interesting.

They do not spend months deciding the perfect path.

They start.

They build small things.

They experiment.

They fail and learn quickly.

Instead of thinking for weeks, they write code.

Instead of worrying about the future, they build the present.

Action gives them something thinking never can.

Experience.

Clarity Does Not Come From Thinking

This is one of the biggest misunderstandings people have.

They believe clarity comes from thinking harder.

But that rarely works.

Clarity comes from doing something.

If you are unsure about Flutter, build five small apps.

If you are curious about AI, experiment with a simple project.

If you want to start writing, publish a few articles.

After action, the mind becomes clear.

Without action, confusion grows.

The Simple Rule for the AI Era

The internet will keep giving you new trends.

Every day there will be something new to learn.

A new framework.

A new tool.

A new opportunity.

If you try to analyze every option, you will never move forward.

So here is a simple rule that might help.

Think less.

Build more.

Consume less.

Create more.

The people who will thrive in the AI era are not the ones who think the most.

They are the ones who start before they feel ready.

A Small Personal Reflection

When I started learning Flutter, I had similar thoughts.

Should I learn something else instead?

Should I move to another technology?

Is this the right path?

These questions kept appearing.

But eventually I realized something simple.

Thinking about different paths never helped me.

Building things did.

Every small project removed a little confusion.

Every experiment created a little clarity.

The Quiet Truth

Your mind will always generate thoughts.

Some useful.

Some unnecessary.

But you do not have to believe every thought you think.

Sometimes the best decision is not the perfect decision.

Sometimes the best decision is simply this.

Choose something.

Start building.

And let the noise of the internet stay where it belongs.

Outside your mind.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

How Flutter Developers Can Use Stitch to Build Client Apps Faster in 2026

Safiullah Korai — Mon, 09 Mar 2026 15:00:00 +0000

AI-driven app design process

A client once told me:

“I don’t care how it looks. I just want an app like Uber, but for groceries.”

No wireframes.

No design system.

No brand guide.

Just an idea.

I’m Safiullah Korai (also known as Shahzaib), a Software Engineer and full-stack Flutter developer. I work on real production apps, experiment with app architecture, and focus on building modern, scalable, and maintainable mobile solutions.

If you are a Flutter developer, you’ve probably been there.

You know how to build logic.

You know how to manage state.

You know how to connect APIs.

But when it comes to design, clients often expect you to magically “make it look good.”

That is where AI tools like Stitch are quietly changing the game.

The New Reality for Flutter Developers

In 2026, being “just a developer” is not enough.

Clients expect:

• Clean UI

• Modern design

• Fast turnaround

• App Store ready polish

But many clients do not hire a UI/UX designer. They come with only a product idea.

Instead of struggling inside design tools for hours, you can now use Stitch to generate professional UI drafts in minutes, then refine them inside Figma before building them in Flutter.

This is not about replacing designers.

It is about empowering developers when designers are not available.

(Client Idea to Flutter App Workflow)

What Is Stitch in Simple Terms?

Stitch is an AI-powered design tool that creates user interfaces from text prompts or sketches.

You can type:

“Create a food delivery app home screen with categories, search bar, and featured restaurants.”

Within seconds, it generates UI screens.

Not rough sketches.

Actual structured layouts.

You can export them to Figma or even generate frontend code.

For a Flutter developer, this means you no longer start from a blank screen.

(Stitch Prompt Interface to Generate Mobile App UI)

(UI Screens Design generated by Stitch)

Scenario 1: Client Has an Idea but No Design

Let’s say your client says:

“I want a fitness app where users can track workouts.”

That is it.

Instead of guessing layout structures, you can:

Step 1 :

Prompt Stitch with a detailed description.

Step 2 :

Generate 3 to 5 UI variations.

Step 3 :

Show those options to the client.

Suddenly, the conversation becomes visual.

Instead of abstract discussion, the client reacts to real screens.

This reduces confusion and saves revision cycles.

Multiple UI Variations from One Prompt (The Previous Design)

Scenario 2: You Are Building Your Own Product

If you are building your own SaaS or mobile app, design often becomes the bottleneck.

You delay launching because “UI is not ready.”

With Stitch:

• Generate MVP screens quickly

• Validate idea with users

• Improve design later

Speed matters in early-stage products.

Stitch helps you move from idea to prototype faster.

How to Integrate Stitch into a Flutter Workflow

Here is a practical workflow you can follow:

Step 1: Define the Core Features

List main screens:

• Home

• Login

• Profile

• Dashboard

Step 2: Prompt Stitch Clearly

Be specific about:

• Theme

• Layout type

• Target audience

• Platform type (mobile or web)

Example prompt:

“Design a clean mobile banking app home screen with balance card, recent transactions, and bottom navigation.”

Step 3: Export to Figma

Import the design into Figma for:

• Adjusting spacing

• Fixing typography

• Aligning brand colors

• Creating reusable components

Step 4: Translate to Flutter Widgets

Now you rebuild the design using:

• Scaffold

• Column

• Row

• ListView

• Custom widgets

Instead of designing from imagination, you replicate from a visual reference.

This improves visual consistency.

(Stitch Design Export to Figma)

Why This Is Powerful for Freelancers

If you are a freelance Flutter developer, this approach gives you an edge.

You can:

• Deliver design mockups faster

• Impress clients with visual proposals

• Reduce back-and-forth revisions

• Increase perceived professionalism

Many freelancers lose projects because their UI mockups look weak.

Stitch helps you present polished drafts early.

How This Can Increase Your Freelance Income

Using AI-assisted UI tools like Stitch is not just about speed.

It is about positioning yourself as a more complete solution for clients.

Here’s how it directly impacts your freelance income:

1. Faster Proposals

Instead of sending text-only proposals, you can attach quick visual mockups generated with Stitch.

Clients understand visuals better than descriptions.

This increases your chances of closing deals.

2. Faster Mockups

What used to take 1–2 days of rough layout experimentation can now take 30 minutes.

Less design struggle means more billable development time.

3. More Clients Impressed

When a client sees multiple UI variations early, you look organized and professional.

Perception matters in freelancing.

Higher perceived expertise = higher rates.

4. Shorter Revision Cycles

Visual alignment happens earlier in the project.

Fewer misunderstandings.

Fewer redesign requests mid-development.

That means:

• Less unpaid rework

• Faster project completion

• More projects per month

And more projects per month means higher overall income.

But Be Careful

AI generates layouts.

It does not understand:

• Real user psychology

• Accessibility deeply

• Long-term product strategy

• Complex UX flows

You still need judgment.

Do not blindly implement everything AI generates.

Use it as a starting point.

You are still the decision maker.

“AI Suggests. Developer Decides.”

Does This Replace Learning UI/UX?

No.

If anything, it makes learning UI/UX more important.

When you understand:

• Spacing

• Hierarchy

• Color balance

• Typography

You can guide AI better.

A developer who understands design fundamentals will use Stitch far more effectively than someone who only types random prompts.

Final Thoughts

Flutter makes building cross-platform apps easier.

Stitch makes designing those apps faster.

Together, they reduce friction between idea and execution.

If your client brings only a concept, you no longer need to panic about design.

You can:

Generate

Refine

Build

Deliver

The future of development is not developer versus designer.

It is human plus AI.

And if you learn how to combine tools like Stitch with your Flutter skills, you will not just build apps.

You will build them smarter.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

Stitch vs Figma: Is AI Replacing UI/UX Designers in 2026?

Safiullah Korai — Sun, 08 Mar 2026 15:00:00 +0000

I still remember the first time I opened Figma.

A blank canvas.

A few frames.

Some rectangles pretending to be buttons.

That was design.

You dragged. You aligned. You adjusted spacing. You changed fonts. You argued with padding. Slowly, a screen was born.

Now imagine typing one sentence:

“Create a modern fintech dashboard with a dark theme and analytics cards.”

And within seconds, full screens appear. Clean layout. Color palette ready. Buttons styled. Even code generated.

That is what Google Stitch is doing.

And if you are into UI/UX, product design, or frontend development, this moment matters.

During this journey, I have worked closely with designers, design systems, and handoff workflows.

I have seen how much time goes into turning ideas into real interfaces.

And I have also seen how small design decisions can completely change the quality of a product.

So when I saw Google introduce Stitch, an AI-powered design tool that generates complete UI screens from text prompts and images, I immediately realized something important.

This is not just another design tool.

The Shift No One Saw Coming

For years, tools like Figma have been the home of designers. From wireframes to polished UI, everything lived there. Teams collaborated. Developers inspected designs. Startups launched products.

Then AI entered the room.

Google introduced Stitch, an AI-powered design tool that generates user interfaces from text prompts and images.

Not templates.

Not partial layouts.

Complete screens.

And suddenly, the design process feels different.

Design process with AI and UI tools

What Exactly Is Stitch?

Stitch is an AI design tool that lets you describe an interface in plain language. It then generates UI screens based on your description.

You can:

• Type a prompt

• Upload a sketch

• Upload a screenshot

• Ask for multiple variations

• Export to Figma

• Export frontend code

Instead of manually building every card, button, and section, Stitch handles the first draft.

It feels like brainstorming with a machine.

(SCREENSHOT 1: Stitch Prompt Input Interface)

(SCREENSHOT 2: Generated UI Variations from Same Prompt)

Why This Feels Different From Other AI Tools

We have seen AI image generators. We have seen AI code assistants.

But Stitch sits in a powerful position.

It connects design and development.

It does not just generate a picture. It creates structured UI layouts that can move into Figma or directly into code.

That reduces the gap between idea and execution.

For startup founders, solo developers, and product teams, that speed matters.

But Where Does Figma Stand Now?

Here is the important part.

Figma is not disappearing.

Figma is still where serious design work happens.

Collaboration

Design systems

Component libraries

Prototyping

Team feedback

Developer handoff

Even if Stitch generates the first version, designers still refine inside Figma.

Think of it like this.

Stitch gives you a strong first draft.

Figma helps you perfect it.

(SCREENSHOT 3: Stitch Design Import into Figma)

A Realistic Workflow in 2026

Let’s imagine you are building a fitness app.

Step 1 :

You prompt Stitch:

“Create a mobile fitness app home screen with workout stats and a progress chart.”

Step 2 :

Stitch generates 3 design variations.

Step 3 :

You export the best version to Figma.

Step 4 :

Inside Figma, you adjust spacing, improve typography, fix accessibility, align with brand colors.

Step 5 :

You export assets or code.

This workflow can save days in early design stages.

But it does not remove the need for design thinking.

Is AI Replacing UI/UX Designers?

This is the question everyone is asking.

The short answer is no.

AI can generate layouts.

It can suggest colors.

It can create structured components.

But it does not understand:

• Real user pain

• Accessibility depth

• Cultural context

• Business goals

• Long term product strategy

Design is not just pixels. It is problem solving.

Stitch accelerates the process. It does not replace the human behind it.

Why Developers Should Care

If you are a Flutter developer, React developer, or frontend engineer, this shift is important.

Instead of waiting days for UI drafts, you can prototype faster.

You can validate ideas earlier.

You can even generate quick UI concepts for client pitches.

Stitch lowers the entry barrier for clean interface design.

But you still need design sense to choose what actually works.

The Bigger Picture: AI + Design Is Just Beginning

We are moving into a phase where:

• AI generates first drafts

• Designers refine

• Developers implement faster

• Iterations happen quicker

The distance between idea and product is shrinking.

And that is exciting.

Because the faster you test ideas, the faster you learn.

Should You Learn Figma in 2026?

Yes.

More than ever.

AI tools will come and go.

But understanding layout, hierarchy, spacing, typography, and user behavior will always matter.

Tools change.

Principles stay.

If you know design fundamentals, you can use Stitch better than someone who only knows prompting.

“Tools Change. Principles Stay.”

Final Thoughts

When I first opened Figma, design felt manual and slow.

Today, with Stitch, design feels instant.

But here is the truth.

Speed is powerful.

Understanding is powerful.

Together, they are unstoppable.

Stitch is not the end of UI/UX design.

It is the beginning of a new design workflow.

And if you learn how to combine AI with real design thinking, you will not just survive this shift.

You will lead it.

Thanks for reading! I write about Flutter, AI in dev, and learning smarter as a developer. Follow for more!

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

In the Era of AI, Why Do I Still Choose Flutter?

Safiullah Korai — Wed, 04 Mar 2026 15:20:00 +0000

Everywhere I look in 2026, the conversation is the same.

AI is writing code.

AI is designing UI.

AI is debugging errors.

AI is generating entire applications in minutes.

Sometimes I open my laptop, scroll through tech news, and wonder the same thing many developers are quietly thinking.

If AI can build apps, why should anyone still learn Flutter?

Why invest time in mastering app development at all?

It is not a silly question.

It is a serious one.

And as someone who builds products for a living, I had to answer it for myself first.

A Small Flashback

There was a time when building an app meant choosing sides.

If you wanted an iPhone app, you learned one language.

If you wanted an Android app, you learned another.

If you wanted a web app, that was a different world entirely.

Development was divided. Time was divided. Teams were divided.

Then tools started changing.

And one of the tools that changed everything for me was Flutter.

Hello, I am Safiullah Korai. I am a Software Engineer and a full stack Flutter developer. Over the past few years, I have spent countless hours building mobile applications, experimenting with architecture, fixing real production bugs, and understanding what makes modern app development efficient and scalable.

I have seen trends come and go.

But AI feels different.

It feels bigger.

So the real question is not whether AI is powerful.

The real question is this:

Where do developers stand in this new era?

AI Is Powerful. But It Is Still a Tool.

I use AI almost every day.

I use it to brainstorm ideas.

I use it to speed up repetitive code.

I use it to review logic.

It saves time.

But I have noticed something important.

AI can generate.

It cannot take responsibility.

When an app crashes in production, AI does not answer to users.

When architecture decisions fail at scale, AI does not sit in meetings explaining tradeoffs.

Developers do.

AI can give you a starting point.

It cannot give you ownership.

And that difference matters.

Apps Need Structure, Not Just Screens

Yes, AI can generate UI screens.

But can it:

Design scalable architecture for a startup expecting growth?
Decide performance tradeoffs for low-end devices?
Plan state management for complex flows?
Think long-term about maintainability?

Not independently.

That responsibility still belongs to someone who understands systems.

And this is where Flutter still matters.

Flutter gives you control over structure. Over layout behavior. Over state flow. Over platform integration.

It is not just about writing widgets.

It is about understanding how everything connects.

In the AI era, speed is increasing.

But deep understanding is still rare.

And rare skills always carry value.

Why I Still Choose Flutter Specifically

There are many frameworks available.

So why Flutter?

Because Flutter represents efficiency without sacrificing control.

I can build for Android, iOS, Web, and Desktop using one codebase.

I can prototype quickly.

I can iterate fast.

When AI reduces thinking time, Flutter reduces production time.

Together, they create leverage.

And leverage is what modern developers need.

The Difference Between Code and Product Thinking

Building an app is not just writing functions.

It involves:

Understanding user behavior
Designing intuitive navigation
Handling edge cases
Planning for scale
Shipping updates safely

AI can assist with fragments of this.

But someone still needs to see the full picture.

When I build an app, I am not just writing code. I am solving a real problem for real users.

Flutter is the toolkit.

AI is the assistant.

I remain the architect.

And that mindset changes everything.

The Human Edge in 2026

In 2026, the competitive advantage is no longer typing speed.

It is judgment.

Knowing:

When to optimize
When to simplify
When to ship
When to refactor

AI does not carry responsibility.

Developers do.

And the deeper your fundamentals, the more powerful AI becomes in your hands.

Without fundamentals, AI suggestions feel confusing.

With strong Flutter fundamentals, AI becomes a multiplier.

Why App Development Still Matters

Some people believe AI will eliminate developers.

What I see instead is a shift.

Repetitive low-skill work is shrinking.

High-understanding product-focused work is growing.

Businesses still need:

Mobile apps
SaaS dashboards
Customer platforms
Internal systems

Those problems did not disappear.

AI accelerates building.

It does not replace ownership.

If you deeply understand Flutter, you are not just someone who copies code.

You are someone who can turn ideas into usable digital products.

That skill remains relevant.

Choosing Flutter in the AI Era Is Not Fear. It Is Strategy.

For me, choosing Flutter today is not about ignoring AI.

It is about combining forces.

Flutter gives me structure.

AI gives me acceleration.

I do not fight AI.

I build with it.

The developers who will win in this era are not the ones afraid of automation.

They are the ones who understand systems deeply enough to guide automation.

Final Thoughts

AI is changing how we write code.

It is not changing why we build software.

People still need solutions.

Businesses still need products.

Users still need smooth experiences.

Flutter remains a practical and efficient way to build those experiences across platforms.

And if you truly understand it, AI becomes your assistant, not your replacement.

If you want to build with clarity instead of confusion, I am currently covering 100 Flutter widgets in my series, Flutter Code & Concepts. The goal is simple. Strong fundamentals. Clear understanding. Practical knowledge.

The tools are evolving.

The builders still matter.

And I choose to be one of them.

🧭 Want to Learn Smarter as a Developer?

I write about Flutter, developer mindset, and learning techniques. Follow me here on Medium for more practical tech learning insights.

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

Flutter in 2026: What It Is, Why It Matters, and Why App Development Is a Skill Worth Learning?

Safiullah Korai — Sat, 28 Feb 2026 17:00:00 +0000

There was a time when building an app meant choosing sides.

If you wanted an iPhone app, you learned one language.

If you wanted an Android app, you learned another.

If you wanted a web app, that was a completely different world.

Development was divided. Time was divided. Teams were divided.

Then tools started changing.

And one of the tools that changed the conversation completely was Flutter.

Today in 2026, Flutter is not just an option. For many developers and companies, it is the first choice.

Hello, I am Safiullah Korai. I am a Software Engineer and a full stack Flutter developer. Over the past few years, I have spent countless hours building mobile applications, experimenting with architecture, and understanding what makes modern app development efficient and scalable.

I have seen how cross-platform development evolved. I have seen what works, what creates friction, and what actually delivers results in real projects.

But before we talk about demand or money, let’s understand what Flutter actually is.

What Is Flutter in Simple Words?

Flutter is a toolkit created by Google that allows developers to build applications for:

Android
iOS
Web
Windows
macOS
Linux

All from a single codebase.

Instead of writing separate apps for every platform, you write your code once using the Dart language. Flutter then turns that code into real, fast, production-ready applications.

But here is what makes it special.

Flutter does not rely on the platform’s default design components. It draws everything itself. That is why Flutter apps look consistent and smooth across devices.

You control every pixel on the screen.

For developers, that means freedom.

For businesses, that means consistency.

For users, that means better experience.

Why Flutter Feels Different

Technology becomes powerful when it removes friction.

Flutter removes a lot of friction.

One Codebase, Multiple Platforms

In traditional development, companies needed separate teams for Android and iOS.

That meant:

More hiring
More cost
More maintenance
More time

With Flutter, one team can build for multiple platforms. Updates are faster. Bugs are fixed once instead of twice.

Source: Based on developer survey trends including Statista and industry reports (2019–2024).

Flutter’s growth over the past few years shows how quickly it moved from emerging tool to mainstream framework.

Fast Development Cycle

Flutter has a feature called hot reload.

When you change something in your code, you see the result almost instantly. You do not restart the entire application.

This encourages experimentation. It reduces frustration. It keeps you in a creative flow.

For someone learning app development, this matters more than you think. Faster feedback means faster growth.

Illustration comparing iteration speed between traditional native development and Flutter using hot reload. Conceptual comparison based on documented workflow differences.

UI That Is Predictable and Structured

Flutter works on a simple idea.

Everything is a widget.

Text is a widget.
Button is a widget.
Row is a widget.
Padding is a widget.

Once you understand this structure, building interfaces becomes logical instead of confusing.

This is one of the reasons many developers find Flutter easier to reason about compared to other frameworks.

Why App Development Is a Skill Worth Choosing in 2026

Let’s step back for a moment.

Why should someone even consider app development as their main skill?

Because software is no longer optional in business.

Every business wants:

A mobile presence
A booking system
A dashboard
A marketplace
A custom internal tool

And most of these solutions live inside apps.

The world is mobile-first now. People shop on apps. Learn on apps. Communicate on apps. Manage finances on apps.

If you understand how to build apps, you are building the digital front door of modern businesses.

That is not a small role.

Demand for Flutter in 2026

In 2026, companies are looking for developers who can deliver faster without increasing costs.

Flutter fits that requirement.

Job listings across freelance platforms and remote job boards continue to include Flutter as a required or preferred skill.

Startups prefer it for MVP development.
Agencies prefer it for client projects.
Companies prefer it for unified cross-platform strategy.

Source: Aggregated trend representation based on job listings from platforms such as LinkedIn, Indeed, and remote job boards (2020–2026).

This steady upward movement reflects increasing confidence in Flutter across the developer community.

How Developers Earn With Flutter

Learning a skill is one thing. Turning it into income is another.

Here are realistic paths people are using in 2026.

Freelancing

Many developers build:

Startup MVPs
E-commerce apps
Delivery systems
Booking platforms
Internal business tools

Freelance rates typically range:

Beginner level: $15–30 per hour
Intermediate level: $30–70 per hour
Advanced level: $80–150 per hour

Estimated hourly rate ranges based on freelance marketplaces including Upwork and Fiverr (2024–2026 averages).

Full-Time Roles

Flutter developers are hired as:

Mobile Developers
Cross-Platform Engineers
UI Developers

Salary varies by region, but globally the demand remains strong. In tech-focused markets, experienced developers earn competitive salaries comparable to other modern stacks.

Building Your Own Products

This is where things get interesting.

Some developers use Flutter to build their own apps:

Subscription-based tools
SaaS dashboards
Educational apps
Productivity apps

Because development time is shorter, the cost of experimenting is lower.

You can test ideas faster.

You can launch updates faster.

You can pivot faster.

Illustrative distribution based on common income paths observed among Flutter developers globally.

The Bigger Picture

Flutter is not magic.

It still requires:

Understanding of programming basics
Clean architecture thinking
Good UI decisions
Problem solving skills

But what it offers is efficiency.

In a world where speed matters, efficiency wins.

And app development as a core stack is not just about coding. It is about building real-world digital products that people use daily.

That is a powerful position to be in.

If You Want to Go Deeper

Flutter is not just a framework.

It is a way of thinking about modern product development. It teaches you how to structure ideas, how to design systems, and how to ship real applications that people actually use.

In 2026, tools are evolving fast. AI can generate code. It can scaffold interfaces. It can automate repetitive tasks.

But understanding still matters.

The developers who grow in this era are not the ones who rely only on automation. They are the ones who understand architecture, scalability, and user experience at a fundamental level.

That is why I am building and documenting my journey publicly.

Through my Flutter Code & Concepts series, I am breaking down Flutter widget by widget, concept by concept, focusing on clarity and real-world usage.

If this article helped you see Flutter more clearly, leave a comment and share your thoughts. I would love to know what stage you are in on your development journey.

Data in this article is compiled from publicly available developer surveys, marketplace trends, and job listing platforms between 2019 and 2026. Some charts represent aggregated industry patterns rather than single-source datasets.

🧭 Want to Learn Smarter as a Developer?

I write about Flutter, developer mindset, and learning techniques. Follow me here for more practical tech learning insights.

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

Who is Safiullah Korai? Flutter Developer Today, AI Engineer Tomorrow

Safiullah Korai — Mon, 23 Feb 2026 17:00:00 +0000

Hi, I’m Safiullah Korai but many people also know me as Shahzaib.

I’m a Software Engineer, a passionate Flutter Developer, a community contributor, and a lifelong learner who believes that technology is not just code but it’s impact.

If you’re reading this, you’re probably curious about who I am and what you can expect from this blog. So let me introduce myself properly.

I am from Pano Akil, Sukkur, Sindh, Pakistan.

Before I talk about technology, let me tell you where it all began.

🧐 Early Life and Curiosity

During my college days, I was always active. I consistently secured first position and stayed involved in different activities. I was never the type to sit quietly and just pass exams. I wanted to understand things deeply and perform at my best.

But the real turning point came when I got my first mobile phone.

I was in 8th class when I received it. For many people, a mobile phone is just for calls or social media. For me, it was something magical.

I was fascinated by applications.

I used to explore every feature. I would install apps, delete them, test them, and wonder how they were built. Questions kept coming to my mind.

How does this button work?
How does this app store data?
How are these interfaces designed?

That small device triggered a big dream.

From that time, I decided I wanted to become a Software Engineer.

💻 Entering Software Engineering

Years later, I got admission into the Software Engineering department. It felt like I was stepping into the world I had imagined since 8th class.

University was not just about classes for me. It was about exploration.

I worked on different technologies and tools. I explored web development and built multiple projects. I worked as a WordPress developer and created websites. I designed using Canva and even built web projects using Canva. I explored data visualization with Power BI. I kept learning, experimenting, and building.

But one technology truly connected with me.

Flutter.

When I started working with Flutter, I felt that same excitement I felt when I first explored apps on my mobile. Now I was not just using applications. I was building them.

Today, I have a strong command of Flutter and I focus on building clean, scalable, and user friendly mobile applications. I genuinely enjoy the process of turning an idea into a real app that people can use.

🏆 Communities & Leadership Experience

My journey was not limited to coding alone.

One thing that shaped me deeply is community work.

I actively worked in different communities and organizations

I’ve actively contributed to and worked with:

Women Techmakers (WTM) Hyderabad Community
Google Developer Students Club (GDSC) MUET Khairpur
ASME (American Society of Mechanical Engineering)
ETL (Empowerment Through Learning) — a US-based organization operating in Pakistan
Microsoft Learn Student Ambassador (Beta MLSA)

Through these communities, I’ve:

Organized multiple tech events
Managed teams
Worked on branding & marketing
Built technical projects
Collaborated with amazing people Community work taught me leadership, networking, and the real meaning of growth.

⚒ What I Am Focused On Now

Currently, I am focused on Flutter app development and strengthening my software engineering fundamentals.

At the same time, I am building my path toward my next big goal.

I want to become an AI Engineer.

Artificial Intelligence is shaping the future, and I want to be part of that transformation. Maybe if you are reading this after a year, I am already an AI Engineer. Or maybe I am still learning and building toward it.

Because learning never ends.

And I Love that about technology. ❤

✍️ What I’ll Be Writing About

On this blog, you can expect:

Flutter tutorials (beginner to advanced)
Mobile app architecture concepts
Real-world development experiences
Community building insights
Tech career guidance
AI learning journey
Productivity & growth in tech This blog is not just about code.

It’s about building skills, mindset, and impact.

🌍 My Work & Portfolio

I’ve worked on:

WordPress websites — Check out here
Canva-designed web projects — Check out here
Web development projects — GitHub
Data dashboards with Power BI
Flutter mobile applications

📚 Beyond Technology

I am not very socially active, but I always keep myself updated with the latest tech trends. I believe technology is a race that never stops, and if you stop learning, you fall behind.

Apart from coding, I love reading books. Especially books about self improvement, mindset, growth, and finance.

I enjoy reading about topics like self help and the psychology of money. If I learn something valuable from a book, I will definitely share it here with you.

Growth is not only about technical skills. It is also about mindset.

💡 Who Am I Really?

I am someone who:

Loves building things
Believes in continuous improvement
Values community
Dreams big
Works silently And trusts consistency more than motivation.

I’m not perfect.

I’m evolving.

Let’s Connect!

If you would like to follow my journey, connect with me on:

Instagram ✦ LinkedIn ✦ GitHub

Let’s learn and grow together.

Final Thoughts
From a curious 8th class student exploring apps on his first mobile phone to a Software Engineer building applications today, the journey has been exciting.

And this is just the beginning.

🧭 Want to Learn Smarter as a Developer?

I write about Flutter, developer mindset, and learning techniques. Follow me here on DEV.to for more practical tech learning insights.

✍️ Written by Safiullah Korai — Flutter Developer, Tech Writer & Lifelong Learner.

What do you think about AI? is it really gonna take our jobs or gonna create more jobs?

Safiullah Korai — Mon, 23 Feb 2026 15:12:09 +0000