---
title: "Learn by doing: dashboard to first app"
description: "Small dashboard fragments and ready-to-run first projects for every listed language and WooCommerce."
slug: "/docs/v1/tutorials"
section: "Practical tutorials"
order: 1000
audience: "all"
level: "beginner"
last_updated: "2026-10-26"
version: "v1"
related: ["/docs/v1/tutorials", "/docs/v1/tutorials/python", "/docs/v1/sdks/capabilities"]
draft: false
layout: "guide"
---

## Choose the language you already use

Every guide follows the same small steps: **open this section → enter these values → save → run the example → see the result**. Dashboard fragments use example data and do not change your account. You do not need to program a whole application to try the first export.

| Language | Learning path | What the provided example uses |
| --- | --- | --- |
| Python | [Desktop + web + credits](/docs/v1/tutorials/python) | Official Python SDK; real desktop window, local Flask app and durable credit job |
| PHP | [First export](/docs/v1/tutorials/php) | Official native SDK directly |
| JavaScript | [First export](/docs/v1/tutorials/javascript) | Official native SDK directly |
| Rust | [First export](/docs/v1/tutorials/rust) | Official native SDK directly |
| C# | [First export](/docs/v1/tutorials/csharp) | Official native SDK directly |
| TypeScript | [First export](/docs/v1/tutorials/typescript) | Native language launcher + clearly identified local Python SDK helper |
| Java | [First export](/docs/v1/tutorials/java) | Native language launcher + clearly identified local Python SDK helper |
| C | [First export](/docs/v1/tutorials/c) | Native language launcher + clearly identified local Python SDK helper |
| C++ | [First export](/docs/v1/tutorials/cpp) | Native language launcher + clearly identified local Python SDK helper |
| Go | [First export](/docs/v1/tutorials/go) | Native language launcher + clearly identified local Python SDK helper |
| Ruby | [First export](/docs/v1/tutorials/ruby) | Native language launcher + clearly identified local Python SDK helper |
| Kotlin | [First export](/docs/v1/tutorials/kotlin) | Native language launcher + clearly identified local Python SDK helper |
| Swift | [First export](/docs/v1/tutorials/swift) | Native language launcher + clearly identified local Python SDK helper |
| Dart | [First export](/docs/v1/tutorials/dart) | Native language launcher + clearly identified local Python SDK helper |

[Download Python desktop/web projects](/docs/downloads/kdpika-python-projects-1.0.0.zip) · [Download the other-language first projects](/docs/downloads/kdpika-first-projects-1.0.0.zip).

## No code? Start with your store

[WordPress + WooCommerce: connect, map and test a purchase](/docs/v1/tutorials/woocommerce). This sets up license delivery from store orders without writing an SDK. The software you sell still needs its own app-side licensing integration; a store plugin cannot protect an arbitrary executable automatically.

## The easiest order to learn

1. Create one normal Sandbox license with `csv_export` and make one successful export.
2. Learn device allowance and offline access.
3. Add shared seats **or** usage credits only when your product needs it.
4. Adjust one customer with an override, then try the hosted portal and your brand.
5. Test your target machines and real sales flow before deliberately switching to Live.

[See all five licensing models as dashboard steps](/docs/v1/tutorials/python). Python explains the shared dashboard settings in full; the same settings apply to every language. Only the client calls differ.

## Keep these names separate

Your **KDPika subscription** determines the developer capabilities available to your workspace. Your **software plan** defines what your customers get. One **license** is one customer's access. Products, monthly requests and workspace devices are not local Python/Java/C# constants.

A REST transport sample is not a full SDK. The helper routes are marked clearly and require Python. No browser/WASM hardware fallback, automatic native app protection, custom-domain hosting or exactly-once external payment execution is promised.