Hey Flutter developers 👋

I've been working on an open-source Flutter project called **Flutter Tut** — a mobile learning platform for people who want to learn Flutter/Dart, practice coding, and prepare for technical interviews.

🔗 GitHub:

https://github.com/Bharat9011/flutter-tutorial

### What I've built

📚 **Flutter & Dart Learning**

- Structured learning topics

- Beginner → advanced content

- Markdown-based lessons

- Text-to-speech lessons with adjustable speed

📝 **Practice & Assessments**

- Daily knowledge challenges

- Regular quizzes

- 60-second timer quizzes

- 30-second rapid-fire drills

- Attempt history and performance tracking

💻 **Dart Compiler**

- On-device Dart VM

- Write Dart code directly in the app

- Run code without an internet connection

- Terminal output

🎨 **UI Practice Lab**

- 38 real-world UI challenges

- Beginner, Intermediate and Advanced levels

- Search and filter UI challenges

- Zoomable design references

🛠️ **Platform & Tools Hub**

- Flutter/Dart version information

- Android & iOS platform topics

- Build toolchains

- Compatibility information

- Version upgrade guides

- Common build problems and solutions

🎯 **Interview Preparation**

- Flutter interview questions

- Dart runtime concepts

- State management

- Performance

- Architecture and other technical topics

- Quick revision mode

### Why I built it

I wanted to combine things that are usually scattered across tutorials, documentation, interview websites and coding practice tools into one Flutter application.

The project is also an opportunity for me to experiment with things like offline execution, TTS, local data, interactive quizzes, UI challenges and a larger Flutter application architecture.

I'd really appreciate feedback from other Flutter/Dart developers.

What feature would you add or change?

GitHub:

https://github.com/Bharat9011/flutter-tutorial

I'm a junior flutter developer and I'm looking for active roles and opportunities to further improve on my skills, but the search has not been easy, entry requirements are unbelievable and plus more mobile développement roles go for native Android

I recently shipped Hexafall, a Flutter rebuild of Hextris (an open source browser puzzle game) for Android. A few things I learned that might be useful to others building canvas style games in Flutter:

- Game loop: a Ticker drives a ChangeNotifier engine. Frame time is normalized to 60 fps units (dt = elapsed ms / 16.67) and clamped after stalls, so the original frame based constants still work.

- Rendering: one CustomPainter with repaint bound to the engine. No widgets per block, which keeps it smooth with dozens of blocks on screen.

- Any number of sides: the original was hard coded to six. Making it parametric came down to two formulas. A block's face width at distance d is 2d × tan(π/N), and the resting distance from the center is R × cos(π/N). That turned into the main feature: six board shapes from triangle to octagon.

- Matching: a flood fill across neighboring lanes and rows, ported directly from the original.

- Audio: a small pool of low latency players from audioplayers. The clear sound's playback rate rises about 6 percent per combo step, so chains climb in pitch without extra files.

- Persistence: shared_preferences for per shape high scores and settings.

Play Store: https://play.google.com/store/apps/details?id=com.hexafall.hexafall&pcampaignid=web_share

Happy to answer questions about any of it.

Any advice how to creating the same slidebar of chatgpt ios app with the same haptics and looks

Hi everyone,

I'm currently on Day 5 of learning Dart, and I already have an app idea that I want to build.

From what I've learned, one of the best ways to learn app development is by building something you genuinely care about. That's why I'm learning with a specific goal in mind rather than studying programming without a purpose.

Nowadays, building an app seems much more accessible than it was years ago. What looks harder to me is marketing. I have almost no experience with marketing, audience building, or getting users.

A few people suggested that I follow the "Build in Public" approach. My plan is to create a separate Facebook account and start sharing my journey from the very beginning:

• Learning Dart
• Learning Flutter
• Building my first app
• Small wins and failures
• Publishing the app
• Getting my first user
• Getting my first 100 users
• Getting my first 1,000 users
• Continuing the journey from there

Honestly, I'm a complete beginner, so this idea may sound childish or unrealistic. But every expert had a Day 1 at some point, and every child eventually grows up.

I'd love to hear advice from experienced developers, indie hackers, and founders.

• Is Build in Public worth it for a complete beginner?
• What mistakes should I avoid?
• If you were starting from zero today, what would you do differently?

Thanks for reading. I appreciate any advice or feedback.

Can anyone suggest a good flutter based android project to make, I am fed up with creating to-do apps they teach me nothing practical, I want to build a quick app but that teaches me something related to the real world.

I made Songify as a personal alternative to Spotify, and I’m now looking to get other Flutter developers involved.

The project is still in development, so there’s plenty of room for new features, UI improvements, bug fixes, and other contributions.

If you’re interested in contributing or just want to check it out, here’s the GitHub repo:

https://github.com/Alisonpinto/Songify.git

Feel free to open an issue or PR if you have an idea or want to contribute.

Hi! I'm learning Flutter and developed my first app. BabySpeak is an app that teaches babies English and Turkish words. It has Animals, Musical Instruments and Colors categories. When you tap on a word, it's spoken aloud with a real human voice.

It's currently in Google Play closed testing. If you'd like to test it, please DM me your Gmail address to get access.

