What I learned packaging 31 source-code products for sale

Marco Loos — Tue, 01 Sep 2026 21:32:39 +0000

Selling source code is not the same as uploading a repository. A buyer needs to understand what the product does, what is included, how it starts, which services it depends on, and what rights the purchase grants.

I recently packaged a catalog of 45 digital products: 31 apps/source-code products and 14 ebooks/bundles. The software catalog spans private AI, React Native and Expo, subscriptions, productivity, marketplaces, mobile utilities and games.

Five lessons from the packaging work

1. Separate the product from the development environment

The deliverable should not depend on private machine paths, local caches or undocumented tools. Buyers need an explicit dependency list and repeatable installation steps.

2. Never ship secrets

API keys, tokens, private environment files and production credentials are not product assets. A clean package should include safe placeholders and explain which buyer-owned credentials are required.

3. Make licensing precise

A download license and a complete IP acquisition are different products. For example, CHAVA Gold 4.0 is available as a €59 source-code license, while its full software/IP acquisition is a separate €19,500 transaction.

4. Documentation is part of the product

A concise README, architecture overview, installation guide, dependency notes and buyer-handover checklist often determine whether source code is usable after purchase.

5. Be honest about traction

These listings are newly launched and currently pre-revenue. I would rather give buyers a verifiable technical package than invent revenue claims.

What is in the catalog?

Highlights include CHAVA Gold 4.0, the Expo RevenueCat Launch Kit, NEXUS, OC OriginalCheck, Task Flow Pro, MineX, LifeTree and multiple mobile/game products. The book catalog includes ADHD Life Systems, caregiver-support resources and fiction.

Browse all 45 products: https://marcomatic06.gumroad.com

Complete CHAVA software/IP acquisition: https://vertosmarket.com/project/cmtes8ik2000klrcsufkxhi9z

I am interested in feedback from developers, agencies, distribution partners and technical buyers: what evidence do you require before buying packaged source code?

How I structured an Expo + RevenueCat starter that cannot charge in preview mode

Marco Loos — Tue, 01 Sep 2026 20:12:58 +0000

Subscription UI is easy to mock. Subscription state is where a mobile project usually starts accumulating edge cases.

For an Expo app, I wanted one small reference implementation that handled the current RevenueCat offering, localized package prices, purchases, cancellation, restores, entitlement state, optional custom user IDs, and customer-info updates without scattering the logic across every screen.

The key design decision was an explicit preview mode.

Before public SDK keys and native store products are configured, the app can render the complete paywall and navigate through its interface, but purchase and restore actions remain unavailable. Preview data is clearly separated from live RevenueCat data, so a developer can review the UI without suggesting that a real transaction is possible.

Once live configuration is present, the service layer initializes RevenueCat with the platform-specific public key, optionally identifies the user, retrieves the current offering, listens for customer-info changes, and maps the configured entitlement into a small app-level state.

The paywall itself does not need to know how RevenueCat is initialized. It receives packages and state, then calls purchase or restore actions exposed by the subscription layer. That keeps store-specific details out of the UI and makes the failure states easier to explain.

Before packaging the reference app, I ran a strict TypeScript check, Expo Doctor with 21/21 passing checks, and a clean static web export. The downloadable package also includes a setup guide and a real-device test checklist because a browser preview cannot validate Apple or Google billing.

I released the complete source as the Expo RevenueCat Launch Kit. This is my paid product, and I am linking it transparently rather than presenting this article as independent coverage:

https://marcomatic06.gumroad.com/l/expo-revenuecat-launch-kit/LAUNCH25

The launch link gives the first 10 buyers 25% off for 72 hours. The kit is an independent developer resource and is not affiliated with RevenueCat or Expo.

DEV Community: Marco Loos