Get to know our frameworks

Select an app template built on your preferred framework.

Build apps on our native app editor. Use drag and drop elements, Velo code and Wix APIs to develop custom features.

Streamline your app development process with the Wix CLI. Get a familiar developer experience with minimal setup and configuration.

Take full control over your app's tech stack, deployment, and hosting.

App templates

Wix Blocks templates

Wix CLI templates

Self-hosted templates

Kickstart your app development with templates built on your preferred Wix developer tool. Browse templates for practical foundation and get to know the Wix ecosystem.

Wix App Templates for Developers

This example apps can be used as a starting point for building your own app, for concrete examples of how to use Wix framework, or for inspiration.

Choose a template.<0 />Build an app.

Browse by:

How to build it step by step:

This template is built with:

Read how this template was built, step by step.

How we built this template

Deployment instructions:

Choose a package manager and run the command in your terminal.

Copy command

Before you get started, make sure you have the following:

Prerequisite steps

Get started with Wix CLI

Begin by setting up your Next.js project with your preferred hosting platform.

Select your hosting service

Start the deployment flow and set up your template repo on Netlify. After you finish set up, come back here and add your Netlify custom domain.

Copy the code from our Git repo to deploy your app on any platform that supports Next.js.

Start the deployment flow and set up your template repo on Vercel. After you finish set up, come back here and add your Vercel generated URL.

Add the base URL and give your app a name.

App details

Go to the app dashboard and test your app to ensure a smooth integration within the Wix ecosystem. <0>Learn more about app checks and testing</0>

Define your environment

Terminal

Related templates

Note

Warning

Your app name will be used as the namespace suffix.

Name your app to generate a namespace. This lets you refer to your app in code later on.

Go Headless

Build Apps

Client

API Preview

Ricos

Develop Websites

REST

Velo

GraphQL (Alpha)

# Module Export Syntax

When exporting functions in the following files, we recommend you use the standard export syntax contained in the documentation's code examples:

+ [`events.js`](portalId::bcc88c7b-94f5-4c35-b1cb-d7a20f2669b0resourceId::595cc6cb-bc5d-484b-8f70-fac8a3abae87*fallback::https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/backend-code/web-modules/velo-backend-events)
+ [`data.js`](portalId::bcc88c7b-94f5-4c35-b1cb-d7a20f2669b0resourceId::7843d8ac-d0af-4112-9ba8-f6a81dc9cbb0slug::using-data-hooks#velo-using-data-hooks*fallback::https://dev.wix.com/docs/develop-websites/articles/databases/wix-data/hooks/using-data-hooks#velo-using-data-hooks)
+ [`routers.js`](fallback::https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/routers/about-routers)
+ [Service plugin code files](portalId::bcc88c7b-94f5-4c35-b1cb-d7a20f2669b0resourceId::1faa11b0-b2be-4d78-a100-8016cf8b1fb8*fallback::https://dev.wix.com/docs/develop-websites/articles/coding-with-velo/integrations/custom-extensions-spis/custom-app-extensions-using-sp-is)

You can also use other export formats that are part of the [ES6 (ES2015) module export syntax](fallback::https://developer.mozilla.org/en-US/docs/web/javascript/reference/statements/export). However, the following export formats are **not** supported in `events.js`, `data.js`, `routers.js`, or service plugin code files:

+ **Re-exporting a function:** Directly re-exporting a function imported from an npm or Velo package. For example, this **doesn't** work:

  ```javascript
  import { myFunction } from 'myPackage';
  
  export const wixMediaManager_onFileUploaded = myFunction;
  ```

  The following alternative syntax **is** supported:

  ```javascript
  import { myFunction } from 'myPackage';
  
  export const wixMediaManager_onFileUploaded = (paramA, paramB) => myFunction(paramA, paramB);
  ```

+ **Dynamic exports:** Exports including a dynamic operation or expression that requires execution to resolve. For example, this **doesn't** work:

  ```javascript
  import myPackage from 'my-package';
  
  export const myRouter_Router = myPackage.router((paramA, paramB) => {
    // ...
  });
  ```

  The following alternative syntax **is** supported:

  ```javascript
  import myPackage from 'my-package';

  const functionForExport = myPackage.router((paramA, paramB) => {
    // ...
  })

  export const myRouter_Router = (paramA, paramB) => functionForExport(paramA, ParamB);
  ```

+ **Exports wrapped in objects:** Exports where functions are defined as properties of an object. For example, this **doesn't** work:
  
  ```javascript
  const dataHooks = {
    beforeInsert: (paramA, paramB) => {
      // ...
    }
  };

  export const MyCollection_beforeInsert = dataHooks.beforeInsert;
  ```

  The following alternative syntax **is** supported:

  ```javascript
  const dataHooks = {
    beforeInsert: (paramA, paramB) => {
      // ...
    }
  };

  export const MyCollection_beforeInsert = (paramA, paramB) => dataHooks.beforeInsert(paramA, paramB);
  ```

+ **CommonJS exports:** Exports in the CommonJS (CJS) format that preceded ES6 (ES2015). For example, this **doesn't** work:

  ```javascript
  module.exports = {
    MyCollection_beforeInsert: () => {}
  };
  ```

Functions exported using a syntax that isn't supported aren't called by the triggering event.