Native Apps Framework Workflow¶
This topic describes the workflows for developing, publishing, and installing an application created using the Native Apps Framework.
The following workflow outlines the general tasks for developing and testing an application using the Native Apps Framework:
Developing an application is an iterative process. You might perform many of these tasks multiple times or in a different order depending on the requirements of your application and environment.
Create the setup script for your application.
The setup script contains the SQL statements that define the components created when a consumer installs your application.
Create the manifest file for your application.
The manifest file defines the configuration and setup properties required by the application, including the location of the setup script and versions.
Upload the application files to a named stage.
The setup script, the manifest file, and other resources that your application requires must be uploaded to a named stage so that these files are available as you develop your application.
An application package is a container that encapsulates the data content, application logic, metadata, and setup script required by an application.
Adding versions and patches to your application allows you to add features to your application or fix problems.
The Native Apps Framework allows you to securely share your data content with consumers.
You can include business logic as part of your application. An application can contain:
To troubleshoot an application, the Native Apps Framework provides logging and event handling. Consumers can set up logging and event handling in their account and share them with providers.
A release directive determines which version and patch level are available to consumers.
Before you can share an application with consumers outside your organization, the application must pass an automated security scan to ensure that it is secure and stable.
After developing and testing the application, providers can publish the application to share it with consumers. See Sharing an Application with Consumers for details.
Becoming a provider allows you to create and manage listings to share your application with consumers.
You can create a private listing or a Snowflake Marketplace listing to share your application with consumers.
Before you can publish a listing to the Snowflake Marketplace, you must submit the listing to Snowflake for approval.
After your listing is approved, you can publish the listing to make it available to consumers.
Consumers can discover the application and install it from a listing. After installing the application, consumers can configure, use, and monitor the application. See Working with Applications as a Consumer.
Becoming a Snowflake consumer allows you to access listings shared privately or on the Snowflake Marketplace. You can also access data shared as part of direct shares or data exchanges, which offer more limited data sharing capabilities.
Consumers can install an application from a listing.
Some applications might ask the consumer to grant global and object-level privileges to the application.
A provider can set up an application to emit logging and event data. A consumer can set up an events table to share this data with providers. Logs and event data are useful when troubleshooting an application.
After installing and configuring the application, a consumer can perform additional tasks to use and monitor the application.