In 2025, software development crossed a quiet threshold. In our latest Octoverse report, we found that the fastest-growing languages, tools, and open source projects on GitHub are no longer about shipping more code. Instead, they’re about reducing friction in a world where AI is helping developers build more, faster.

By looking at some of the areas of fastest growth over the past year, we can see how developers are adapting through: 

• The programming languages that are growing most in AI-assisted development workflows.
• The tools that win when speed and reproducibility matter.
• The areas where new contributors are showing up (and what helps them stick).

Rather than catalog trends, we want to focus on what those signals mean for how software is being built today and what choices you might consider heading into 2026. 

The elephant in the room: Typescript is the new #1

In August 2025, TypeScript became the most-used language on GitHub, overtaking Python and JavaScript for the first time. Over the past year, TypeScript added more than one million contributors, which was the largest absolute growth of any language on GitHub. 

Python also continued to grow rapidly, adding roughly 850,000 contributors (+48.78% YoY), while JavaScript grew more slowly (+24.79%, ~427,000 contributors). Together, TypeScript and Python both significantly outpaced JavaScript in both total and percentage growth. 

This shift signals more than a preference change. Typed languages are increasingly becoming the default for new development, particularly as AI-assisted coding becomes routine. Why is that?

In practice, a significant portion of the failures teams encounter with AI-generated code surface as type mismatches, broken contracts, or incorrect assumptions between components. Stronger type systems act as early guardrails: they can help catch errors sooner, reduce review churn, and make AI-generated changes easier to reason about before code reaches production. 

If you’re going to be using AI in your software design, which more and more developers are doing on a daily basis, strongly typed languages are your friend.

Here’s what this means in practice: 

• If you’re starting a new project today, TypeScript is increasingly becoming the default (especially for teams using AI in daily development).
• If you’re introducing AI-assisted workflows into an existing JavaScript codebase, adding types may reduce friction more than switching models or tools.

Python is key for AI

Contributor counts show who is using a language. Repository data shows what that language is being used to build. 

When we look specifically at AI-focused repositories, Python stands apart. As of August 2025, nearly half of all new AI projects on GitHub were built primarily in Python. 

This matters because AI projects now account for a disproportionate share of open source momentum. Six of the ten fastest-growing open source projects by contributors in 2025 were directly focused on AI infrastructure or tooling.

Python’s role here isn’t new, but it is evolving. The data suggests a shift from experimentation toward production-ready AI systems, with Python increasingly anchoring packaging, orchestration, and deployment rather than living only in notebooks. 

Moreover, Python is likely to continue to grow in 2026, as AI continues to gain support and additional projects.

Here’s what this means in practice:

• Python remains the backbone of applied AI work from training and inference to orchestration.
• Production-focused Python skills such as packaging, typing, CI, and containerization are becoming more important than exploratory scripting alone. 

A deeper look at the top open source projects

Looking across the fastest-growing projects, a clear pattern emerges: developers are optimizing for speed, control, and predictable outcomes. 

Many of the fastest-growing tools emphasize performance and minimalism. Projects like astral-sh/uv, a package and project manager, focus on dramatically faster Python package management. This reflects a growing intolerance for slow feedback loops and non-deterministic environments. 

Having just one of these projects could be an anomaly, but having multiple indicates a clear trend. This trend aligns closely with AI-assisted workflows where iteration speed and reproducibility directly impact developer productivity. 

Here’s what this means in practice: 

• Fast installs and deterministic builds increasingly matter as much as feature depth.
• Tools that reduce “works on my machine” moments are winning developer mindshare.

Where first-time open source contributors are showing up

As the developer population grows, understanding where first-time contributors show up (and why) becomes increasingly important. 

Projects like VS Code and First Contributions continued to top the list over the last year, reflecting both the scale of widely used tools and the persistent need for low-friction entry points into open source (notably, we define contributions as any content-generating activity on GitHub).

Despite this growth, basic project governance remains uneven across the ecosystem. README files are common, but contributor guides and codes of conduct are still relatively rare even as first-time contributions increase.

This gap represents one of the highest-leverage improvements maintainers and open source communities can make. The fact that most of the projects on this list have detailed documentation on what the project is and how to contribute shows the importance of this guidance.

Here’s what this means in practice: 

• Clear documentation lowers the cost of contribution more than new features.
• Contributor guides and codes of conduct can help convert curiosity into sustained participation.
• Improving project hygiene is often the fastest way to grow a contributor base.

Putting it all together

Taken together, these trends point to a shift in what developers value and how they choose tools. 

