6 Reasons Why Felgo Saves Months of Development Time

 import Felgo 3.0
 import QtQuick 2.12

 App {
  NavigationStack {
    initialPage: pageComponent
  }
 
  Component {
    id: pageComponent
    
    Page {
      id: pageItem
      property int count: 0
      title: "Page #"+count
      
      Row {
        AppButton {
          text: "Pop"
          onClicked: navigationStack.pop()
        }
        
        AppButton {
          text: "Push"
          onClicked: navigationStack.push(pageComp, { count: (pageItem.count+1) })
        }
      }
    }
  }
 }

Of course you may place a NavigationStack inside a NavigationItem to implement a mixture of direct and hierarchical navigation.

The Felgo approach is much cleaner than the solution we made ourselves. We tried to handle this all within one multi-purpose component, which led to some rather messy QML code.

Reason 3: Controls and Theming

When populating your pages with GUI controls, make sure you use the enhanced Felgo ones instead of Qt Quick Controls. They automatically respect platform colors and screen-independent sizes defined in the app-wide styling Theme! We had to do this ourselves, because the default QML controls are quite low level. 

The Felgo items also add even more useful features. For example the AppTextField, which is an input control for one line of text. It offers a clear button (a little ‘x’ to clear all input) or the clearsOnBeginEditing property. This customization and flexibility is great in case you need such features. We did.

Apart from such simple controls, there are many advanced features as well, like a SearchBar or a PullToRefreshHandler. Implementing all of those without Felgo cost us quite some precious time.

Reason 4: Access to Native Platform Features

We did want dialogs to look and behave like they do on the respective platforms, so we had to do two different implementations and pass data and signals between the native code, the C++ layer and the QML UI. With the NativeDialog component we could have saved quite a substantial amount of platform specific code.

When talking about native features, you should check out the Felgo NativeUtils as well. You can use it to handle the safe area on iPhone X or to get access to device contacts, pictures or the camera. For even easier access to native dialogs, there are a couple of ready-to-use display-functions as well:

import Felgo 3.0

 App {
  AppButton {
    text: "Open Dialog"
    anchors.centerIn: parent
    onClicked: {
       nativeUtils.displayAlertDialog(qsTr("Title"), qsTr("Description"), qsTr("OK"), qsTr("Cancel"))
    }
  }
}

myStorage.setValue (key, value)

value = myStorage.getValue (key)

 import Felgo 3.0
 import QtQuick 2.5

 App {
  id: app
  // this property holds how often the app was started
  property int numberAppStarts

  Component.onCompleted: {
    // read setting, or start with '0' if 'undefined' is returned
    numberAppStarts = app.settings.getValue("numberAppStarts") || 0 

    // increase value and store setting
    numberAppStarts++ 
    app.settings.setValue("numberAppStarts", numberAppStarts)
  }

  NavigationStack {
    Page {
      title: "Settings"

      AppText {
        anchors.centerIn: parent
        text: "App starts: " + numberAppStarts
      }
    }
  }
 }