ShopKit documentation
Ten designed shop themes and a 48-screen core, in hand-written Flutter.
Before you start
- Flutter and Dart installed, with the toolchain for whichever platform you ship
- A backend of your own if you want real products, payments or accounts — none is included
- An Apple and a Google developer account to publish under your own name
- Nothing else to see all 192 screens: it runs on bundled mock data
A front-end template driven by bundled mock data. It contains no backend, no payment processing and no third-party service — connecting any of those is your own work and your own bill.
What it does not do
- There is no backend. No API, no database, no server — the screens run on bundled mock data.
- There are no payments, no push notifications, no maps and no chat. Connecting any of those is your own work and your own bill.
- It does not connect to WooCommerce, Shopify or any other shop out of the box.
- It is a front-end template you build and publish under your own developer account.
What is in the download
Ten complete app themes and a 48-screen Core Kit, 192 screens in total, all hand-written Flutter driven by bundled mock data.
A deliberately small dependency list. No backend, payment processing or third-party service is included — that is stated here because discovering it after purchase is the most common complaint about templates in this category.
The first build
Install Flutter, open the project and run it. The mock data means a failed first build is a toolchain problem, which is much easier to diagnose than a data problem.
Click through the theme you intend to use in full before starting work. Ten themes is ten opinions about flow, and choosing the wrong one costs more than any code you will write this week.
Connecting a real shop
Replace the mock data source rather than the screens. The screens read from a data layer; keeping that boundary is what lets you take an update later without losing your work.
Do checkout last. It is the screen most affected by whichever payment provider you choose, and building it before that decision means building it twice.
Budget for the parts that are not here — payments, push notifications, search, chat — before you promise a launch date. They are ordinary work, but they are work.
Licence, updates and support
- One licence covers 1 application you build and publish.
- 1 year of updates, from the date of purchase.
- 1 year of email support.
- Instant download + licence key by email
- 30-day money-back guarantee
Questions this page does not answer go to support@webkoding.com. If you bought from us and cannot find your licence key, look it up here.
Common questions
Is there a backend?
No, and the product page says so before you buy rather than after. ShopKit is front end only: no backend, no payments, no push, no maps and no chat. Connecting those is your own work and your own bill.
What are the ten themes?
Ten niche app designs, each with its own colour system, typography and screen flow, around a shared 48-screen core covering catalogue, search, cart, checkout, account and order tracking. 192 screens in total.
Is the Flutter hand-written or generated?
Hand-written, from a 390×844 design source. No auto-generated widgets and no placeholder filler — which is the difference between a template you can maintain and one you eventually rewrite.
Can I see it before writing any code?
It runs on bundled mock data, so every one of the 192 screens is clickable straight after unzipping, with no service to configure.
Can I publish it under my own name?
Yes — the licence covers the application you build and publish under your own developer account.