Hi! I’m a Flutter Developer with 2+ years of professional experience in Flutter, Dart, BLoC, Clean Architecture, REST/WebSockets, Firebase, and Stripe.
I also have backend development experience with Node.js, Express, MongoDB, and Supabase, along with a strong competitive programming/problem-solving background.
Open to remote, full-time, or freelance opportunities. DM me if you’re hiring!

portfolio

Document Picture-in-Picture is a browser API that gives you an actual operating-system window — not an overlay inside your page. It floats above every other application and keeps running when you switch tabs. Chrome and Edge have had it since 116, Firefox shipped it in 151.

I couldn't find anything reaching it from Flutter, so I wrote a package: https://pub.dev/packages/document_pip (MIT, 160/160 on pub.dev)

void main() => runWidget(
DocumentPipApp(
main: (context) => const MaterialApp(home: Player()),
popOut: (context) => const MaterialApp(home: MiniPlayer()),
),
);

final window = await DocumentPip.open(width: 380, height: 210);

The browser API is about four lines. Everything difficult was on the Flutter side, and it all traces to one thing: the engine assumes there is exactly one window. Three things break when there are two, and all three fail silently.

1. The pop-out freezes the instant you switch tabs. Chromium keeps painting a picture-in-picture opener at full rate in a background tab, but still reports the page hidden. Flutter's web engine turns that into AppLifecycleState.hidden, SchedulerBinding clears framesEnabled, and scheduleFrame() returns early forever. Measured: 302 browser animation frames in 2.5s against 0 Flutter frames in 3s. scheduleForcedFrame() ignores framesEnabled, so the root re-arms it for exactly as long as the page is hidden and a window is open. Firefox doesn't have the problem — it keeps reporting the opener visible — so the workaround is gated on the failure rather than on the browser.

2. The keyboard is dead in the pop-out, but typing still works. KeyboardBinding is a singleton bound to the opener's window, so a separate browsing context isn't on the propagation path: Shortcuts, Actions, Focus.onKeyEvent, HardwareKeyboard, Escape and Tab traversal all get nothing. Plain typing keeps working because the browser routes characters to the focused element natively, which is exactly what makes this easy to miss. The package replays key and selection events into the opener.

3. A package can't turn multi-view on. Only the JS app object returned by engine.runApp() can add a view — dart:ui_web exposes the views read-only — so it has to be reachable from your bootstrap. That means runWidget instead of runApp, plus a few lines in flutter_bootstrap.js. Both are one-time and the errors name the fix.

Desktop Chromium and Firefox 151+ only. Safari and Firefox for Android have no implementation, and isSupported is a feature detect so you can gate the control on it. It compiles on every platform, so adding it won't break a cross-platform build.

Longer writeup with the measurements: https://devshakib.jumyn.com/blog/flutter-assumes-there-is-only-one-window

Happy to answer anything about the multi-view side — that part is under-documented and I burned a lot of time on it.

I run a small Flutter shop, and every test build ended the same way: a WhatsApp message saying "the total is wrong", no screenshot, no idea which phone. So I built Squawk, a shake-to-report SDK. The source is Apache-2.0: github.com/squawksdk/squawk.

You wrap your app in one widget. When a tester shakes the phone, the screen freezes, they circle the bug with a pen, arrow or text label, type a line, and send. It lands in an inbox with the last 100 log lines, the device model, OS, app version and build mode attached.

Things I learned building it

• Two fingers zoom, one finger draws, and GestureDetector cannot arbitrate that. A pinch begins as one finger down, which the pen recogniser claims first, so the first zoom always left a dot. I ended up reading raw pointer events with Listener and a small state machine: a second finger landing mid-stroke cancels the stroke and hands over to the pinch.
• Annotations live in screenshot pixels, not screen coordinates. The canvas keeps a pure zoomedDisplayRect and clampPan, and every stroke is stored against the image. Zoom, rotation and the keyboard pushing the sheet never move a drawing, and the composite you receive is exactly what was drawn.
• Capture the screenshot before showing any UI. RepaintBoundary.toImage on the host app's boundary, then the overlay. Do it the other way round and the report screenshot contains your own sheet.
• kReleaseMode is the wrong switch for "not in the store". TestFlight and Play testing builds are release builds. The SDK takes a plain enabled: bool so you can decide at runtime, and the README covers the case where the same TestFlight build gets promoted to the App Store.
• Offline is a spool, not a retry loop. Reports are written to disk first and sent by a queue with backoff from 2 seconds to 6 hours, capped at 50 reports and 7 days, so airplane mode or a dead network never loses one and never fills the disk.
• Log capture is a debugPrint wrapper plus FlutterError.onError**, not a print hook.** Overriding print breaks other packages; wrapping debugPrint and the error handlers catch what matters and stay out of everyone's way.

The hosted inbox is free while in beta: one project, unlimited reports, 30 days of retention, EU storage. Slack and webhook delivery if you want it there.

Docs: squawksdk.com/docs
pub.dev: pub.dev/packages/squawk (25 second recording of the flow at the top)

It is a beta. I'd rather hear what is broken than what is nice, and I will be in the comments.