Shopify App Development

Where Is App Development in Shopify?

Where is app development in Shopify? For a current store, open Settings → Apps → Develop apps → Build apps in Dev Dashboard. That route takes you from the Shopify admin to the Dev Dashboard, which is now the central place for creating and managing new custom apps. If you are looking for the older “Develop apps for your store” screen, the interface has changed: new legacy custom apps can no longer be created directly in the admin.

The practical decision is not only where the menu is. You also need to determine whether you should install an existing Shopify App Store app, configure an app extension, create a custom app for one store or organization, or build a public app for many merchants. Each option changes the required permissions, technical scope, testing process, ownership, cost, and maintenance responsibility.

Before enabling access or approving development, define the business workflow, data involved, users affected, required Shopify surfaces, and expected support model. App development can expose orders, customers, products, inventory, checkout behavior, or external systems, so access scopes and security should be designed deliberately rather than added after coding begins.

Quick Answer: Finding Shopify App Development

Go to Shopify admin → Settings → Apps → Develop apps. For a new custom app, click Build apps in Dev Dashboard, then create or select the app in the dashboard. Shopify recommends Shopify CLI for a complete app project and supports direct Dev Dashboard configuration for backend automation, data synchronization, or API-only integrations that do not need an embedded interface.

If the Develop apps option is missing, check your role. Store owners have full access, while staff need appropriate App development permissions. Access may also depend on organization-level Dev Dashboard permissions and the ability to manage and install apps and sales channels.

Do not enable development merely to obtain an API key. First decide what the app must do, which data it needs, whether an existing app already solves the requirement, and who will maintain the integration when Shopify APIs, business processes, or connected systems change.

Key Takeaways

• Current location: Settings → Apps → Develop apps → Build apps in Dev Dashboard.
• New workflow: new custom apps are managed through the Dev Dashboard or Shopify CLI, not the old legacy admin flow.
• Permissions matter: staff need App development access and related app-management permissions.
• Choose before building: compare an existing App Store app, a custom app, and a public app against the real workflow.
• Limit data access: request only the API scopes required for the approved functionality.
• Test away from production: use a development store and verify installation, permissions, failures, upgrades, and uninstall behavior.
• Plan maintenance: API versions, webhooks, security, monitoring, and ownership continue after launch.

Table of Contents

1. Current Shopify app-development path
2. What each app option means
3. When custom development is justified
4. Permissions and access controls
5. Creating a custom app safely
6. App Store app vs custom vs public app
7. Cost, resources, and timeline
8. Testing and maintenance
9. Practical Shopify examples
10. Summary and next decision

The Current Shopify App-Development Path

Shopify’s current merchant workflow begins in the store admin, but new app creation moves into the Dev Dashboard. From Settings → Apps, select Develop apps, then Build apps in Dev Dashboard. In the dashboard, you can create an app, define configuration and access, release a version, connect a development store, install the app, and review operational information.

This change matters because instructions published before 2026 may still tell merchants to create a custom app entirely inside the Shopify admin. Existing admin-created legacy apps can continue to be managed, but Shopify states that new legacy custom apps cannot be created from January 1, 2026. For new work, use the Dev Dashboard or Shopify CLI.

Official references: Shopify’s app installation and custom app guidance and Shopify’s notice about legacy admin-created apps.

Custom, Public, and Installed Apps Solve Different Needs

An installed App Store app is usually the fastest option when the required feature is common, such as reviews, subscriptions, search, shipping rules, merchandising, or analytics. You evaluate the app’s permissions, compatibility, pricing, support, and fit, then configure it without owning the source code.

A custom app is built for a specific merchant, store, or organization. It can automate private workflows, connect Shopify with an ERP, warehouse, CRM, finance platform, marketplace, or internal tool, and provide controlled functionality that a generic app cannot match.

A public app is built for distribution to multiple merchants. It introduces a broader product responsibility: onboarding, billing, support, multitenancy, privacy obligations, app review, listing requirements, version compatibility, and scalable operations.

Shopify apps can also extend particular surfaces, including the admin, checkout, customer accounts, or storefront. The word “app” therefore does not always mean a separate mobile application. A Shopify admin extension, checkout block, backend integration, or storefront experience may be the correct solution.

Build a Custom App Only When the Workflow Requires It

Custom development is justified when the business requirement is distinctive, operationally important, and not solved acceptably by existing products. Good candidates include complex pricing, private catalog rules, specialized fulfillment, regulated approval flows, organization-specific customer portals, or reliable synchronization with a core system.

It is usually premature when the requirement is still vague, demand is unvalidated, the same outcome can be achieved through Shopify configuration, or a reputable app already provides most of the value. Building custom software creates continuing responsibility for security, hosting, monitoring, API changes, defects, and user support.

