Welcome to the documentation for AppGyver Composer Pro!
Over on YouTube we have a new series called Mevi's Component Factory. In it, AppGyver's own Mevi shows you how to build a variety of useful components in Composer Pro. These include a tag input, image picker and a calendar component.
A new tutorial on input validation has been added to the tutorials section, find it here
A new guest tutorial by MongoDB's Pavel Duchovny has been added to the tutorials section. Learn how to integrate MongoDB Realm and MongoDB Atlas with Composer Pro.
The 25 quick onboarding videos previously available on the platform itself were made part of the documentation too!
If you're new, you should start with the Introduction guide, which gives you an overview of the tool, as well as viewing the todo app tutorial video below.
If you want to get a hang of things quickly, we recommend viewing the short Composer Pro onboarding videos.
Composer Pro itself can be accessed at https://platform.appgyver.com.
This 13-minute video goes over the basic concepts of AppGyver Composer, showing you how to build an offline-capable todo application.
Highly recommended viewing
This 41-minute video goes much deeper, covering many of the more advanced features in Composer, and showing you how to build a movie review app.
The app fetches data from The Movie Database API (you can sign up for free to get an API key, see https://developers.themoviedb.org/3/getting-started/introduction) via a direct REST API integration.
The user can search for movies and view a details page.
Finally, we construct a star review widget, where the user can give the movie a rating between 1-5 stars, which is then saved in the AppGyver Cloud Storage database.
These videos show you the basics on how to user Composer Pro. Quick onboarding videos
You can make bug reports and post feature requests, as well as track our roadmap at https://tracker.appgyver.com.
If you have any general questions on Composer, the best resource is our community forums at https://forums.appgyver.com.
We're working hard to constantly improve our documentation.
Let us know of any improvement suggestions to the docs at email@example.com!