NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
Reorderable list and grid: drag and drop an item to reorder a ListView or GridView, or to move it between multiple lists, swipe to delete, and animate each insert, remove and move.
Latest stable
2.10.1
Last release 1 months ago
22 Oct 2026
Ships unpredictably
gaps range from 2 weeks to 2.0 years
Nearly every release is documented
notes for 30 of 31 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
32 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
2.10.1: end a drag or a swipe the system cancels
2.10.1: end a drag or a swipe the system cancels
onEnd wasn't called; and a list the item was held at the edge of went on scrolling to its end.
ItemDragCallbacks.onEnd is called for both, with no velocity.Keep an item that flies from one list's look to another's opaque all the way. The default shuttle faded the old look out and the new one in together,
FlightOptions.shuttleBuilder gets from and to at their own sizes, rather than stretched to the shuttle. Each holds the point the pointer holds and is cut at the shuttle's edges, and to lays out at the shuttle's size while the shuttle is bigger than it.Your coding agent can read these notes before it upgrades. Set up the MCP server →
License the package under the Apache License 2.0. Versions up to 2.9.0 stay under the MIT License.
AnimatedReorderable and its state, AnimatedReorderableGroup, ReorderOptions, SwipeToRemoveOptions, ItemMoves, ItemMove and the typedefs each say first what they do. The library page also compares the package with Flutter's ReorderableListView, AnimatedList and AnimatedGrid.These still work, and go in 3.0:
These still work, and go in 3.0:
Permutation, Permutations and PermutationsCallback. Use ItemMove, ItemMoves and ItemMovesCallback, the same types under new names: onReorder gets the moves of the items a reorder takes to new indexes, as in onReorder: (moves) => moves.apply(items). An ItemMove prints itself as one.Permutations.addPermutation. Use ItemMoves.addMove.Paint an item's ink with the item, such as a ListTile's tile color or an InkWell's splash. Ink paints on the closest Material above it, which was the
ListTile's tile color or an InkWell's splash. Ink paints on the closest Material above it, which was the app's, under the list, and that Material doesn't paint again as items move on layers of their own. So as items moved to their new places after a removal, an insert or a swipe, or out of a dragged item's way, their text slid and their tile colors stayed behind, then jumped to their places as the moves ended. A held item's tint didn't fade or grow with its decoration either. Each item now has a transparent Material of its own, which paints its ink on the item's layer and passes on the text style the item inherits. This broke in 2.1.0. As in a Card, an item's splash or highlight now paints the item again rather than the app's Material, and ends at the item's edges. A transition that the app puts around its item, as the builder given to removeItem may, still doesn't fade the item's ink, as in an AnimatedList. A Material inside the transition, such as a Card's, does.ListTiles, with less work a frame. The app's Material painted every item's ink again on each frame of a scroll, while each item now paints its own once, on its layer. On an iPhone 17 Pro, a frame that scrolls ListTiles by 24 px takes 0.46–0.47 ms on the UI thread instead of 0.65–0.69 at the median, and 1.46 ms instead of 1.69–1.75 at the 90th percentile.Material of its own as it comes into sight. On an iPhone 17 Pro, the savings above outweigh it: a frame that builds 15 new ListTiles at once takes 6.7–6.8 ms instead of 7.1–7.3 at the median. Reorders in a list, and removals in a list and in a 12-column grid, take as long as before. On macOS, the slowest tenth of the frames that build 15 tiles took about 4 ms longer, as garbage collection ran during them.ReorderableListView, AnimatedList and AnimatedGrid, and with other packages, and answers to common questions. A Performance section gives the package's measurements against Flutter's lists on an iPhone 17 Pro.ReorderableListView sample of cards, animated: a long press drags a card, a swipe deletes it, and + inserts one.lib/kanban/. Both have hero_here's look, kept apart in lib/style/.2.8.1: docs on keeping heavy items from building again
2.8.1: docs on keeping heavy items from building again
removeItem returns the item builder's widget types, such as the same transition around the cached widget. The AnimatedReorderable docs say it too.Spring a dragged or swiped item back to its place smoothly. The default spring pulled hardest as the item was let go, whatever its speed: in the packa
SpringDescription.withDurationAndBounce makes for 250 ms with no bounce. The item speeds up over the first frames and lands within half a pixel after 352 ms. To keep the old spring, pass springDescription: SpringDescription(mass: 1, stiffness: 2000, damping: 150) to ReorderOptions and SwipeToRemoveOptions.Fly an item swiped away off as it is, with its state. removeItem built it with its builder as it flew off: the sample's builder faded it on its way ou
removeItem built it with its builder as it flew off: the sample's builder faded it on its way out, and a builder whose widgets weren't the item builder's built it anew. The swipe's throw is now all of its going, and the release builds it no more: in the package's measurements, a swipe's release builds only the items it moves, and with widgets cached by id only the item that comes into sight. The builder still builds the items removed otherwise.AnimatedList's does.2.6.1: swiped items fly off at the finger's speed, plus swipe z-order, nesting and keep-alive fixes
2.6.1: swiped items fly off at the finger's speed, plus swipe z-order, nesting and keep-alive fixes
SwipeToRemoveOptions.springDescription now sets only the spring that takes an item back to its place when a swipe doesn't remove it.groupId, such as a list that reorders a board's columns. With moveToListLabel set, each item's build threw a null check error as it listed the moves to the group's lists. This broke in 2.6.0.Column in a SingleChildScrollView. Lifting or removing an item threw "A Stack requires bounded constraints".AutomaticKeepAliveClientMixin, are out of sight, and remove such an item. Either threw errors in debug builds, because the package moved items that the list doesn't lay out. isItemRendered is now false for an item kept alive out of sight, as its docs say.removeItem returns widgets of the same types as the item builder.SwipeToRemoveOptions.springDescription takes back only an item that a swipe doesn't remove.Put a shrink-wrapped list or grid at the start of its space, rather than in the middle. In the middle, it moved at once, with its items, as it grew or
ValueKey hashes its runtimeType with its value, and a generic class's runtimeType, such as ValueKey<int>'s, is slow to get in release builds: in a drag across a 12-column grid, it took a third of each rebuild. The package now hashes value keys by their values. On an iPhone 17 Pro, the slowest frame of that drag builds in 5.2 ms rather than 6.9.ReorderableList's order, then the moves to the group's other lists, in the order of the board. The platform lists an item's actions in the order Flutter first numbered their labels anywhere in the app, so the order depended on which items were built first: on the example's board, "Move to Done" came before "Move to In progress".ReorderOptions.gestureRecognizerFactory, which didn't compile: a DelayedMultiDragGestureRecognizer takes its delay as it's created, and comes from package:flutter/gestures.dart.onSwipeToRemove does: it removes the item from the app's data, and from the list with removeItem, as an AnimatedList's items are removed. The docs said only to remove the item, and an item removed from the data alone stayed in the list.Card in an item from taking a touch without them. The first example of the README, of the API docs and of the example app builds ListTile items rather than cards, so a touch finds their moves.Set the spring a dragged item flies back to its place with: ReorderOptions.springDescription, as swipes have SwipeToRemoveOptions.springDescription. 2
ReorderOptions.springDescription, as swipes have SwipeToRemoveOptions.springDescription. 2.4.0's faster default spring had no option for drags. SpringDescription(mass: 1, stiffness: 500, damping: 75) restores the old one.AnimatedReorderableGroup.moveToListLabel, which names the move to each list in the app's language, such as "Move to Done". Each item that can be dragged and reordered can then move to each other list that the group's canMove lets it go to, in the order of the tree. It goes to the same index there, or to the end of a shorter list, and flies there through the group's layer, to the new list's look, as a drag that lets it go there does. onMove moves its data. Without the labels, screen readers move items only within their lists.AnimatedReorderable, as the README does.Signing.xcconfig, which git ignores, and the example's README says how.Animate faster by default, at the pace of Flutter's own lists. Items move to their new places in 250 ms rather than 500, as a ReorderableListView's do
ReorderableListView's do, and a held item's decoration comes and goes as fast. Inserted and removed items enter and leave in 300 ms rather than 500, as an AnimatedList's do. The spring that flings an item back to its place, or out of the list, is four times as stiff and twice as damped, so it gets there in half the time with the same feel. To keep the old pace, pass MotionOptions(duration: Duration(milliseconds: 500)), ItemDecoration(duration: Duration(milliseconds: 500)), a duration to insertItem and removeItem, and SwipeToRemoveOptions(springDescription: SpringDescription(mass: 1, stiffness: 500, damping: 75)). An item let go after a drag has no option for its spring.AnimatedReorderableGroup and give each a ReorderOptions.groupId. An item dragged over another of the lists goes into it, as the group's onMove(from, to) moves its data, and the items of both lists move in place out of its way and into its old place. Let go, it lands there, with its state kept and the size of the new list's slots. canMove can refuse a move before any data changes. The drag callbacks come from the list the item is in at the time, and an item dragged over no list stays in the last one it was over.AnimatedReorderableGroup.flight sets the duration, the curve and the shuttle builder, which has hero_here's shape, and FlightOptions.none turns flights off. An item let go mid-flight lands once it has flown.animated_reorderable 2.3.0
animated_reorderable 2.3.0
ReorderableList does: each item that can be dragged and reordered gets the actions Move to the start, Move up, Move down and Move to the end. They take their names from the app's WidgetsLocalizations, and sit on a semantics node of each item's own, under its index, as in ReorderableList. A move goes as reorderItem does, in place, and calls onReorder. It takes the item past items that can't be reordered. Each move is named after the way it goes on screen: Move left and Move right in a horizontal list and along a grid's row, and in a reversed list Move up goes up the screen, where ReorderableList's would go down.animated_reorderable 2.2.1
animated_reorderable 2.2.1
example/example.md, in the package, so pub.dev shows it on the package's Example tab and counts it. .pubignore left out the whole example folder, so pub.dev found no example, which cost 10 of the 160 points.animated_reorderable 2.2.0
animated_reorderable 2.2.0
animated_reorderable 2.1.0
animated_reorderable 2.1.0
setState, which builds every item again.animated_reorderable 2.0.1
animated_reorderable 2.0.1
Material, MediaQuery, theme or inherited widgets. So items such as a ListTile or a CircleAvatar threw, and an item that the theme sizes slid in at the wrong size. Now the overlay lays the item out at its own size. Until it does, the package takes the item to be as big as one the list built, so an item bigger than the others starts its way in that much closer.animated_reorderable 2.0.0
animated_reorderable 2.0.0
2.0 removes what 1.6.0 deprecated. Upgrade to 1.6.0 first and fix its deprecation warnings. Three changes are left after that: drop the null from insertItem(index, null), rename ReorderCallback to PermutationsCallback, and drop the type argument from AnimatedReorderableState<…>.
AnimatedReorderable.list and .grid take only keyGetter, motion, reorder, swipeToRemove, insertTransition and the view. Each flat parameter moved to an option object:
| 1.x | 2.0 |
|---|---|
motionAnimationDuration, motionAnimationCurve |
motion: MotionOptions(duration:, curve:) |
onReorder, draggableGetter, reorderableGetter, autoScrollerVelocityScalar, reorderGestureRecognizerFactory |
reorder: ReorderOptions(onReorder:, draggableGetter:, reorderableGetter:, autoScrollerVelocityScalar:, gestureRecognizerFactory:) |
draggedItemDecorator, draggedItemDecorationAnimationDuration |
reorder: ReorderOptions(decoration: ItemDecoration(decorator:, duration:)) |
onItemDragStart, onItemDragUpdate, onItemDragEnd |
reorder: ReorderOptions(callbacks: ItemDragCallbacks(onStart:, onUpdate:, onEnd:)) |
onSwipeToRemove, swipeToRemoveDirectionGetter, swipeToRemoveExtent, swipeToRemoveVelocity, swipeToRemoveSpringDescription |
swipeToRemove: SwipeToRemoveOptions(onSwipeToRemove:, directionGetter:, extent:, velocity:, springDescription:) |
swipedItemDecorator, swipedItemDecorationAnimationDuration |
swipeToRemove: SwipeToRemoveOptions(decoration: ItemDecoration(decorator:, duration:)) |
onItemSwipeStart, onItemSwipeUpdate, onItemSwipeEnd |
swipeToRemove: SwipeToRemoveOptions(callbacks: ItemDragCallbacks(onStart:, onUpdate:, onEnd:)) |
The getters of the same names on AnimatedReorderable are gone. Read the options instead, such as widget.reorder.onReorder.
insertItem(index, builder) is insertItem(index). Move the builder's transition to insertTransition, which gets the item as its child:
// 1.x
state.insertItem(index, (context, index, animation) =>
FadeTransition(opacity: animation, child: buildItem(index)));
// 2.0
AnimatedReorderable.list(
insertTransition: (child, index, animation) =>
FadeTransition(opacity: animation, child: child),
// …
);
state.insertItem(index);
The AnimatedReorderable constructor and AnimatedReorderableState.buildCollectionView are gone. Use AnimatedReorderable.list and .grid.
AnimatedReorderable and AnimatedReorderableState are final classes, and AnimatedReorderableState<T> is AnimatedReorderableState.
ReorderCallback is PermutationsCallback, so that it no longer clashes with Flutter's ReorderCallback.
MotionOptions.duration along MotionOptions.curve, so an item comes to rest one duration after its place last moved, as before. An item flung back to its place after a drag or a swipe still starts over when its place moves.animated_reorderable 2.0.0-dev.1
animated_reorderable 2.0.0-dev.1
animated_reorderable 1.6.1
animated_reorderable 1.6.1
The deprecated AnimatedReorderable constructor is no longer const.
AnimatedReorderable.list and .grid with option objects: motion: MotionOptions(…), reorder: ReorderOptions(…) and swipeToRemove: SwipeToRemoveOptions(…). ItemDecoration and ItemDragCallbacks group a held item's decoration and its callbacks.insertTransition, the way AnimatedList gives its item builder an animation. Insert with insertItem(index, null). Every item is built through the transition, so an item keeps its state when it has entered. An item inserted with a builder that wraps it, such as a FadeTransition, lost its state at the first rebuild after it entered.swipeToRemoveSpringDescription, which had no effect.PrimaryScrollController like a plain list or grid. Tapping the iOS status bar scrolls a wrapped list to the top again, and wrapping a view with primary: true no longer throws.destIndex in reorderItem. A reorder past the end corrupted the list's state.TypeError.RangeError.StateError, ArgumentError, RangeError and UnsupportedError instead of strings.These still work, and go in 2.0:
AnimatedReorderable.list and .grid, such as onReorder and onSwipeToRemove, and the getters of the same names. Use the option objects.AnimatedReorderable constructor and AnimatedReorderableState.buildCollectionView. Use AnimatedReorderable.list and .grid.builder of insertItem. Use insertTransition and insertItem(index, null).Permutation compares by value.AnimatedReorderable constructor is no longer const.animated_reorderable 1.5.0
animated_reorderable 1.5.0
Scrollable.of and PrimaryScrollController don't find the list's scroll view during those 500 ms.findChildIndexCallback, the list now finds items by key.keyGetter, item builder, callbacks and scroll controller after a rebuild, instead of the ones from the first build.scrollCacheExtent, itemExtentBuilder and hitTestBehavior to the wrapped list or grid.Fix typo in reorderGestureRecognizerFactory name.
reorderGestureRecognizerFactory name.Updated part of directives to use string-based file paths instead of library names for improved compatibility and compliance with current Dart best pr
part of directives to use string-based file paths instead of library names for improved compatibility and compliance with current Dart best practices.Added getRenderedItemBuildContext method to retrieve the BuildContext of a rendered item.
getRenderedItemBuildContext method to retrieve the BuildContext of a rendered item.Clarified index updates during item reordering in drag callbacks and specified that in ItemDragEndCallback, the index indicates where the item was dro
Enabled disabling swipeToRemove for specific items.
Made the Permutation class public and Permutations iterable.
Added method to check if an item is rendered in the viewport or cache extent.
Write API documentation
Write API documentation
- Initial stable release.
Nothing published for this version
One column per quarter.