How Should a Shopify Developer in Spain Show Apps, Themes, and Client Stores?

A Shopify developer should group public apps, reusable themes, and client stores by what they delivered, then give each entry a safe public destination and a precise statement of their own role.

A store homepage can prove that a merchant is live, but it rarely proves who built the theme, checkout integration, or back-office workflow. Your portfolio has to add that missing context without revealing administration screens, sales figures, customer data, or code owned by the client.

Which Shopify projects belong in the portfolio?

Include public apps, themes, approved client builds, and reusable integrations that demonstrate work you can discuss and still verify.

Treat a complete merchant build as one project even when it contains theme work, migrations, and integrations. Create a separate entry for a public app or theme only when it has its own destination and maintenance story.

Exclude experiments that are merely tutorial copies and client work you are not allowed to name. An anonymised case can remain useful if the problem, your responsibility, and the permitted proof are specific.

What is the fast way to build the Shopify portfolio with IndieShow?

The fast way is to add one IndieShow card per app, theme, or approved store and organise the cards by current delivery status.

Use a logo you have permission to display, a tag such as Shopify app or custom theme, and a description that states your contribution. Point the card to the app listing, product site, theme page, approved case study, or public storefront—whichever best proves that project.

IndieShow gives you one stable personal URL and an editor with live preview, so the portfolio does not depend on rebuilding a custom site each time a merchant launches or an app is retired.

Build your IndieShow pageClaim your handle, organise the evidence in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

Should a client-store card link to the storefront or a case study?

Link to an approved case study when your role needs explanation; use the storefront only when it is stable, public, and the merchant permits the reference.

A live store can change after your engagement ends. State the scope and delivery period in your description so later design or operational changes are not mistaken for your work.

Never link an admin route or share screenshots containing orders, customer details, analytics, or private configuration. When the public store no longer demonstrates the work, archive the entry or replace its destination with an approved case study.

How do you describe results without exposing merchant revenue?

Describe the delivered capability and use a result only when the merchant has approved the wording and you can substantiate it.

Useful descriptions name the constraint and the change: a custom product flow, a catalogue migration, a theme rebuild, or an integration you owned. They do not need a confidential sales number to show technical relevance.

Leave IndieShow's optional metric empty when the evidence is private. Do not turn an estimate, platform dashboard, or client conversation into a public claim without explicit permission.

How does IndieShow keep a Shopify portfolio current?

IndieShow keeps it current by letting you move each app, theme, or store between active, in-progress, unsuccessful, and archived sections while preserving one personal link.

Audit public destinations regularly because stores close, domains change, and listings can disappear. A retired app can remain in Archived with an honest description and no dead destination.

That maintained IndieShow page becomes the index you send in proposals: public products first, relevant client evidence next, and confidential details kept out of the page.