Connect the website you already run.

Install the connector that matches your site, then set the navigation people see in the app. Your website remains the source of your content, accounts and any checkout you already have.

Install the connector that matches your website.

Use the package built for your platform and version. Find AppNuno integration packages, then test your storefront, account pages, cart, and checkout with your theme and extensions before launch.

01 · WordPress

WooCommerce

Install the AppNuno WooCommerce plugin for the WooCommerce release family used by your store. Packages cover WooCommerce 1.x through 11.x; WooCommerce must be installed and active.

  1. In WordPress, open Plugins → Add New Plugin → Upload Plugin.
  2. Upload the matching AppNuno ZIP, choose Install Now, then activate it.
  3. Open AppNuno from the admin menu, configure the navigation, and save.

AppNuno reads the current WooCommerce session for cart state and refreshes it after successful cart changes. WooCommerce does not provide a built-in wishlist, so no wishlist badge is available in this integration.

02 · PrestaShop

PrestaShop

AppNuno modules are available for PrestaShop 1.7.x, 8.x, and 9.x. PrestaShop 1.6 is not currently available; older releases are unsupported.

  1. In the back office, open Modules → Module Manager → Upload a module.
  2. Upload the ZIP matching your PrestaShop release and install it.
  3. Open AppNuno in the admin menu, or choose Configure on the module row, then save your settings.

The module uses the active customer session and current cart. When updating, install the new package without uninstalling the existing module; uninstalling removes its saved settings.

03 · OpenCart

OpenCart

Choose the package matching OpenCart 2.0.x, 2.1.x, 2.2.x, 2.3.x, 3.x, or 4.x. A release-family match does not guarantee compatibility with every theme or extension.

  1. In admin, open Extensions → Extension Installer and upload the matching AppNuno package.
  2. Open Extensions → Extensions, choose Modules, and install AppNuno Native Navigation.
  3. Choose Edit, configure the navigation, and save.

For OpenCart 4, keep the package filename unchanged when uploading. The installer uses it to place the extension correctly. The installing administrator group receives access and modify permissions; grant those permissions to other groups that need to manage AppNuno.

04 · Custom website

Manual integration

For a site without a supported store plugin, a developer must connect the site to the AppNuno storefront SDK. This is not a paste-only install: loading the SDK by itself does not provide the store configuration or session data it needs.

  1. Have the site generate its navigation configuration from the store’s actual pages and routes.
  2. Load the AppNuno SDK from https://appnuno.com/sdk/v1/appnuno.js on the storefront pages that run inside the app.
  3. Provide the SDK’s AppNunoIntegration configuration and initial state, plus a same-origin endpoint for current session state.
  4. Return a real cart count when a cart badge is configured and refresh it after confirmed successful cart changes.
  5. Test sign-in, sign-out, cart updates, destinations, and checkout in the actual store.

Custom sites do not get the plugin settings screen automatically. Their integration must supply equivalent tab, badge, back-button, appearance, and color configuration. Agree on the implementation with your website developer before launch.

What each setting controls.

The WordPress, PrestaShop, and OpenCart integrations use the same settings concepts. Some destination and route choices depend on the platform and the pages available in your store.

Navigation status

Status turns the AppNuno navigation on or off for store visitors. Turning it off hides the navigation but keeps the saved configuration.

Tabs and destinations

Add and arrange the buttons customers see. A tab’s ID is a stable internal identifier; its label is the translated text shown to customers. Choose an icon and a store page or local/custom URL as the destination. Changing a label does not change the tab’s identity.

Visibility and pages

Hide a tab without deleting its settings. Choose whether it appears on every page or only selected store pages. If no pages are selected, the tab stays hidden. Where route-specific navigation is available, it lets you tailor the tab list for particular store routes.

Badge source

Choose Disabled or Cart for each tab. The source is attached to the tab’s stable ID, not its label. Cart shows the current cart quantity from the visitor’s store session; it is refreshed from store state after successful cart changes, not incremented just because a button was pressed. A zero count hides the badge. Wishlist counts are not currently supported.

Back button

Enable or hide the app’s back control and choose Separate or In tab bar placement. On iOS the choice controls the visible back button. Android uses its system back button or gesture.

Glass appearance

Enable or disable the translucent Liquid Glass effect. Choose whether its color scheme follows the device or stays light/dark; Regular keeps the usual effect, Clear makes it more transparent, and None turns it off. Animation makes appearance changes smooth, and duration sets how long they take (zero changes instantly). Interactive glass responds to touch on supported devices. Tint color blends into the surface, while opacity controls its strength from none to full. Liquid Glass is for supported iOS versions; other devices use their regular navigation appearance.

Light and dark colors

Set the navigation background and the content color used for labels and icons, separately for light and dark appearance. The app selects the matching appearance for the storefront.

Saving and testing

Save changes in the store’s AppNuno settings. Then open the app experience and check tab order, translated labels, destinations, visibility, cart updates, and the checkout path in every language and route you use.

Keep the store in control.

AppNuno navigation does not replace or edit your product catalog, store pages, customer accounts, or checkout. Cart and sign-in behavior still depends on the store session, theme, extensions, and payment flow, so test those journeys on your own site.