Skip to main content

A month of Flutter: navigate to user registration


Originally published on bendyworks.com.
With users now being able to sign in with Google, I want to have them confirm their name and agree to a terms of service. To lay the groundwork I'm going to add a placeholder RegisterPage and navigation to it.
This will be my second page, of what I expect to be many, so I went ahead and created a pages directory. The existing MyHomePage class was renamed to HomePage and relocated to the pages directory. That's a refactor and ideally should be in its own pull request, but it's of minimal impact so I'm lumping in with today's other changes.
The new RegisterPage is simple and currently just displays some text. On the first implementation I did find that the AppBar title was no not centered.

This is because I was placing the text in a Center widgetCenter was centering the text in the space available to it but the back navigation icon was not being accounted for.
AppBar(
  title: Center(
    child: Text('Register'),
  ),
  elevation: 0.0,
)
A quick switch to using centerTitle fixes it.
AppBar(
  title: Text('Register'),
  centerTitle: true,
  elevation: 0.0,
)

But how do users get to this new registration page? It has to happen after a user is authenticated (how else will I know if they are registered?) but before they perform any other authenticated actions. That only leaves _handleSignIn in SignInFab.
void _handleSignIn(BuildContext context) {
  auth.signInWithGoogle().then((FirebaseUser user) {
    if (_existingUser()) {
      _showSnackBar(context, 'Welcome ${user.displayName}');
    } else {
      _navigateToRegistration(context);
    }
  });
}
For now I've set _existingUser to return a hardcoded boolean. If they are an existing user they should just see the SnackBar, otherwise send them to the RegisterPage.
void _navigateToRegistration(BuildContext context) {
  Navigator.pushNamed(context, RegisterPage.routeName);
}
_navigateToRegistration uses the Navigator widget to push a new route onto the stack by name. In this case I'm defining the routeName in RegisterPage itself so if I want to change it later, I only have to change it in one place.
In MyApp I will now register the route with MaterialApp, also using the routeName from RegisterPage.
MaterialApp(
  // ...
  home: const HomePage(title: 'Birb'),
  routes: <String, WidgetBuilder>{
    RegisterPage.routeName: (BuildContext context) => const RegisterPage(),
  },
);

Code changes

Comments

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.



Advertising!


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:

https://api.twitter.com/1/users/profile_image/abraham

* 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:

https://twitter.com/account/redirect_by_id?id=9436992

In_reply_to_status_id mentions:

https://api.twitter.com/1/statuses/update.json?status=reply+to+@abraham&in_reply_to_status_id=12410413197

* 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:

http://a3.twimg.com/profile_images/54160223/chart-black-small.png

* 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.

Assumptions:
LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz 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…