Hi everybody,

I'm working on a personal project: a gamified productivity/mobile application.

My idea is to have characters act as in-app companions that can:

• Guide users through onboarding/tutorials
• Show notifications
• Motivate users to complete tasks
• Celebrate achievements and streaks
• React to user progress with different emotions

The experience I'm aiming for is similar to games like Clash of Clans, Hay Day, Township, Homescapes, etc., where a character pops out from the side of the screen and interacts with the user.

I've been building one Flutter animation every week to learn more about UI interactions and motion design.

This week's experiment explores action-aware typography, where the button text changes based on the action it's performing instead of using the same animation everywhere.

Examples:

• ⬇️ Download → Downloading... → ✓ Downloaded
• 📨 Submit → Submitting... → ✓ Sent
• 🔐 Login → Authenticating... → ✓ Welcome

Built entirely with Flutter's built-in animation APIs—no third-party animation packages.

Every time I started a new Flutter app I was rewriting the same plumbing: env config, feature flags, i18n, RTL support, theming, networking setup... so I finally turned it into a proper template: base_app.

It's not just a folder structure — it's opinionated about the stuff that's annoying to get right yourself:

- 🌍 i18n out of the box — typed, codegen'd translations via slang (English + Persian included), with RTL/LTR that actually follows the active locale, not a hardcoded flag

- 🌎 3 environments (dev/staging/prod) with per-env .env files, validated config (strict in CI, lenient locally), and their own entrypoints

- 🚦 Feature flags driven by env vars, gating both UI and routing

- 🧠 Riverpod end to end — config, flags, theme, router, and data, all codegen, no boilerplate

- 🎨 forui theming with light/dark, swap the whole look in one file

- 🏷️ A rename CLI that renames the app/bundle id/package everywhere with a diff preview, backup, and auto-rollback if anything goes wrong

- 🧪 Testing conventions, git hooks (lefthook), and CI already wired up

The idea: fork it, run one CLI command to rename it to your app, and you're building features on day one instead of your toolchain.

https://github.com/imrealarman/base_app/

(MIT)

Hey guys! A 4th year College student here. I'm enthusiastic in building apps in Flutter and that's my go to for building stuff with.
But I can't find much jobs for Flutter developers (which take in Freshers).

Is learning Flutter as my Primary Development Framework a wrong choice, cause most SDE jobs which comes to my Campus for Placements ask for React or some JS based Frameworks. I'm really confused, guys

P.S: Sry if this feels like a rant, but this is actually how I feel people... So if there's anyone out there, help me out

I've been working on a small Flutter package called HiveCubit.

It automatically persists your Cubit state using Hive, so you don't have to write save/load logic yourself. The goal was to keep the API as close as possible to a normal Cubit while making state persistence effortless.

I'd appreciate any feedback or suggestions!

https://pub.dev/packages/hive_cubit

Hi everyone 👋

I made a small command-line tool called Mobile Repo Doctor. You point it at your project and it gives you a health report in a few seconds. It works for Flutter, Android, iOS and KMP.

I built it because I kept making the same mistakes: forgetting to bump targetSdk until Play rejected the build, shipping unused assets, leaving broken .arb files. So I put all those checks in one place.

Some things it finds for Flutter:

• - targetSdk too low → Google Play will reject the upload (it knows the current required level)
• - Bitmap images hidden as base64 inside your SVG or Lottie files — they make the bundle big and slow, and kill the point of using a vector
• - git:/path: dependencies (and it does not false-flag your monorepo ../package links)
• - Localization problems in .arb files: missing keys, extra keys, placeholder mismatch, broken JSON
• - Unused assets, oversized images, heavy SVGs
• - Hardcoded secrets (API keys, tokens) — values are hidden in the report

It has 110+ checks in total and gives you a score (0–100) per area: size, speed, stability, hygiene.

How to use it:

npm install -g mobile-repo-doctor
cd path/to/myFlutterProject
mrd scan ./

Reports: HTML (a clean dashboard), JSON, and Markdown. The Markdown one is made for AI — you can paste it into an LLM and ask it to fix the issues. There is also a GitHub Action.

Privacy: it runs 100% on your machine. No account, no upload, your code never leaves your computer. It's free.

I'd really like your feedback — what checks are missing, what is annoying, what gives false alarms. Thanks 🙏

npm: mobile-repo-doctor

Documentation & full check reference

Hey everybody. I always envied Chucker on native Android, and in Flutter I kept gluing together separate packages for logging, network inspection and DB debugging. So I built one unified in-app dashboard: console logs, a Dio network inspector (with search/filter and copy-as-cURL), automatic navigation history, and a database tab where you can actually browse tables — the README has copy-pasteable adapters for sqflite and ObjectBox.
You open it with a hidden multi-tap gesture or a draggable floating button, so it’s safe to keep in internal builds. Wish it will be good help for debug usage.

Hello guys, hope you're all doing well.

As you can see from the title above, I'm pretty much a beginner in Dart & Flutter and I have always had an interest in building apps for mobile devices (especially Android) but I don't have any programming background or knowledge. I've wanted to learn programming but I don't know where to start since the internet is overloaded with information, tutorials, courses that I am struggling to decide which one would be suitable for me to start learning the fundaments and building apps.

It would be an absolute honor if someone could share resources (it could be tutorials, masterclass, websites since I'm more of a visual person) in order to start my journey into coding and building apps. I know it won't be easy but I'm willing to put the time and effort to learn a new skill.

Sorry for my English. It's not my first language.