3 minute read
If you’ve ever used Flutter and have gone through the process of creating a new Flutter Application Project, you’re more than likely aware of what a fresh application should look like. We’ve decided to create our own toolkit here on the @platform to make your ‘Getting Started’ experience that much smoother!
As of now, the only way to use this toolkit is via the command line. In the future we plan on supporting IDE extensions, be sure to check for when those come out!
at_app is our command line toolkit that can be installed via pub. Behind the scenes, it uses flutter create in order to create your project, and it completes the necessary steps to setup your @platform application for you!
flutter pub global activate at_app
Verify your system PATH variable
Note for Windows users
at_appcommand, please replace it with
at_app create [...options] path/to/your/project
In practice the command looks like this:
at_app create --namespace=myatsign myproject
In addition to the same options available for flutter create, at_app create includes three new ones to help you automatically configure your application.
|--namespace||-n||The @protocol app namespace to use for the application.||(defaults to “”)|
|--root-domain||-r||The @protocol root domain to use for the application.||[prod (default), ve]|
|--api-key||-k||The api key for at_onboarding_flutter.||(defaults to “”)|
Note: at_app create does not include
--list-samples (Coming soon).
Okay great, we know what the flags are but what do they do?
The namespace is the most important flag to include when creating your application.
When storing keys on the secondary server, the namespace is used to filter the data produced by your app from the other @platform applications. To create a namespace for your app, make sure to register an @sign from atsign.com and use that as your namespace. By owning the @sign, you can ensure that you also own the namespace.
You can specify the namespace with
By default the root domain is set to prod (production). In the production domain, you can use real @signs to test your application.
Alternatively you can specify
--root-domain=ve in the command to choose the virtual environment, and test with those @signs instead.
When you are ready to publish your application, you can request an api-key for the Onboarding Widget. This api-key will authorize your app when attempting to generate a free @sign within the widget.
You can specify this with
If you would like to update your environment at any point in time, it is safe to do so. Just specify the options you would like to change.
--overwriteflag when doing so, or it will overwrite the changes you have made to
You have successfully created your first @platform application!
Time to start coding!
We recommend checking out the demo apps that we have to offer! Reviewing these will greatly assist in your understanding of verb implementation on the @platform! It would also be a good idea to check out our @dev program which will show you how to have your app @certified and released to the market!
Sample Apps: See apps that show off the power of the @platform on your own machine!
@dev Program: Read up on how to get your @certification and go to market with your privacy-focused application!