AI is no longer a separate category of development. It’s shaping the languages teams use, which tools gain traction, and which projects attract contributors. 

Typed languages like TypeScript are becoming the default for reliability at scale, while Python remains central to AI-driven systems as they move from prototypes into production. 

Across the ecosystem, developers are rewarding tools that minimize friction with faster feedback loops, reproducible environments, and clearer contribution paths.

Developers and teams that optimize for speed, clarity, and reliability are shaping how software is being built.

As a reminder, you can check out the full 2025 Octoverse report for more information and make your own conclusions. There’s a lot of good data in there, and we’re just scratching the surface of what you can learn from it.

The post What the fastest-growing tools reveal about how software is being built appeared first on The GitHub Blog.

Topics covered in this episode:

• django-bolt: Faster than FastAPI, but with Django ORM, Django Admin, and Django packages
• pyleak
• More Django (three articles)
• Datastar
• Extras
• Joke

Watch on YouTube

About the show

Sponsored by us! Support our work through:

• Our courses at Talk Python Training
• The Complete pytest Course
• Patreon Supporters

Connect with the hosts

• Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky)
• Brian: @brianokken@fosstodon.org / @brianokken.bsky.social
• Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky)

Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 11am PT. Older video versions available there too.

Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it.

Brian #1: django-bolt : Faster than FastAPI, but with Django ORM, Django Admin, and Django packages

• Farhan Ali Raza
• High-Performance Fully Typed API Framework for Django
• Inspired by DRF, FastAPI, Litestar, and Robyn
• Django-Bolt docs
• Interview with Farhan on Django Chat Podcast
• And a walkthrough video

Michael #2: pyleak

• Detect leaked asyncio tasks, threads, and event loop blocking with stack trace in Python. Inspired by goleak.
• Has patterns for
  • Context managers
  • decorators
• Checks for
  • Unawaited asyncio tasks
  • Threads
  • Blocking of an asyncio loop
  • Includes a pytest plugin so you can do @pytest.mark.no_leaks

Brian #3: More Django (three articles)

• Migrating From Celery to Django Tasks
  • Paul Taylor
  • Nice intro of how easy it is to get started with Django Tasks
• Some notes on starting to use Django
  • Julia Evans
  • A handful of reasons why Django is a great choice for a web framework
    • less magic than Rails
    • a built-in admin
    • nice ORM
    • automatic migrations
    • nice docs
    • you can use sqlite in production
    • built in email
  • The definitive guide to using Django with SQLite in production
    • I’m gonna have to study this a bit.
    • The conclusion states one of the benefits is “reduced complexity”, but, it still seems like quite a bit to me.

Michael #4: Datastar

• Sent to us by Forrest Lanier

• Lots of work by Chris May

• Out on Talk Python soon.

• Official Datastar Python SDK

• Datastar is a little like HTMX, but

  • The single source of truth is your server

  • Events can be sent from server automatically (using SSE)

    • e.g

      yield SSE.patch_elements(
          f"""{(#HTML#)}{datetime.now().isoformat()}"""
      )
      

• Why I switched from HTMX to Datastar article

Extras

Brian:

• Django Chat: Inverting the Testing Pyramid - Brian Okken
  • Quite a fun interview
• PEP 686 – Make UTF-8 mode default
  • Now with status “Final” and slated for Python 3.15

Michael:

• Prayson Daniel’s Paper tracker
• Ice Cubes (open source Mastodon client for macOS)
• Rumdl for PyCharm, et. al
• cURL Gets Rid of Its Bug Bounty Program Over AI Slop Overrun
• Python Developers Survey 2026

Joke: Pushed to prod

Download audio: https://pythonbytes.fm/episodes/download/468/a-bolt-of-django.mp3

Hello Champions, and Happy New Year!
Here’s a recap and top Q+A from our first monthly call of 2026, featuring Copilot Pages with the Copilot Pages & Microsoft Loop product team members Constance Gervais, Senior Product Manager and Oby Omu, Product Manager.

We kicked off the call with two major community event announcements. First, the SharePoint 25th Birthday Celebration is happening on March 2, 2026—a free digital event highlighting SharePoint’s most defining innovations and offering a forward‑looking view into its AI‑driven future, with insights from Microsoft leaders. We also shared that the Microsoft 365 Community Conference returns April 21–23, 2026 in Orlando, where attendees can connect with Microsoft experts, explore hands‑on labs, and dive into the latest advancements across AI and Microsoft 365.