Questions to answer before development

• Which user task or operational failure is the app solving?
• Who will use it, how often, and from which Shopify surface?
• What Shopify and external data must be read, created, or changed?
• Could a workflow, theme customization, Shopify Flow, or existing app solve it?
• What happens when the integration is unavailable or data is delayed?
• Who owns the source code, hosting, credentials, documentation, and support process?

Permissions Determine Who Can Develop and What Apps Can Access

There are two permission layers to consider. First, the person creating or managing the app needs appropriate Shopify access. The store owner has full access, while staff permissions can include viewing developed apps, developing apps, and enabling development. Access to Apps settings can also require permission to manage and install apps and channels.

Second, the app itself receives API scopes. Scopes define the data and actions available to the app. A product synchronization tool may need product and inventory access; an order-routing integration may need order and fulfillment access; a reporting service may require read-only scopes. Requesting broad access “just in case” increases risk and makes approval harder.

Use named accounts, least-privilege access, documented scope reasons, and a revocation plan. Avoid sharing owner credentials with a developer. When an external specialist needs access, agree which actions require merchant approval and how access will be removed after delivery.

Create a Shopify Custom App with a Controlled Process

The interface can create an app quickly, but a production-ready implementation requires more than clicking Create app. Use a controlled sequence:

1. Define the outcome. Document the user, workflow, data, edge cases, and acceptance criteria.
2. Choose the app type and surfaces. Decide whether the solution is API-only, embedded in admin, connected to checkout, or part of a storefront.
3. Prepare a development store. Test with representative products, customers, orders, and roles without risking live operations.
4. Create the app. From Settings → Apps → Develop apps, open the Dev Dashboard and create the app. Shopify CLI is generally appropriate for a full application project.
5. Configure versions and scopes. Define URLs, webhook API version, access scopes, and release information.
6. Build authentication and data handling. Protect client credentials, validate requests, handle rate limits, and avoid exposing secrets in browser code or repositories.
7. Test failures and lifecycle events. Include expired credentials, webhook retries, partial data, permission changes, app upgrades, and uninstall behavior.
8. Install and verify. Review requested access, install in the intended store, monitor logs, and confirm that business data is correct.
9. Document ownership and support. Record architecture, scopes, deployment, rollback, alerts, contacts, and handover steps.

Compare App Store, Custom, and Public App Options

The right option depends on uniqueness, control, distribution, and operational capacity. Use this comparison before approving development.

Choose the smallest solution that meets the business need. A well-selected App Store app is often better than custom code. A custom app is valuable when control and integration justify its lifecycle cost. A public app should be treated as a software product business, not as a one-store customization.

Cost and Timeline Depend on Integration Depth

Shopify app cost is driven less by the number of screens than by business rules, data sensitivity, API breadth, external systems, reliability requirements, and operational support. A simple private data export differs substantially from real-time inventory synchronization across warehouses, or a checkout-related capability with strict performance expectations.

Budget for discovery, design, development, quality assurance, infrastructure, deployment, documentation, monitoring, and maintenance. External costs can include hosting, databases, logging, email, third-party APIs, security tooling, and support coverage. Public apps also require merchant onboarding, billing, app-review preparation, customer support, and product operations.

A useful estimate states assumptions and separates a proof of concept from production readiness. It should identify which Shopify plans and surfaces are involved, expected transaction volume, data-retention rules, dependencies, acceptance tests, and post-launch support. A phased release can validate the riskiest workflow before expanding the scope.

Testing and Maintenance Continue After Installation

A successful installation is not the end of app development. Shopify APIs are versioned, webhooks can fail or arrive more than once, permissions can change, external systems can become unavailable, and business rules can evolve. Maintenance should be designed into the solution.

• Test API responses, rate limits, retries, duplicate webhooks, and delayed events.
• Confirm data accuracy for products, customers, orders, inventory, and financial values where relevant.
• Use logs and alerts that reveal failures without exposing sensitive information.
• Review supported API versions and upgrade before deprecation deadlines.
• Recheck access scopes when functionality changes.
• Define backup, rollback, incident, and escalation procedures.
• Verify uninstall behavior and any required deletion or retention process.

Quality assurance should include technical tests and business acceptance. The merchant team must confirm that the workflow is understandable, permissions are appropriate, reports reconcile with source systems, and exceptions can be handled without unsafe manual workarounds.

Practical Shopify App-Development Examples

Example 1: A retailer needs stock synchronization

An ecommerce business assumes it needs a customer-facing mobile app because inventory errors are causing cancellations. The real problem is operational: stock quantities in an external warehouse system do not update Shopify reliably. A private custom integration is more appropriate than a mobile app. Specialist guidance helps define source-of-truth rules, retry behavior, conflict handling, and monitoring.

