• There are no suggestions because the search field is empty.
RELEASE

Marketplace Listing Page Best Practices

Vim
Vim

General

Visibility: Control who can see your app in the marketplace.

  • Public: Visible to all users on the Vim network; ideal for maximizing reach.
  • Private: Only visible to designated practices or users; good for pilots or limited rollouts.

Pricing models: Vim does not manage billing, developers own all pricing, access, and payment flows.

  1. Free Trial. Let users try your app at no cost for a limited time before requiring payment.
    1. You are responsible for managing access, billing, and post-trial conversion.
    2. Strongly recommend enabling SSO + auto-provisioning to streamline onboarding.
    3. Ensure your app:
      1. Identifies users with expired trials and returns them as “unauthorized” in the auth flow.
      2. Does not activate app status as “enabled” unless the user has converted to paid (to avoid billing errors).
  2. Free of Charge. Offer your app at no cost to maximize adoption and minimize friction.
    1. No billing or payment setup needed.
    2. SSO and auto-provisioning are still recommended for easy access.
  3. Paid Application. Charge practices directly for access to your app.
    1. You own pricing, subscription management, and all payment operations. Vim does not manage or process billing.

Distribution settings: Determine how users can access and install your application from the marketplace.

  • User-Level: Any individual can install the app. Great for solo users or small teams. Organization admins can still add the app for broader use.
  • Org-Level: Requires org admin and your review to approve. Best for practice-wide tools. 

Marketplace App Store Listing Page

Example of the Demo Canvas app store listing page here as a reference.

App Description (up to 3000 characters):
Make your app listing easy to read and visually engaging. Here’s how:

  • Keep it short and scannable -  aim for clarity and simplicity.

  • Use emojis or symbols to organize content and improve readability.
  • Group content into clear sections: Overview, Features, Audience, CTA.
  • Highlight key points with symbols like ✓, •, →, or ➤.
  • Use bullets for quick feature highlights e.g., EHR integrated
  • Organize your listing with visual section breaks e.g., Overview, Features
  • Use emojis to bring clarity and personality e.g., 🔒 Secure data
  • Present key features and availability concisely e.g., 1 line feature tables
  • Close with a compelling call-to-action e.g., Tap "Install" to get started!

Short Description (120 characters): A punchy summary of the app’s value for quick discovery.

Media (up to 5 files): The media section allows you to upload both images (screenshots) and demo videos to showcase your application's user experience and value.

  • Image specs: PNG/JPG/JPEG files. Recommended size: 1920×1080 px.

  • Video specs: MP4/MOV file. Recommended length: up to 2 minutes. 

Resources:

  • Developer name: Displayed on your app listing to identify your company or individual developer. Contact Vim Support to update.
  • Developer address: Your company’s full legal address. Contact Vim Support to update.
  • Phone number: Your main business phone number for support or inquiries. Contact Vim Support to update.
  • Support email: Public-facing email for app users and Vim to reach your support team for troubleshooting or customer assistance.
  • Network email: Used by Vim to notify you when an organization admin expresses interest in your app. Ensures smooth follow-up and faster approval.

Legal Requirements:

  1. Privacy Policy: Clearly explain how your app collects, uses, and protects user data.
  2. Terms of Service: Outline your legal agreement with users, including usage terms, restrictions, and liabilities.
  3. Business Associate Agreement (BAA) - You must choose one of the following:
    1. Public BAA (Recommended):
      Add a link to your BAA that will apply to all end users using your app. This BAA governs your access to and use of patient data, including any PHI exchanged through the app. Publishing your BAA on the marketplace streamlines onboarding by allowing clinics to review legal terms upfront.
    2. Private BAA (By Request):
      If you don’t provide a public BAA, you must submit your standard BAA to the Vim team for internal review. This means you will enter into a separate BAA with each clinic or care team member individually. Please include a brief explanation for why your BAA is not public.

Action Buttons (Optional but Highly Recommended):

  • Primary Action Button: You have an opportunity to add links to external collateral, webpages, meeting scheduling and more. Listings with additional material and transparent pricing consistently attract more engagement and installs.
  • Secondary Action Button: Use this button to drive leads or connect with interested practices. Linking to your pricing page or contact form is a great way to convert marketplace interest into conversations. Here’s a sample pricing structure you can use as a guide:
    • Basic Tier - $/month: Includes core features
    • Pro Tier - $/month: Includes advanced features such as [add brief feature info]
    • Enterprise Tier - Pricing based on number of users and usage

Categories: Choose up to 3 relevant tags for discoverability (e.g., “Care Navigation”, “Medication Management”). To add a new category, contact support@getvim.com.

Additional Best Practices:

  • SSO + Auto-Provisioning: Strongly recommended to reduce friction.
  • Keep It Updated: Refresh media, pricing, and descriptions regularly.
  • Lead Gen: Use CTAs to capture leads from orgs viewing your listing.