Constance introduced Copilot Pages as the next evolution after Copilot Chat—turning conversational output into flexible, collaborative canvases. She highlighted how pages support rich content types, enable sidebyside editing with Copilot, and can be generated instantly using intent based prompts like “create a page.” She also shared practical prompts attendees can use to build structured pages, refine content, or even experiment with interactive UI prototypes.‑by‑side editing with Copilot, and can be generated instantly using intent‑based prompts like “create a page.” She also shared practical prompts attendees can use to build structured pages, refine content, or even experiment with interactive UI prototypes.

Oby followed with a live demo showcasing how Copilot Pages simplify research, ideation, and content creation. She demonstrated starting with the Researcher agent, adding results into a page to further refine the research output, and then generating a PowerPoint from that page to quickly communicate key takeaways to colleagues — highlighting how Pages seamlessly move content into whichever M365 app best supports your next step. Her walkthrough also demonstrated real‑time editing with Copilot — including turning text into tables, shortening sections, and adjusting tone and formatting with Copilot shortcuts — as well as restoring previous page versions.

She showed how Pages are built for collaboration with capabilities like comments, content author identification, presence indicators, @mentions, and sharing — with particular emphasis on sharing a page as a component in M365 apps such as Teams to enable real‑time collaboration without leaving the app. Lastly, she previewed emerging capabilities for creating interactive UI experiences using code‑backed pages.

We wrapped with a live Q+A session featuring Constance, Oby and our colleague Patrick Gan, Principal Product Manager from Copilot Pages and Microsoft Loop product team, who helped answer attendees’ top questions.

Prompts to try out!

Creating a page  (“Create a page” )

• Create a wiki for onboarding new team members that explains our team’s goals, key tools, workflows, and who to contact for help. Create this as a polished page with sections.
• Based on our recent chat in the [Team/Project/Support] channel, create an FAQ page covering common questions and standard responses
• Convert this chat thread into a page with a table of decisions, rationale, and tasks. Flag unresolved questions. Post a 3‑bullet recap at the top for a quick scan. Output directly on a Page.

Editing a page when page is open

• Add an introduction section to the top of the Page, and a short table of contents based on the themes or headers
• Update references from “2024” to “2025” and update headers to be collapsible
• Turn the 3rd paragraph into a diagram with accessibility labels and a title

Generating visual content (“create an interactive UI”)  - currently rolling out in Web tab

• Make an interactive UI explaining Microsoft Environmental Strategy.
• Create an interactive UI that helps me manage my weekly team scrum. It should randomize the order of participants, time everyone with 3 minutes to speak and remind them to mention achievements, help needed, and fun plans for the weekend.
• Build an interactive UI seating chart that lets me explore different seating layouts based on the dimensions of the room and the number of people registered for my conference

Try out the new Copilot Pages features and share your feedback! Download Microsoft 365 Copilot App | Microsoft 365

 

Q+A from this month's session:

1. Can Copilot Pages be shared with users who don’t have an M365 Copilot license?

Answer: Yes. Anyone with an M365 license can access and use Copilot Pages; only certain features (like Researcher) require the paid Copilot license.

2. Is a Copilot Page the same as a Power Page?

Answer: No. Copilot Pages are separate and built leveraging the Loop experience; they are not connected to Power Pages.

3. Why don’t I see the Researcher agent in my Copilot app?

Answer: Possible reasons include:

1. You don’t have an M365 Copilot license,
2. Your admin has disabled agents, or
3. The feature hasn’t rolled out to your tenant yet.

4. What’s the difference between free Copilot Chat and paid M365 Copilot?

Answer:
• Free Copilot Chat: Web only grounding.
• Paid M365 Copilot: Web + Work grounding, including files, emails, meetings, SharePoint/OneDrive content.

5. Do Copilot Pages have version history?

Answer: Yes. You can view and restore past versions of a page.

6. Does the post call Copilot experience require the meeting to be recorded?

Answer: Yes. Copilot depends on having a meeting recording available.

7. Can Copilot-generated PowerPoints use corporate branded templates?

Answer: Yes. You can apply company templates by starting from a branded deck or using Designer-supported templates.

8. Is Copilot Memory available for saving tone or communication preferences?

Answer: Yes. Copilot Memory can store preferred writing styles; custom Agents can also help maintain tone.

9. Are interactive UI pages available to everyone?

Answer: No. This feature is rolling out and currently only available in the Web tab for some users.

10. How do I reopen a Copilot Page after closing it?

Answer: Pages appear in the Copilot Library and in the Loop app (Recent Pages). Both access the same file.

