Skip to main content

A month of Flutter: the real hero animation

Originally published on

For the last post before the month's wrap up tomorrow, I wanted to do something more fun: use a hero animationbetween the home page list and the individual post page.
When I first implemented the Hero animation it never worked going back from a PostPage to the HomePage. The reason was that HomePage would get rerendered and that would generate new fake posts. So I moved the fake data generation up a level to MyApp and pass it into HomePage. This is more realistic as going to the HomePage shouldn't request the Posts every time.
  title: 'Birb',
  posts: _loadPosts(context),
The PostPage implementation is a simple StatelessWidget that takes Post and renders a PostItem. This will become more complex as things like comments and likes are implemented but works for now.
class PostPage extends StatelessWidget {
  const PostPage({
    Key key,
  }) : super(key: key);

  final Post post;

  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Post'),
        centerTitle: true,
        elevation: 0.0,
      body: SingleChildScrollView(
        child: Padding(
          padding: const EdgeInsets.fromLTRB(16.0, 16.0, 16.0, 8.0),
          child: PostItem(post),
With PostItem being used to render on the HomePageand on the PostPage, wrapping the Image in a Hero is handled in a single place. tag is how Hero knows what to transition between pages.
  child: ClipRRect(
    borderRadius: BorderRadius.circular(10.0),
The last piece is navigating from PostList to PostPage when a user taps on a PostItem. I'll handle this with an InkWell widget so there is a nice Material ripple.
  onTap: () => _navigateToPost(context, post),
  child: PostItem(post),
The navigation is more complex then opening the registration page for two reasons. Named routes don't support parameters and I wanted a simple transitionbetween the rest of the content on the page.
void _navigateToPost(BuildContext context, Post post) {
      pageBuilder: (
        BuildContext context,
        Animation<double> animation,
        Animation<double> secondaryAnimation,
      ) {
        return PostPage(post: post);
      transitionsBuilder: (
        BuildContext context,
        Animation<double> animation,
        Animation<double> secondaryAnimation,
        Widget child,
      ) {
        return FadeTransition(
          opacity: animation,
          child: child,
Here I will push a PageRouteBuilder onto the navigation stack. PageRouteBuilder has two key builders in use here. pageBuilder builds the widget that should be rendered as the new page and transitionBuilder specifies how to transition between the old and new pages. Note that this FadeTransition is not related to implementing Heroearlier.
The tests for PostPage is simple and just checking that PostItem is rendered. I did update the PostItem test to expect that its Hero widget had the correct tag value.
PostsList tests had to be wrapped in a MaterialAppas InkWell must have a Material widget ancestor.
The navigation and animation from PostsList to PostPage is now doing more work so I replaced several pump pauses with pumpAndSettle.
Here is the fancy Hero animation:
Code changes


Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

In_reply_to_status_id mentions:

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…