r/FlutterBeginner

I created the most simple app to determine which game my girlfriend and I are gonna play in the evenings. Shipping it to the AppStore I invited my friends to download it and test it out. Most of the feedback was the same.. “where are the games?” .

For me this was quite obvious , that you first have to add the games you own at home to the app in order for it to choose for you.

But as it seems , people are .. dumb? I don’t know, maybe the app needs a proper on boarding or a pre filled list with common games. Maybe something like “welcome, do you own xyz ..”

What do you guys think how I can improve this ?

Hi folks,

Our studio's development has primarily shifted towards Claude Code Desktop + Codex.

To make implemention and testing even more autonomous we've been developing some agentic skills in-house and decided to make them open source.

Skill	Description	Useful for
android-emulator	Allows the agent to run the app on an emulator, navigate it using the semantic widget tree, take screenshots, tap, pan, input two-finger gestures etc.	UI design, bug reproduction, QA
design-polish	Asks the agent to design a screen, and spawns an independent sub-agent to judge that screen. Agent keeps making tweaks until it receives 7+/10 rubric score.	UI design, fixing AI-slop UI
symbolize-android-stacktrace	Given a Google Play Console reported ANR or crash, first downloads Codemagic debug symbols, then symbolizes the strack trace, and finds the root cause.	App maintanence

Install with: npx skills add chunkytofustudios/flutter-skills

Would be glad to hear your thoughts, and receive PRs. What does your agentic engineering stack look like?

Every Flutter project I worked on had this in at least 5 widgets:

dart
final scale = MediaQuery.of(context).size.width / 375;
padding: EdgeInsets.all(16 * scale)
fontSize: (14 * scale).clamp(11, 18)

After seeing it repeat across multiple projects I finally spent time building a proper fix instead of copy-pasting. Spent about a month on it.

It's called layout_flow. The core idea: write UI once, let it adapt to every screen without manual scaling or breakpoint conditionals.

The part I'm most happy with is `FlowRow` — it switches between Row and Column automatically based on screen width:

Before (16 lines):

dart

final isWide = MediaQuery.of(context).size.width >= 480;

if (isWide) {
  return Row(children: [
    Expanded(child: Card()),
    SizedBox(width: gap),
    Expanded(child: Card()),

layout_flow — built this after copy-pasting the same MediaQuery boilerplate across too many projects. feedback welcome.

Every Flutter project I worked on had this in at least 5 widgets:

final scale = MediaQuery.of(context).size.width / 375;
padding: EdgeInsets.all(16 * scale)
fontSize: (14 * scale).clamp(11, 18)

After seeing it repeat across multiple projects I finally spent time building a proper fix instead of copy-pasting. Spent about a month on it.

It's called layout_flow. The core idea: write UI once, let it adapt to every screen without manual scaling or breakpoint conditionals.

The part I'm most happy with is FlowRow — it switches between Row and Column automatically based on screen width:

before

final isWide = MediaQuery
  .of(context).size.width >= 480;

if (isWide) {
  return Row(children: [
    Expanded(child: Card()),
    SizedBox(width: gap),
    Expanded(child: Card()),
  ]);
}
return Column(children: [
  Card(),
  SizedBox(height: gap),
  Card(),
]);

after

FlowRow(
  gap: FlowSpacing.md(context),
  children: [
    Expanded(child: Card()),
    Expanded(child: Card()),
  ],
)

Also ships with design tokens — FlowSpacing, FlowTextStyle, FlowRadius — so there are zero raw numbers anywhere in your UI code.

Zero external dependencies. Uses InheritedWidget + LayoutBuilder internally. Material Design 3 breakpoints.

Genuinely curious what's missing or what would stop you from using this over flutter_screenutil. Happy to take harsh feedback — that's kind of the point of posting here.

pub.dev/packages/layout_flow/

github.com/Aditya-Karmalkar/Layout_Flow