11. Does free Copilot Chat ever access my organization’s data?

Answer: Not automatically. It only uses your data when you manually upload or attach a file.

12. Can admins control who creates agents?

Answer: Yes. Tenant admins can govern agent creation policies.

13. Does Outlook’s Agenda/Loop component behave the same as Loop in Teams?

Answer: No. Some experiences appear similar but function differently across apps, leading to user confusion. The product team is working on alignment.

14. Is it possible to export a Copilot Page to a SharePoint Page?

Answer: Not currently but can you say more of what you might want to do? We are always interested in learning new scenarios!

15. Can I automate tone or message style based on my manager’s patterns?

Answer: Yes. This can be done using Copilot Memory or by building a custom agent with your preferred tone instructions.

16. Can Copilot Pages be converted into Word or PowerPoint?

Answer: Yes. Pages can generate Word documents, PowerPoints, or PDFs from the Page tool bar menu.

17. Can I use Pages in Teams without leaving the chat?

Answer: Yes. Pages can be shared as components that update live inside Teams chat.

18. Do components update in real time for all collaborators?

Answer: Yes. Live presence and simultaneous edits are supported.

19. Can Pages be used without Loop Workspaces?

Answer: Yes. Even if your organization hasn’t enabled Workspaces, Pages still function and can be shared individually.

20. Can users without Loop or Pages access embedded components?

Answer: Yes, as long as they have M365 identity and access permissions.

21. Can I upload my own template for Copilot-generated presentations?

Answer: Yes — Copilot honors the template used when starting from an existing branded file.

22. Why can’t I see Pages in Teams?

Answer: You may need to access Copilot through the browser (“work/web” toggle) or your admin may have disabled features.

23. Can you embed a Copilot Page inside SharePoint?

Answer: Not natively today. You can share links/components, but not publish as a SharePoint page.

24. Is it possible to get list of prompts/steps done for the demo? As it be a big help to run something similar for our organization.

Answer: yes we will try to share! We are also doing a webinar on this so stay tuned :-)

25. How can you organize Pages?

Answer: You can try and organize your pages with Copilot Notebooks. In the page header you'll find a "..." where you can Add to Notebook.

26. What would be the difference between app building in Copilot Pages vs App Builder Frontier agent ?

Answer: Copilot Pages stored and shared like a file. App Builder will create an application that can be deployed to your organization. With App Builder you can also connect the app to Dataverse where as Copilot Pages are more lightweight.

27. 
    Can Copilot create a PowerPoint in your company's PowerPoint-branded template from Copilot pages?

Answer: Yes it can! If your company has connected branded templates.

28. Please advise if M365 copilot chat that comes with the M365 business premium license has direct access to your company data, there is confusion from staff when looking at your M365 copilot hub page where there is a copilot chat overview however I don't think they are the same thing, can you confirm that the M365 paid copilot chat and the M365 included copilot chat are the same and therefore has access to your company data -hopefully I am making sense

Answer: Business Premium users will see both Work and Web as options for Chat - meaning that they can query Copilot on items in their tenant. Customers who don't have the Copilot license but have access to Copilot Chat, and that chat is only based on the web.

29. It seems like copy/paste component is like Loop, is there a comparison somewhere?

Answer: Yes, Pages are very similar to Loop and can be shared like Loop components.

30. Does the call need to be recorded for the after call experience to be available with Copilot regarding the new feature announced on the call today?

Answer: Yes, the call needs to be recorded, or have transcription turned on, in order to use Copilot on the call itself.

31. When it creates a page is it loop and where does it save?

Answer: Copilot Pages are stored in SharePoint Embedded. They are based Loop but are slightly different - see this faq! Frequently asked questions about Microsoft 365 Copilot Pages - Microsoft Support

32. Is this page referring to Power Pages, or is it a separate page feature within Copilot?

Answer: This is a separate feature from power pages

33. Do pages or these components have version history ? 

Answer: Yes, Pages have version history! View or restore previous versions of Microsoft 365 Copilot Pages

34. Where exactly do Copilot Pages and Copilot Notebooks live?

Answer: They are stored as a .page file in SharePoint Embedded, inside a user-owned container. For more information please read: Overview of Copilot Pages and Copilot Notebooks storage | Microsoft Learn

35. If a user leaves the organization, how can admins or managers access their Copilot Pages?
    Answer: Pages follow the same governance pattern as OneDrive:

• The SharePoint embedded container is lifecycle managed with the user account and is deleted when the user account is deleted from the organization.

