Studio · August 28, 2026
Building an Independent Digital Product Studio in 2026
Lessons from building Lumarc Studio as a solo product studio, covering product selection, technical architecture, launch strategy and sustainable development practices.
Lumarc Studio started with a question: can one person build a portfolio of useful digital products with the quality and polish normally associated with larger teams?
After launching multiple products — mobile apps on Google Play, a suite of 63 browser-based developer tools, a creative studio for app store assets, construction calculators and a technology publication — the answer is a qualified yes. Qualified because the reality of running an independent product studio is more nuanced than the “indie maker” narrative suggests.
This article shares what we have learned so far.
Choosing what to build
The hardest part of running a product studio is not building — it is deciding what to build. With limited time and resources, every product choice is a trade-off against everything else you could be working on.
Our selection criteria evolved through trial and error:
Useful over novel. We prioritise products that solve real, recurring problems over products that demonstrate technical novelty. A JSON formatter is not exciting, but developers use it multiple times a day. A construction calculator is not glamorous, but someone estimating concrete quantities needs accurate results.
Small scope, complete execution. We build products that can be launched as complete, useful tools rather than minimum viable products that need months of iteration. Water Reminder shipped as a fully functional hydration tracker on day one, not as a beta with missing features.
Sustainable maintenance. Every product we launch is a long-term maintenance commitment. We avoid products that require constant content creation, community management or operational support that would consume all available time.
Technical architecture decisions
Running multiple products as a solo operation requires architecture that minimises operational complexity.
Static sites for everything possible
Most Lumarc Studio web products are static sites built with Astro. DevTools, the marketing website, creative tool landing pages and calculators are all pre-rendered at build time and served from a CDN.
Static sites are:
- Cheap to host — CDN costs are negligible for static files
- Fast to load — no server-side rendering latency
- Secure by default — no server to compromise
- Low maintenance — no databases, no runtime dependencies, no security patches
Client-side processing
For products that need interactivity (the developer tools, calculators, the creative editor), processing happens in the browser. This eliminates the need for backend infrastructure, reduces hosting costs to near zero and provides a natural privacy guarantee.
Monorepo versus multi-repo
We use separate repositories for each product. This trades some code sharing efficiency for operational independence — any product can be deployed, updated or archived without affecting the others.
Hosting on commodity infrastructure
All products are hosted on commodity platforms (Cloudflare Pages, Vercel, Netlify) with free or near-free tiers. The total hosting cost for the entire product portfolio is under $20 per month.
Launch strategy
For an independent studio without a marketing budget, launch strategy is mostly about making products discoverable:
SEO-first content. Each product has dedicated landing pages optimised for the search queries its target users actually type. DevTools has individual pages for each tool. The creative studio has pages for each asset type. Calculators have pages for each calculation type.
App store optimisation. Mobile apps are optimised for Play Store search with clear titles, descriptive screenshots, accurate category selection and relevant keywords.
No paid advertising. All growth so far has been organic — search traffic, app store discovery and word of mouth. This is slower than paid acquisition but costs nothing and compounds over time.
What surprised us
Maintenance is the real cost. Building a product takes weeks. Maintaining it takes years. Bug reports, platform updates, dependency patches, user questions and feature requests accumulate across every product in the portfolio.
Quality earns trust slowly. Users do not immediately trust an independent studio the way they trust established brands. Every interaction — the support response time, the quality of error messages, the absence of dark patterns — contributes to trust that builds over months.
Simple products get used more. Our simplest products (the JSON formatter, the water tracker, the concrete calculator) get more consistent usage than our most technically impressive ones. Users value reliability and speed over sophistication.
Not every product needs to grow. Some products are complete at launch. Water Reminder does not need social features. The concrete calculator does not need user accounts. Resisting the urge to add features is as important as building the right features.
What comes next
Lumarc Studio continues to focus on building useful, privacy-conscious products that are complete at launch and sustainable to maintain. Current planned work includes expanding the developer tools collection, launching a mobile puzzle game and extending the construction calculator with additional calculation types.
The studio operates on the principle that many small, useful products can together serve more people than one ambitious product that tries to do everything. Each product has a clear job, a clear audience and a clear standard of quality. That is the goal.