Example 2: A store wants a loyalty feature

A growing store plans custom development immediately, but its loyalty rules are standard and several established apps meet the requirement. Installing and testing an existing app reduces initial effort and transfers much of the maintenance responsibility to the vendor. Custom work becomes relevant only if the loyalty model or system integrations are genuinely distinctive.

Example 3: A B2B merchant has complex approvals

A B2B merchant needs account-specific catalogs, purchasing limits, internal approval routing, and ERP synchronization. Generic apps cover parts of the process but create fragmented administration. A phased custom app can first validate account rules and order approval, then add ERP synchronization after the workflow is stable.

Example 4: A software company wants an App Store product

A software company has solved a recurring merchant problem for one client and wants to sell the solution broadly. Converting the private solution into a public app requires multitenant architecture, merchant onboarding, secure authorization, billing design, support, privacy controls, documentation, and Shopify App Store review. The decision is a product investment, not a simple reuse of the original code.

Summary: Find the Menu, Then Validate the Build

For new Shopify app development, start at Settings → Apps → Develop apps → Build apps in Dev Dashboard. Existing legacy custom apps may still be managed in the admin, but new custom apps use the Dev Dashboard or Shopify CLI.

An existing App Store app is usually best when the need is common and the vendor’s permissions, support, and pricing are acceptable. A custom app fits a distinctive store or organization workflow that requires controlled integration. A public app is appropriate only when you are prepared to operate a product for multiple merchants.

Before development, validate the user need, Shopify surface, data access, scope, budget, timeline, maintenance ownership, quality assurance, security, and handover. This prevents a quick technical build from becoming an unsupported operational dependency.

FAQs About Shopify App Development

Where is app development in Shopify?

In the current Shopify admin, go to Settings, open Apps, click Develop apps, and then select Build apps in Dev Dashboard. New custom apps are created and managed in the Dev Dashboard. Legacy custom apps created before January 1, 2026 can still appear in the Shopify admin under the legacy custom apps area.

Why can’t I see Develop apps in Shopify?

The most common reason is permissions. The store owner has full access, but staff need the relevant App development permissions, including Develop, and may also need Manage and install apps and channels. An organization administrator might need to grant access before the Dev Dashboard is available.

Did Shopify remove custom app development from the admin?

Shopify stopped allowing new legacy custom apps to be created directly in the admin from January 1, 2026. Existing legacy apps continue to work, but new custom apps should be created with the Dev Dashboard or Shopify CLI.

What is the difference between a Shopify custom app and an App Store app?

A custom app is built for a specific store or organization and usually solves a private workflow, integration, or data requirement. A public app is designed for multiple merchants and can be distributed through the Shopify App Store after meeting Shopify’s distribution and review requirements.

Do I need coding knowledge to create a Shopify custom app?

Yes, meaningful custom app development usually requires knowledge of Shopify APIs, authentication, access scopes, webhooks, deployment, security, testing, and often an application framework. A simple configuration can begin in the Dev Dashboard, but production functionality normally requires a developer.

Can a Shopify collaborator create a custom app?

Collaborators can help with app work only when the store and organization permissions allow it. Shopify’s current Dev Dashboard uses organization-level permissions, and collaborator access can be more limited than staff or owner access. Confirm the required role before development begins.

Should I install an existing app or build a custom Shopify app?

Use an existing app when it already meets the requirement, has acceptable permissions, reliable support, and a sustainable cost. Build a custom app when the workflow is distinctive, the integration is business-critical, existing apps create serious limitations, or you need controlled ownership of the solution.

How are API permissions configured for a Shopify app?

API access is controlled through scopes. In the Dev Dashboard, the app version defines the URLs, webhook API version, and access scopes. Request only the permissions required for the intended features, document why each scope is needed, and review access before installation.

How should a Shopify app be tested before launch?

Use a development store or safe test environment, realistic sample data, role-based access, error logging, webhook tests, API-limit handling, security checks, and acceptance criteria. Test installation, upgrades, failure states, uninstall behavior, and data handling before releasing the app to a live store.

Can Rudrriv help with Shopify app development?

Rudrriv can support technical discovery, Shopify app planning, API integration, UI and workflow design, development, quality assurance, deployment preparation, maintenance planning, and dedicated specialist support when a custom solution is justified by the business requirement.

Need help planning a Shopify custom app?

Share the workflow, Shopify store context, users, data, external systems, and current limitations. Rudrriv can help with technical discovery, app planning, API integration, development, quality assurance, deployment preparation, maintenance planning, and specialist support where a custom solution is justified.

Discuss your requirement

At Rudrriv, we make it easier for businesses to access the right expertise, execute important work, and scale with confidence.