• You can't permanently reassign content to a new owner.
• The container follows the same cleanup schedule as OneDrive: 30 days active, then soft deleted, and permanently purged 93 days after soft deletion.
• Admins can recover the entire container (including all Copilot Pages and Copilot Notebooks) during the soft delete period using the SharePoint Admin Center or PowerShell.

36. Can retention policies be applied to Copilot Pages?
    Answer: Yes.
    SharePoint Embedded containers respect SharePoint retention policies set by IT administrators. For more information please read: Purview management for SharePoint Embedded containers | Microsoft Learn

 

Join us next month on February 24th for our next community call.

• Haven't joined the program yet? It's free! Join here: https://aka.ms/M365Champion.
• Bring your questions to our discussion forum: https://aka.ms/DriveAdoption.

If you’ve ever wished Copilot could remember the context of a project, understand the documents your team already relies on, or answer repeat questions without retracing your steps, Agents in OneDrive were built for you.

Rather than asking Copilot the same questions across individual files, you can now create an Agent that understands an entire set of documents, project plans, specs, meeting notes, research, or decks, and responds with answers grounded in your content.

What is an agent in OneDrive?

Think of an agent as a focused AI teammate built from your own files and folders. You choose the content, and the agent uses it to:

• Answer questions across multiple documents at once
• Summarize discussions, decisions, and key takeaways
• Surface owners, deadlines, risks, and action items
• Keep shared context intact as work evolves

Agents are saved directly in OneDrive as .agent files, just like a document or spreadsheet. Open one, and you’re dropped into a full-screen Copilot experience that stays centered on that specific project or topic.

See Agents in Action

The capabilities highlighted here are demonstrated in a video walkthrough featuring Mithuna Soundararaj, Akash Ravi, and Vesa Juvonen.

Creating an Agent in OneDrive

Getting started is simple and requires no special admin setup.

You’ll need OneDrive on the web and a Microsoft 365 Copilot license. From there, you can:

1. Select + Create or upload and choose Create an agent
2. Or select files and choose Create an agent from the toolbar or right‑click menu

Pick up to 20 files, name your agent, add optional instructions, and save. Your Agent immediately appears in OneDrive as a .agent file.

Agents in OneDrive are now generally available worldwide for OneDrive on the web. A Microsoft 365 Copilot license is required.

Where agents shine

Because agents stay tied to the content you select, they’re especially powerful for work that spans people, time, and files.

Project coordination

Get clarity fast without digging through folders:

• “What decisions have we made so far?”
• “What’s still open, and who owns it?”

Onboarding and knowledge transfer

Help teammates ramp up using the content that already exists:

• “Explain how this team operates based on these docs.”
• “Summarize how we ship new features.”

Meeting prep and follow-up

Keep momentum without re-reading notes:

• “What did we agree to in recent reviews?”
• “What risks keep coming up?”

Research and synthesis

Turn collections of material into insights:

• “What themes show up across these reports?”
• “What did we learn from this research?”

Instead of jumping between files, you keep the conversation in one place with context and history preserved per project.

Agents behave like any other file in OneDrive. You can search for them, filter by file type, open them, and update them as work progresses. As projects change, you can add or remove files or refine instructions, so your agent stays aligned with the latest information.

Sharing an agent is just as easy. Share it with teammates like a regular OneDrive file. As long as collaborators have access to the source documents, the agent can provide complete, grounded responses keeping everyone aligned without extra handoffs.

We’re excited to see how Agents in OneDrive fit into your daily work and your feedback directly informs what comes next.

Tell us how you’re using agents

Share your thoughts through your usual Microsoft feedback channels or in the comments.

• What types of work are you using Agents for?
• What insights surprised you?
• What would make Agents even more valuable?

If you’d like to dive deeper or share guidance with your teams, explore these resources:

• Get started with OneDrive agents
• Create and use an agent in OneDrive
• Find your agent files in OneDrive
• Share an agent in OneDrive

We’re excited for agents in OneDrive to become a natural part of how you organize information, stay aligned, and move work forward.

When I joined the Dash DevRel team, my manager gave me an onboarding doc which started like this: “Your new job in one sentence: Improve the lives of Dart and Flutter developers.”

In time, I’ve come to understand the definition of ‘Dart and Flutter developers’ to include those who don’t yet even call themselves Dart and Flutter developers; they’re just Flutter-curious.

Today, we’ve landed something that we think improves the lives of those future Flutter developers: the Dart and Flutter Getting Started experience.

What we built

