In order to build Saito applications you first need to install a Saito node.
Then visit our full tutorial series for new developers or jump in with the beginner lessons below:
| Tutorial | Title | Description |
|---|---|---|
| #1 | Hello World | Build an application that installs into the User's wallet and alerts the user every time their wallet loads. This explains the structure of a Saito application, the basic information you should provide to users, and how to compile and distribute your applications. All of the other tutorials in this series assume that you understand the basics covered in this tutorial. |
| #2 | Sending Transactions and UI Components | This tutorial modifies the application we built in our first tutorial. This time we use a UI Component to display a button on the page and attach a click-event. When the button is clicked, this event first and calls a function inside our module that creates a transaction and sends it out into the network. This tutorial teaches the basics of creating UI components and connecting them to functions in your core module. |
| ... | More tutorials | See the complete tutorial series for more advanced lessons. |
Once your application is built you can package it so that any wallet can install it by using our instructions on compiling applications for drag-and-drop install.
If you are an advanced developer our directory of reference modules may be of use for those who want to build "standard" applications in the same style and approach as our default application suite. You can also check out the community resource Livedocs, which serves as a working demonstration and hackable template for basic Saito applications.
The Module API explains what functions you can include in your module. The Events API explain how to listen and respond to system-wide events that are triggered when events happen like a new block being found. The Services API* explains how peers can inform other peers that they can be queried for special types of data. Finally, our Ui Components and CSS Design specifications explain our standard approach for creating UI components that will work and look good regardless of the applications that users are running.
/lib/templates/modtemplate.js file. This template file defines a number of default functions that create the basic behavior for the module. If you overwrite these functions you can customize the behavior of your module, such as specifying what actions it should take when it receives a transaction or off-chain message. This API outlines these basic functions.app.connection channel to be notified when these various events happen - this API explains how to do that and provides a short list of available events.