Notice: You're viewing an old version of the Nylo documentation.
Consider upgrading your project to Nylo 5.20.0.



Before starting, let's go over what a controller is for those new.

Here's a quick summary by

The Controller is responsible for controlling the application logic and acts as the coordinator between the View and the Model. The Controller receives an input from the users via the View, then processes the user's data with the help of Model and passes the results back to the View.

Controller with services

class HomeController extends Controller {

  AnalyticsService analyticsService;
  NotificationService notificationService;

  construct(BuildContext context) {
    // example services
    analyticsService = AnalyticsService();
    notificationService = NotificationService();

  bool sendMessage(String message) async {
    bool success = await this.notificationService.sendMessage(message);
    if (success == false) {
      this.analyticsService.sendError("failed to send message");
    return success;

  onTapDocumentation() {


Call the controller from your widget.

class _MyHomePageState extends NyState<MyHomePage> {
  child: Text(
    style: Theme.of(context).textTheme.bodyText1,
  onPressed: widget.controller.onTapDocumentation,

If your widget has a controller, you can use widget.controller to access its properties.

You can use flutter pub run nylo_framework:main make:page account --controller command to create a new page and controller automatically for you.

Creating pages and controllers

You can use the Metro CLI tool to create your pages & controllers automatically.

flutter pub run nylo_framework:main make:page my_cool_page --controller

This will create a new controller in your app/controllers directory and a page in your resources/pages directory.

Or you can create a single controller using the below command.

flutter pub run nylo_framework:main make:controller profile_controller

Retrieving arguments from routes

If you need to pass data from one widget to another, you can send the data using Navigator class or use the routeTo helper.

// User object
User user = new User();
user.firstName = 'Anthony';

Navigator.pushNamed(context, '/profile', arguments: user);
// or
routeTo('/profile', data: user);

When we navigate to that page we can call to get the data.

class _ProfilePageState extends NyState<ProfilePage> {
  void initState() {
    User user =;
    print(user.firstName); // Anthony


The routeTo(String routeName, data: dynamic) data parameter accepts dynamic types so you can cast the object after it’s returned.