Looking to put your Backendless skills to use for some side cash? With the new Backendless Marketplace, you can create your own App Blueprints to list for sale to the Backendless community.
App Blueprints are fully-functional app or website templates in Backendless. Any Backendless user can build and list their own App Blueprint on the Marketplace. At this time, Blueprints can be listed for free. Listing for one-time fee is coming soon.
The following are examples of Blueprints that qualify*:
- Complete web app with frontend built in UI Builder and backend and database built in Backendless.
- Use-case-specific backend/database structure with backend automations. (A basic frontend is strongly recommended, or instructions for connecting one.)
- Simple, single-page landing page built in UI Builder. (Database-driven image & content delivery recommended; you can learn more about linking images to URLs in file storage here.)
- Complete web app frontend built in UI Builder and designed for integration with a coded backend/database. (Instructions should be provided for minimum backend setup.)
*All submissions are reviewed prior to publication. Backendless reserves the right to reject any submission for any reason; a reason will be provided for all rejections.
In this article, we will lay out the basic guidelines for listing an App Blueprint on the Backendless Marketplace. We will also provide formatting, style and content guidelines for the app’s Instructions document.
Each App Blueprint submitted to the Marketplace will be reviewed by the Backendless team before publication. To give your submission the highest probability of acceptance, please follow the proceeding guidelines.
- Provide a description and clear instructions for your blueprint
The description to describe the app’s purpose, type, and general functionality. The instructions should adhere to the Instructions Guide below.
- Remove any unnecessary data tables, folders and files
All contents of the App Blueprint that are not standard with every Backendless app should have a specific purpose which should be described in the Instructions.
- Make sure any left over data in the database is removed
All data tables should be empty with the exception of 1-2 demo objects (only if absolutely necessary).
- Make sure any image files referenced in the database and CSS extensions are referenced using relative paths
For example, an image file URL should look like this
/ui-builder/containers/default/styles/img/home/home-photo-bg.jpg. The URL should not include
- Configure permissions
If your application requires user registration and login, adjust permissions for the
NotAuthenticatedUsersecurity role. If any other permissions are adjusted from default or if other security roles are included in the Blueprint, include the purpose of such modifications in the Instructions.
- Include push notification setup instructions (if applicable)
If your application requires Android/Apple certificates for push notifications, make sure to describe it in the instructions and remove the certificates from your application.
- Include Google Maps setup instructions (if applicable)
If your application uses Google Maps API key, make sure to describe the setup process (described in this video) in the instructions and remove the API key from your application.
- Clear custom domain(s)
If your application uses a custom domain, make sure to remove it before publishing the app.
- Clear and define custom SMTP server configuration (if applicable)
If your application uses custom SMTP server configuration, make sure to clear it in your app and describe in the instructions the need for a custom SMTP server configuration.