Dismissible for swipe actions in Flutter - Build, Publish & Deploy

Build & Publish - Dismissible for swipe actions

Performance Impact

Using Dismissible widgets for swipe actions can affect your app's frame rate if you have many items in a list. Each swipe gesture triggers animations and state changes, which require CPU and GPU work. On mid-range devices, smooth 60fps is achievable if you keep the list size reasonable and avoid heavy rebuilds during swipe. Memory usage is generally low, but excessive use of complex child widgets inside Dismissible can increase memory and battery drain.

Optimization Tips

• Use lightweight child widgets inside Dismissible to reduce rendering cost.
• Limit the number of Dismissible widgets visible on screen by using lazy loading with ListView.builder.
• Cache data and avoid rebuilding the entire list on each swipe.
• Use key properties properly to help Flutter efficiently identify widgets.
• Keep swipe animations simple and avoid complex custom animations.

App Size and Startup Time

The Dismissible widget is part of Flutter's core framework, so it does not add extra size to your app bundle. However, if you add many custom swipe actions or animations, those can increase your app size slightly. Startup time is not affected by using Dismissible unless you preload large data sets or images for the list items.

iOS vs Android Differences

On both iOS and Android, Dismissible provides consistent swipe-to-dismiss behavior. However, platform conventions differ:

• iOS: Swipe actions often reveal buttons like "Delete" or "Archive". The swipe gesture is usually from right to left.
• Android: Swipe to dismiss is common, but Material Design encourages using snackbars for undo actions after dismissal.

Flutter's Dismissible widget works the same on both platforms, but you should adapt UI feedback and undo options to platform guidelines.

Store Review Guidelines

• Apple App Store: Ensure swipe actions do not cause accidental data loss. Provide undo options or confirmation dialogs if dismissing important content.
• Google Play Store: Follow Material Design guidelines for swipe gestures and feedback. Avoid confusing or inconsistent swipe behaviors.
• Both stores require accessible UI: make sure swipe actions are accessible via keyboard and screen readers.

Self-Check: Slow Screen Load

If your app takes 5 seconds to load a screen with Dismissible widgets, likely issues include:

• Loading too many list items at once without lazy loading.
• Heavy widget trees inside each Dismissible causing slow build times.
• Expensive operations (like network calls or image decoding) happening synchronously during build.
• Improper use of keys causing Flutter to rebuild widgets unnecessarily.

To fix, use ListView.builder for lazy loading, simplify child widgets, and move heavy work outside the build method.

Key Result

Using Flutter's Dismissible widget enables smooth swipe-to-dismiss actions with minimal app size impact. To maintain 60fps, optimize list size and widget complexity. Adapt swipe behavior to platform conventions and ensure accessibility. Avoid loading too many items at once to prevent slow screen loads.

Practice

1. What is the main purpose of the Dismissible widget in Flutter?

easy

A. To display images in a grid layout

B. To create a button that triggers an alert

C. To allow users to swipe and remove items from a list

D. To animate text color changes

Solution

1. Step 1: Understand the widget's function

   The Dismissible widget is designed to let users swipe list items to remove them.

2. Step 2: Compare options with the widget's purpose

   Only To allow users to swipe and remove items from a list describes swiping to remove items, which matches Dismissible's role.

3. Final Answer:

   To allow users to swipe and remove items from a list -> Option C

4. Quick Check:

   Dismissible = swipe to remove [OK]

Hint: Dismissible = swipe to delete list items [OK]

Common Mistakes:

• Confusing Dismissible with buttons or animations
• Thinking it manages image layouts
• Assuming it changes text colors

2. Which of the following is the correct way to assign a unique key to a Dismissible widget?

easy

A. key: Key('item_1')

B. key: UniqueKey()

C. key: ValueKey(1)

D. All of the above

Solution

1. Step 1: Review key types for Dismissible

   Flutter requires a unique key for each Dismissible. Key, UniqueKey(), and ValueKey() are all valid ways to create unique keys.

2. Step 2: Confirm all options are valid

   Each option shows a valid key assignment method, so all are correct.

3. Final Answer:

   All of the above -> Option D

4. Quick Check:

   Any unique key type works [OK]

Hint: Any unique Key subclass works for Dismissible keys [OK]

Common Mistakes:

• Using non-unique keys like constant strings for all items
• Omitting the key parameter
• Using keys that are not unique per item

3. Given this code snippet, what happens when the user swipes the list item?

Dismissible(
  key: Key('item1'),
  onDismissed: (direction) {
    items.removeAt(0);
  },
  child: ListTile(title: Text('Item 1')),
)

medium

A. The first item is removed from the list

B. Nothing happens because the key is wrong

C. The app crashes due to missing setState

D. The item is duplicated instead of removed

Solution

1. Step 1: Understand onDismissed callback

   The onDismissed callback removes the first item from the items list when swiped.

2. Step 2: Analyze the effect of removing item at index 0

   Removing at index 0 deletes the first item, so the list updates accordingly.

3. Final Answer:

   The first item is removed from the list -> Option A

4. Quick Check:

   onDismissed removes item at index 0 [OK]

Hint: onDismissed callback removes the swiped item [OK]

Common Mistakes:

• Assuming key error prevents removal
• Forgetting to update the list state
• Thinking swipe duplicates items

4. What is wrong with this Dismissible usage?

Dismissible(
  key: Key('item'),
  onDismissed: (direction) {
    items.removeAt(index);
  },
  child: ListTile(title: Text('Item')),
)

medium

A. The key is not unique for each item

B. The onDismissed callback is missing

C. The child widget is not a ListTile

D. The index variable is not defined

Solution

1. Step 1: Check the key uniqueness

   The key is Key('item') which is constant and not unique per item, causing issues in lists.

2. Step 2: Verify other parts

   The onDismissed callback exists, child is a ListTile, and index is assumed defined, so no issues there.

3. Final Answer:

   The key is not unique for each item -> Option A

4. Quick Check:

   Keys must be unique per Dismissible [OK]

Hint: Keys must be unique strings or objects per item [OK]

Common Mistakes:

• Using same key for all items
• Ignoring key importance in lists
• Assuming onDismissed is optional

5. You want to show a red background with a trash icon when swiping a Dismissible item to the left. Which code snippet correctly implements this?

hard

A. background: Container(color: Colors.red)

B. background: Container(color: Colors.red, child: Icon(Icons.delete, color: Colors.white))

C. background: Container(color: Colors.white, child: Icon(Icons.delete, color: Colors.red))

D. background: Icon(Icons.delete, color: Colors.red)

Solution

1. Step 1: Understand background property

   The background expects a widget behind the item during swipe, usually a colored container with an icon.

2. Step 2: Check each option's correctness

   The snippet with Container(color: Colors.red, child: Icon(Icons.delete, color: Colors.white)) provides a red background with a visible white trash icon. Others lack a container, the icon, or use colors that do not produce a red background with a visible trash icon.

3. Final Answer:

   background: Container(color: Colors.red, child: Icon(Icons.delete, color: Colors.white)) -> Option B

4. Quick Check:

   Red container + white icon = correct swipe background [OK]

Hint: Use Container with color and Icon for swipe background [OK]

Common Mistakes:

• Using icon alone without container
• Wrong colors making icon invisible
• Missing icon in background