MediaQuery for responsiveness in Flutter - Build, Publish & Deploy

Build & Publish - MediaQuery for responsiveness

Performance Impact

Using MediaQuery to get screen size and orientation is very fast and has minimal impact on frame rate and memory. It reads device metrics from the system, which is lightweight. However, excessive rebuilds triggered by MediaQuery changes (like orientation changes) can cause jank if not managed well.

Overall, MediaQuery itself does not drain battery or memory significantly, but inefficient use in widget rebuilds can affect smooth 60fps rendering.

Optimization Tips

• Cache MediaQuery values in variables instead of calling it multiple times in the build method.
• Use LayoutBuilder or OrientationBuilder alongside MediaQuery to rebuild only parts of the UI that need to change.
• Minimize widget rebuilds by separating responsive widgets from static widgets.
• Use const widgets where possible to reduce rebuild cost.

App Size and Startup Time

MediaQuery is part of Flutter's core framework and does not add any extra size to your app bundle. It does not affect startup time noticeably.

Responsive design using MediaQuery helps avoid multiple layout assets, which can reduce overall app size compared to shipping many fixed-size images or layouts.

iOS vs Android Differences

MediaQuery works the same on both iOS and Android as it reads device metrics from Flutter's engine.

However, device screen sizes and aspect ratios vary more on Android, so responsiveness is more critical there.

On iOS, safe areas (like notches) are important; MediaQuery provides padding and viewPadding and viewInsets to handle these.

Store Review Guidelines

• Apple App Store: Ensure your app adapts well to all screen sizes and orientations to meet Apple's Human Interface Guidelines.
• Google Play Store: Responsive UI improves user experience across devices, which aligns with Google's quality criteria.
• Both stores require apps to handle orientation changes gracefully without crashes or layout breakage.
• Accessibility: Use MediaQuery to adjust font sizes and layouts for better accessibility compliance.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

• You might be rebuilding the entire widget tree on every MediaQuery change instead of only the responsive parts.
• Heavy computations or network calls triggered during build instead of asynchronously.
• Not caching MediaQuery values, causing redundant layout calculations.

Key Result

Using MediaQuery for responsiveness is lightweight and essential for adapting UI to different screen sizes and orientations. Optimize by minimizing rebuilds and caching values to maintain smooth 60fps performance and comply with app store guidelines.

Practice

1. What does MediaQuery.of(context).size provide in a Flutter app?

easy

A. The list of installed fonts

B. The current theme colors

C. The width and height of the device screen

D. The app's current state

Solution

1. Step 1: Understand MediaQuery size property

   MediaQuery.of(context).size returns the screen's width and height as a Size object.

2. Step 2: Differentiate from other properties

   Theme colors, fonts, and app state are unrelated to MediaQuery size.

3. Final Answer:

   The width and height of the device screen -> Option C

4. Quick Check:

   MediaQuery size = screen dimensions [OK]

Hint: MediaQuery size always means screen width and height [OK]

Common Mistakes:

• Confusing size with theme or app state
• Thinking it returns orientation
• Assuming it gives device model info

2. Which of the following is the correct syntax to get the device orientation using MediaQuery?

easy

A. MediaQuery.orientation(context)

B. MediaQuery.of(context).orientation

C. MediaQuery.getOrientation(context)

D. MediaQuery.context.orientation

Solution

1. Step 1: Recall correct MediaQuery syntax

   The correct way is MediaQuery.of(context).orientation to access orientation.

2. Step 2: Eliminate incorrect options

   Other options use invalid method names or wrong property access.

3. Final Answer:

   MediaQuery.of(context).orientation -> Option B

4. Quick Check:

   Use .of(context) to access MediaQuery properties [OK]

Hint: Always use MediaQuery.of(context) to access properties [OK]

Common Mistakes:

• Omitting .of(context)
• Using wrong method names
• Accessing properties directly on MediaQuery

3. Given this Flutter code snippet:

final size = MediaQuery.of(context).size;
final width = size.width;
final height = size.height;

print('Width: $width, Height: $height');

What will this print if the device screen is 360 pixels wide and 640 pixels tall?

medium

A. Width: 360, Height: 640

B. Width: 0, Height: 0

C. Width: 640, Height: 360

D. Width: null, Height: null

Solution

1. Step 1: Understand MediaQuery size values

   MediaQuery.of(context).size.width gives screen width (360), height gives screen height (640).

2. Step 2: Match printed output

   The print statement outputs width first then height, so it prints "Width: 360, Height: 640".

3. Final Answer:

   Width: 360, Height: 640 -> Option A

4. Quick Check:

   Width = 360, Height = 640 [OK]

Hint: Width is first, height is second in MediaQuery size [OK]

Common Mistakes:

• Swapping width and height values
• Assuming zero or null values
• Confusing print output format

4. This Flutter code tries to get screen width but causes an error:

double width = MediaQuery.size.width;

What is the main problem?

medium

A. MediaQuery.size.width should be MediaQuery.width.size

B. Width should be an int, not double

C. MediaQuery.size needs a BuildContext parameter

D. MediaQuery.size is not a valid property; .of(context) is missing

Solution

1. Step 1: Check MediaQuery usage

   MediaQuery properties require calling .of(context) to access size.

2. Step 2: Identify missing .of(context)

   The code misses .of(context), so MediaQuery.size is invalid.

3. Final Answer:

   MediaQuery.size is not a valid property; .of(context) is missing -> Option D

4. Quick Check:

   Always use MediaQuery.of(context) [OK]

Hint: Always call MediaQuery.of(context) before properties [OK]

Common Mistakes:

• Forgetting .of(context)
• Confusing property order
• Wrong data type assumptions

5. You want to build a widget that shows a different layout depending on device orientation. Which Flutter code snippet correctly uses MediaQuery to check orientation?

hard

A. if (MediaQuery.of(context).orientation == Orientation.portrait) { return PortraitWidget(); } else { return LandscapeWidget(); }

B. if (MediaQuery.orientation(context) == 'portrait') { return PortraitWidget(); } else { return LandscapeWidget(); }

C. if (MediaQuery.of(context).size.width > MediaQuery.of(context).size.height) { return PortraitWidget(); } else { return LandscapeWidget(); }

D. if (MediaQuery.of(context).orientation == 'landscape') { return PortraitWidget(); } else { return LandscapeWidget(); }

Solution

1. Step 1: Use correct orientation check

   MediaQuery.of(context).orientation returns an enum Orientation.portrait or Orientation.landscape.

2. Step 2: Verify correct comparison and widget return

   if (MediaQuery.of(context).orientation == Orientation.portrait) { return PortraitWidget(); } else { return LandscapeWidget(); } compares orientation to Orientation.portrait correctly and returns widgets accordingly.

3. Step 3: Eliminate wrong options

   if (MediaQuery.orientation(context) == 'portrait') { return PortraitWidget(); } else { return LandscapeWidget(); } uses wrong syntax, C compares sizes incorrectly, D reverses widget logic.

4. Final Answer:

   if (MediaQuery.of(context).orientation == Orientation.portrait) { return PortraitWidget(); } else { return LandscapeWidget(); } -> Option A

5. Quick Check:

   Compare orientation enum, not strings or sizes [OK]

Hint: Compare orientation to Orientation.portrait or .landscape [OK]

Common Mistakes:

• Comparing orientation to strings
• Using size to guess orientation
• Reversing widget logic