The Getting Started experience is a multi-disciplinary learning pathway for programmers who don’t yet know anything about Dart or Flutter. It spans both the Dart and Flutter websites, and combines written tutorials, video series, quizzes, and documentation to take you from setting up Flutter to building a handful of apps designed to teach the fundamentals.

A quick install guide for those who just want to try Flutter out.

Since the release of hot reload on the web, Flutter learners can have the full Flutter experience without having to download platform-specific development environments until they need them. We wrote a new quick install guide to reduce the friction of trying Flutter. We don’t want it to feel like a commitment before you even start!

Two full tutorials: one for Dart, one for Flutter.

The Dart tutorial was designed to lead into the Flutter tutorial, but they aren’t dependent on one another. If you’re already confident using a different modern, object-oriented language, you’re free to jump straight into the Flutter tutorial.

Four apps that you’ll build from scratch.

Of all the design questions we asked ourselves, we spent the most time thinking about what the reader will actually build. Will it be one giant app, several discreet cookbook recipe-like pieces of Flutter code, or something in between?

Ultimately, we came to the conclusion that smaller apps provide a better experience for new learners for a few reasons:

• With larger apps, there’s more room for things to go wrong, which can cause a new learner to become frustrated.
• The larger the app, there’s more required code that isn’t actually pertinent to what the tutorial is trying to teach.
• We didn’t want to ask the user to clone a repository with 25 projects with names like flutter_tutorial_step_1. Then you have to bring git and terminal commands into the picture, you have to ask the reader to copy the commands that work their operating system, and so on. It’s just a bunch of unnecessary cruft that gets in the way of learning.

At the same time, the apps need to be more than single-feature apps, else we’ll fail to connect the dots of a feature to the bigger picture.

Eight videos accompanying major topics.

The videos in the Getting Started experience were written to provide the most crucial context, so the reader would understand what they were doing when they got to the hands-on-coding part.

Including these videos is important to me on a personal level too. Many years ago when I was learning Flutter, I felt in awe of the early DevRel team. They cared deeply about teaching Flutter, and they were so genuine and supportive that I wanted to be part of whatever it was they were doing. Since this learning pathway is often going to be the first thing a new Flutter developer interacts with, I wanted to honor that feeling and make Flutter-curious developers feel excited and welcomed to join the community.

To that end, we use the videos as a way to teach Flutter, but also to introduce a handful of the real-life humans that work to make the Flutter and Dart better everyday — engineers, tech writers, and product managers are all featured.

Small quizzes throughout to confirm what you’ve learned.

We added simple quizzes at the end of each tutorial page. They’re low-stakes and non-blocking. They exist only to give you a bit of feedback and confidence. If you don’t like ’em, skip ‘em!

The existing How Flutter Works YouTube series as a conclusion.

We cap the learning tutorial off with Craig Labenz’s fantastic video series, released a few months ago, called ‘How Flutter Works’. This series teaches you the inner workings of Flutter with just enough depth that it’s still approachable, yet upgrades your ability to write Flutter apps. This is must-learn knowledge on the way to becoming an advanced Flutter developer.

Website updates

This tutorial is shipping alongside several updates to the Dart and Flutter websites. You may know that we’ve been migrating our website infrastructure from JavaScript-based static site generators (SSGs) to Jaspr, a Dart SSG. The timing of that migration isn’t random! We knew we wanted to do it, and it seemed like the right thing to do before we started work on the considerable updates to the website we made for the Getting Started tutorials.

As a reader, the most noticeable update is the separation of the main docs articles and the Learn section of the website. The learn section of the site is reached by clicking on the Learn button in the site’s header navigation, as seen in this screenshot:

The Learn section is where we’ll organize all existing and future tutorial-style documentation and articles, in order to keep the main docs easier to navigate. In the header navigation the main docs can be reached with the “User Guides” button (or by clicking the site title).

Try it out

The learning pathway is live at docs.flutter.dev/learn/pathway. If you go through it — or even just part of it — please fill out the feedback survey linked on that page. We’re listening, and we’re already thinking about what comes next.

---

Announcing our new Dart and Flutter Getting Started experience was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

Starting April 28, 2026, apps and games uploaded to App Store Connect need to meet the following minimum requirements:

• iOS and iPadOS apps must be built with the iOS 26 & iPadOS 26 SDK or later
• tvOS apps must be built with the tvOS 26 SDK or later
• visionOS apps must be built with the visionOS 26 SDK or later
• watchOS apps must be built with the watchOS 26 SDK or later

Learn more about submitting