DEV Community: TAMSIV

From Idea to Production in 6 Months — A Solo Developer's Journey

TAMSIV — Sat, 04 Apr 2026 07:04:27 +0000

Six months ago, I had a sticky note problem.

My wife would add "kid's shoes" to the grocery list while I was driving. I couldn't write anything down without stopping, unlocking my phone, opening an app, typing... So I opened VS Code. And didn't close it for 6 months.

Today, TAMSIV is live on Google Play Store. In production. For everyone.

What is TAMSIV?

A voice-powered task and memo manager with conversational AI. Press the mic, speak naturally, and the AI creates tasks, memos, or calendar events — organized in the right folder, with the right priority, at the right time.

The stack

Frontend: React Native 0.81 (TypeScript, New Architecture / Fabric)
Backend: Node.js/Express + WebSocket, port 3001
Database: Supabase PostgreSQL — 3 schemas (privat, collaborative, gamification), 30+ tables, 40+ RLS policies
AI: OpenRouter (400+ models), native on-device STT, OpenAI TTS (6 voices)
Website: Next.js 16 + Tailwind CSS 4 on Vercel
Payments: RevenueCat (Free / Pro / Team)

750+ commits, 25 features shipped

Here's what made it to production:

🎙️ Conversational voice AI with 8 function tools
📋 Tasks and memos with photos, videos, PDFs
📅 Calendar with 5 views, recurrence, smart reminders
👥 Real-time collaboration (groups, assignments, checklists)
📁 Unlimited hierarchical folders
🏆 Gamification — 12 levels, 10 badges, streaks up to 365 days
🌍 6 languages (FR, EN, DE, ES, IT, PT)
🖥️ Full web companion app at tamsiv.com
🎨 AI-generated images (Runware HiDream)

The bugs that almost killed launch

6 hooks DDoSing my own database on startup. Six independent React hooks calling getGroups() concurrently. Six identical Supabase queries saturating the connection pool. Fix: one shared GroupsContext.

AI inventing impossible dates. February 29 on non-leap years, "Monday the 15th" that was actually a Wednesday. Fix: server-side validateAndFixDate() + pre-computed day tables in the prompt.

WebSocket callback conflicts. The AI setup screen and dictaphone fighting for the same channel. 3 hours to isolate.

i18n as an acquisition channel

Before launch, I translated everything into 6 languages. Result: 60% of website visitors don't speak French. Germany is the 3rd largest market — without a single German social post. Every language is a door.

What's next

TAMSIV is free — all core features work without paying. iOS is planned.

If you're a developer, the technical decisions are real, the bugs are real, and the code is production code.

If you need a voice-first task manager, give it a try and break things.

📱 Download on Google Play
🌐 Website
▶️ Demo video

Built solo. 750+ commits. October 2025 → April 2026.

38 Commits, Zero New Features — How I Made My Web App Production-Ready

TAMSIV — Wed, 01 Apr 2026 08:07:32 +0000

Sometimes the most important sprints are the ones where nothing new gets shipped.

38 commits in 10 days. Zero new features. But TAMSIV's web dashboard went from "it works" to "it's ready."

The Agenda Gets Real

The web agenda had one view — week. Functional, but limiting. Now it has four: day, week, month, year. Click any event, see its details. Click any task, same thing. Task and memo detail pages were completely redesigned to match the mobile app.

The goal: make the transition between phone and desktop invisible. You create a task by voice on your phone, you find it on your computer with the same layout.

Safety Nets: Crashlytics + Sentry

When your app is used by you and 12 testers, you can debug via Supabase logs and "works on my machine." When you're about to go public, that's not enough.

Two monitoring systems were added:

Firebase Crashlytics on the React Native frontend — catches crashes, ANRs, uncaught JS errors, with full stack traces
Sentry on the Node.js/Express backend — catches API errors, WebSocket timeouts, unhandled exceptions, with breadcrumbs and performance monitoring

When a bug happens in production, we know before the user complains.

The AI Learns Your Naming Habits

One commit. But the kind that changes daily experience.

The voice assistant now analyzes your existing folder names to detect naming patterns. If all your grocery folders start with the store name ("Groceries Carrefour", "Groceries Leclerc"), the AI picks it up and suggests the same pattern for new folders.

No user will ever ask for this. But everyone notices when it's there.

Performance & CRO

The landing page hero used a JavaScript Canvas for its animated glow effect. Beautiful, but heavy — especially on mobile. Replaced with pure CSS. Same visual, zero battery drain.

Other landing page fixes: hero subtitle rewritten for clarity, pricing layout improved, header scroll spy fixed.

Smarter Tracking

UTM parameters on every shared link — to know which post, channel, campaign drives traffic
Server-side IP capture — more reliable than client-side JavaScript
Admin dashboard — period selector (7d/30d/90d/all), config synced between mobile and web

versionCode 32

Build 32 on the Play Store. 740+ commits. Production review pending at Google. We polish, we wait, we polish again.

38 commits, zero features, and an app that went from "it works" to "it's ready."

📖 Full article on the blog: tamsiv.com/en/blog
📱 Try it: Play Store

I Translated My App Into 6 Languages Before Launch. Here's What the Data Says.

TAMSIV — Tue, 31 Mar 2026 08:58:54 +0000

Everyone told me I was crazy.

"You haven't even launched in France yet, and you're translating into German?"

I did it anyway. Here's what happened.

The Decision

TAMSIV is a voice-powered AI task manager I've been building solo for 6 months (730+ commits). When I hit the i18n milestone, I had a choice: launch in French first and "see how it goes," or go all-in on 6 languages from day one.

I chose the second option. I wrote an AI translation script that processes 1,993 keys across 5 target languages (English, German, Spanish, Italian, Portuguese) using OpenRouter. I localized the Play Store listing. The website. Even the voice assistant understands context in multiple languages.

Total investment: about 2 days of work.

The Data (41 days of tracking)

Here's what tamsiv.com analytics show after 41 days:

2,206 unique visitors total
1,142 unique visitors in the last 7 days alone

But the number that stopped me:

60% of visitors don't speak French.

Language breakdown (last 7 days)

Language	% of traffic	Unique visitors
🇫🇷 French	40%	440
🇬🇧 English	20%	226
🇩🇪 German	13%	150
🇪🇸 Spanish	10%	118
🇮🇹 Italian	9%	113
🇵🇹 Portuguese	8%	98

Germany is the third largest market. I never wrote a single German social media post. Zero German marketing. These visitors found TAMSIV through:

Localized Play Store listings — each language has its own title, description, and screenshots
Google searches in their language — the website auto-detects and serves the right locale
Automatic language routing — tamsiv.com detects browser language and redirects

The Technical Setup

Translation script

I use OpenRouter with a configurable model to translate JSON key files:

// Pseudo-code of the translation pipeline
for (const locale of ['en', 'de', 'es', 'it', 'pt']) {
  const translated = await openrouter.chat({
    model: process.env.OPENROUTER_MODEL,
    messages: [{
      role: 'system',
      content: `Translate to ${locale}. Keep placeholders like {name} intact. Adapt idioms naturally.`
    }, {
      role: 'user', 
      content: JSON.stringify(frenchKeys)
    }]
  });
  writeFile(`locales/${locale}.json`, translated);
}

Key decisions:

French as source language (not English) — my native language, so the source is always natural
AI translation with human review — I review German/Spanish/Italian with native speakers when possible
9 passes per language — the script runs multiple passes to catch context-dependent translations
Placeholder preservation — {taskCount} tâches must become {taskCount} tasks, not {taskCount} Aufgaben tasks

Play Store localization

The Play Store supports per-language metadata. I localized:

App title (30 chars)
Short description (80 chars)
Full description (4000 chars)
Release notes

This is probably the highest-ROI i18n work. People search the Play Store in their language. If your listing isn't localized, you're invisible.

Website (Next.js + next-intl)

/fr/  → French (default)
/en/  → English
/de/  → German
/es/  → Spanish
/it/  → Italian
/pt/  → Portuguese

Each locale has its own translated slugs, meta descriptions, and Open Graph tags. The x-default hreflang points to /fr/ (primary market).

The Surprising Insight

The most visited non-homepage pages are:

/fr/politique-de-confidentialite (165 visits)
/fr/suppression-compte (92 visits)

These are Play Store required pages (privacy policy, account deletion). Their high traffic confirms that people are finding TAMSIV through the Play Store, clicking these links, and landing on the website. The Play Store localization is driving real traffic.

Another Data Point

12 people clicked "Download for iOS." The app is Android-only.

12 strangers, somewhere in the world, want TAMSIV on iPhone. That's not a metric — that's a roadmap.

The Lesson

i18n is not polish you add after launch. It's an acquisition channel.

Every language is a door. I spent 2 days opening 5 extra doors, and 60% of my traffic walks through them.

If you're building a side project and thinking "I'll translate later" — consider translating now. The Play Store alone makes it worth it. And with AI translation tools, the cost is nearly zero.

What's Next

Production release is pending (waiting for Google Play review)
iOS version is now on the roadmap (thanks to those 12 clicks)
German-language content might be worth creating (13% is significant)

TAMSIV is a voice-powered AI task manager — speak your tasks, memos, and calendar events instead of typing them. Free on Android.

🌐 tamsiv.com
📱 Play Store

How I Added Voice-Based AI Personalization Two Days Before Launch

TAMSIV — Sun, 29 Mar 2026 08:47:35 +0000

Since October, TAMSIV's voice AI understood commands perfectly. "Create a task", "add a memo", "check my schedule" — all worked. But the AI didn't know the user.

Say "remind me about the thing for the kids" and it had no idea you had kids.

Two days before public launch, I shipped voice-based AI personalization.

Configure Your AI by Talking to It

A new screen: "Configure my AI". You tap, you talk:

"I'm a parent of 3, I manage a cleaning crew of 4, and I forget everything after 30 seconds."

The AI listens, summarizes your context, stores it. From that point on, every response is tailored. "The little one" means your son. "Tuesday's site" means your field intervention.

The implementation: the custom context is sent as part of the system prompt to OpenRouter. The LLM sees it on every conversation turn. Simple, but the UX around it — the onboarding flow, the voice recording, the save/edit/delete — that's where the 1,800 lines went.

6 TTS Voices with Live Preview

Voice is personal. The same robotic voice 50 times a day gets old.

I added a voice selector: 6 OpenAI TTS voices, each with a live preview button. Tap → hear "Hello, I'm your TAMSIV assistant" in that voice → choose. Saved to the user profile, used for all responses.

The tricky part: the preview uses the same WebSocket pipeline as the main dictaphone. Which led to...

The 3-Hour WebSocket Bug

The AI setup screen and the dictaphone share one WebSocket connection. When you preview a voice in setup, the dictaphone's callbacks also fired — processing audio meant for the setup screen.

Fix: an "active owner" pattern. When setup opens, it claims exclusive WebSocket ownership. The dictaphone's callbacks become no-ops until setup closes. Clean in theory, 3 hours of debugging because the conflict only appeared on specific Android models with aggressive garbage collection.

Personalization as a Feature Gate

AI personalization is now part of the Pro/Team plans in the pricing. Free users get basic context, paid users get full customization + voice selection. Added to the pricing page on the website too.

730+ Commits, Monday Is Launch Day

This was the last feature. The app now knows who it's talking to.

Monday, TAMSIV goes public on the Play Store. 6 months of solo development, and the AI finally has context.

TAMSIV is a voice-powered task and memo manager with AI. Try it on Android or visit tamsiv.com.

Vanishing Reminders and Missing Emails — The Never-Ending Quality Sprint

TAMSIV — Thu, 26 Mar 2026 09:16:49 +0000

When you're building an app solo, some weeks you ship shiny new features. Other weeks, you spend your evenings hunting bugs nobody reported — because you found them yourself while dogfooding your own app. This was the second kind of week on TAMSIV.

Here's a rundown of four fixes that look small on their own. But stacked together, they genuinely improve the daily experience.

Reminders That Vanished Into Thin Air

The scenario: you create a task with three reminders — one in 10 minutes, one tomorrow morning, one on Friday. But the first reminder is already in the past (you took too long to confirm). TAMSIV would display a warning: "This reminder is in the past." Fair enough.

The problem? Dismissing that warning wiped all reminders. The two perfectly valid future reminders were gone too. An overzealous cleanup in the validation logic.

The fix now clearly separates past reminders from future ones. The warning only targets what's actually expired, and upcoming reminders stay untouched.

Email Reminders That Never Arrived

TAMSIV supports two notification channels for reminders: push and email. In practice, when a user created a reminder, only the push channel was enabled by default. Email? Silently disabled.

Now both channels are enabled by default. You get a push and an email.

The Ghost Error on Cold Start

You open the app after a few hours of inactivity, and for a split second an "Invalid Refresh Token" error flashes on screen. Then everything works fine.

On cold start, Supabase tried to refresh the auth token. If it had expired, the SDK threw an error before the automatic reconnection mechanism had time to kick in. The error bubbled up to the UI when it had no business being there.

The fix intercepts this specific error at the right level and suppresses it from the display.

Badge Guide Translated Into 6 Languages

TAMSIV is available in French, English, German, Spanish, Italian, and Portuguese. But the badge explainer guide only existed in French and English. Fixed — all 10 badges are now translated into all 6 languages.

What's Next?

These four fixes represent roughly a day's work. None of them would make for an exciting changelog headline. But together, they eliminate real friction.

The quality sprint continues. 720+ commits and counting.

📖 Full article on the blog
📖 New: Productivity App Fatigue
📲 Try TAMSIV on Android

TAMSIV Has a Face — First Demo Video + Quality Sprint

TAMSIV — Wed, 25 Mar 2026 13:16:07 +0000

For 6 months, TAMSIV existed only as text and screenshots. Today, for the first time, the app has a face: a full demo video.

Why a video now?

A voice app needs to be seen. Reading "speak, AI understands and organizes" isn't enough — you need to see the mic activating, the real-time transcription, the task being created automatically in the right folder.

The video shows all of that in 2 minutes. It's now embedded directly in the website's hero section.

Quality sprint: 7 commits, 0 new features

Alongside the video, I spent a week on a 100% quality sprint. No new features — only polish, reliability, and silent fixes.

Dictaphone: 100% reliable stop button

The most frustrating bug: sometimes the "stop" button wouldn't respond. The mic kept recording, forcing users to kill the app.

The cause? A timing issue between native STT initialization and React state. The fix:

A "standby" mode for native STT — ready instantly without blocking the UI
Recording start 2x faster (no callback wait)
A stop button that works 100% of the time

Multi-day voice agenda queries

Previously, asking "what do I have this week?" only worked for a single day. Now the assistant understands ranges: "Monday to Friday", "the next 3 days", "this week".

AI images: switch to HiDream-I1-Fast

Folder cover images are AI-generated. SDXL 0.9 poorly understood complex prompts. HiDream-I1-Fast: better comprehension, more consistent results, ~$0.003 per image.

Folders: instant display

In collaborative groups, the folder tree waited for all content to load. Now it shows instantly — content loads in the background.

Security: data leakage fix

Critical bug: on shared devices, previous user's data could briefly appear when switching accounts. The singleton cache wasn't cleared on logout. Fixed with complete state cleanup.

What I take away

A quality sprint isn't glamorous. No new feature, no before/after screenshot. But it's what separates an app people try from an app people keep.

The video is the opposite: the moment the project becomes tangible for someone who's never touched it. Both complement each other — the storefront and the foundation.

📲 Try TAMSIV on Google Play
🌐 Website
📖 Full blog post

Why Productivity Apps Fail with ADHD — and the 3 Principles That Actually Work

TAMSIV — Mon, 23 Mar 2026 11:40:01 +0000

On Reddit, the same post shows up every week. Someone writes: "I downloaded a new productivity app. The first three days were amazing. Now it's collecting dust on my phone."

If you have ADHD, you know this cycle by heart. Download → get excited → forget → feel guilty → avoid → uninstall. And start over with the next "miracle" app.

The problem isn't you. It's that 95% of productivity apps are designed for neurotypical brains.

The real problem: friction

Open the app. Find the right list. Tap "+". Type the task. Pick a date. Select a category. Six steps. For an ADHD brain, that's five too many.

Each step is a chance to get distracted, lose your train of thought, or tell yourself "I'll do it later" — which means never.

Apps like Todoist, TickTick, or Notion are great for people who enjoy organizing. But with ADHD, the problem isn't organizing — it's capturing before the thought disappears.

Principle 1: Reduce friction to zero

Capturing should take less than 5 seconds. Period.

The fastest method: voice. You think something, you say it out loud, it's recorded. No screen to navigate, no text to type, no category to choose.

Apps like TAMSIV or even Google Tasks' voice input allow this. The goal isn't to find the perfect app — it's to find the one that puts the fewest barriers between your thought and its capture.

The test is simple: if you have to think about HOW to note something down, the app has already failed.

Principle 2: Make progress visible

The ADHD brain needs immediate feedback. A shrinking task list isn't enough — we need to SEE that we're making progress.

That's why gamification works surprisingly well:

Streaks: "Day 27 without breaking the chain" creates a loss aversion that's more motivating than any to-do list.
Levels: Going from "Beginner" to "Organizer" to "Expert" — the brain loves progression narratives.
Badges: Visual rewards for specific actions. It sounds childish, but it activates the reward circuit exactly the right way.

Habitica does this with an RPG angle. TAMSIV does it with levels and daily challenges. Even a simple counter of completed tasks on a sticky note can work. What matters is that progress is VISIBLE.

Principle 3: Flexibility without guilt

Apps that punish you for missing a day are toxic for ADHD. You miss Monday, feel guilty Tuesday, avoid the app Wednesday, and it's over.

The app that works for ADHD lets you pick up where you left off. No passive-aggressive "You missed 3 days!" message. No streak reset without a safety net.

Moving a task to tomorrow isn't failure — it's realistic planning.

Capture first, organize later

The classic trap: trying to organize AT THE MOMENT you capture. "Which folder does this task go in? What priority? What date?"

Stop. Capture first. Organize during a dedicated moment (5 minutes in the morning or evening). These are two different mental modes, and mixing them is exhausting for an ADHD brain.

With voice capture, it's natural: you speak, it's captured. You organize later, with a clear head.

What really matters

The perfect app doesn't exist. But apps that work with ADHD always have these three things: minimal friction, visible progress, flexibility without judgment.

If your current app makes you feel guilty when you open it, it's not the right one. Switch. Test. The right app is the one you still open 30 days from now.

How I Gave My Voice AI the Ability to Read Your Schedule (Not Just Write To It)

TAMSIV — Mon, 23 Mar 2026 08:26:38 +0000

For five months, my voice AI assistant could create tasks, memos, and calendar events. It could write. But it couldn't read.

If you asked "What do I have tomorrow?", it had no idea. It only knew write commands — create, update, delete. Your actual schedule? Completely opaque.

This week I changed that. Here's how.

The Problem

My app TAMSIV uses a voice pipeline: audio → Deepgram STT → OpenRouter LLM → function calling → OpenAI TTS. The LLM has 7 function tools: create_task, update_task, create_memo, update_memo, create_calendar_event, ask_clarification, end_conversation.

All write operations. The AI could create things in your schedule, but couldn't tell you what was already there.

The Solution: An 8th Tool

I added query_agenda(startDate, endDate) — a read tool.

When you ask "What's on my plate this week?", the LLM:

Parses your intent and calls query_agenda with the right date range
A Supabase RPC function queries three tables: privat.tasks, privat.calendar_events, and privat.memos
Returns structured data: tasks with due dates, events with times, memos with timestamps

But raw data isn't useful as a voice response. Nobody wants to hear "Task ID 47, title grocery shopping, due date 2026-03-24T10:00:00Z."

The 2nd LLM Call

This is where it gets interesting. The orchestrator makes a second LLM call — taking the raw agenda data and generating a natural vocal summary:

"Tomorrow you have three things. In the morning, grocery shopping. At 2pm, a dentist appointment. And you still have that memo about calling the insurance company."

Natural. Conversational. Adapted for voice.

The Architecture Change That Surprised Me

The FunctionExecutor — the component that runs tools — was synchronous and had no database access. It only returned instructions that the frontend would execute.

For query_agenda, the backend needed to query Supabase directly. So the FunctionExecutor became async, with access to the Supabase client and userId.

// Before: synchronous, no DB access
executeTool(name: string, args: object): ToolResult

// After: async with DB context
async executeTool(
  name: string, 
  args: object, 
  supabase: SupabaseClient, 
  userId: string
): Promise<ToolResult>

This opened the door for future read tools — the AI can now query anything server-side.

The RPC Function

The Supabase RPC crosses three tables in a single query:

CREATE OR REPLACE FUNCTION get_user_agenda(
  p_user_id UUID,
  p_start_date TIMESTAMPTZ,
  p_end_date TIMESTAMPTZ
) RETURNS JSON AS $$
  SELECT json_build_object(
    'tasks', (SELECT json_agg(...) FROM privat.tasks WHERE ...),
    'events', (SELECT json_agg(...) FROM privat.calendar_events WHERE ...),
    'memos', (SELECT json_agg(...) FROM privat.memos WHERE ...)
  );
$$ LANGUAGE sql SECURITY INVOKER;

Using SECURITY INVOKER means RLS policies are enforced — users only see their own data, even when the backend calls this function.

Frontend: No PendingCreation

Every other tool creates a PendingCreation — a preview the user validates before it's saved to the database. But query_agenda doesn't create anything. The frontend just needs to handle the agenda_queried action by... doing nothing. The voice response is the result.

The Bigger Picture

This changes the nature of the voice assistant fundamentally. Before, it was an input device — you talk, it writes. Now it's a conversational partner — you ask, it answers.

"What do I have this week?" → vocal summary
"Create a task: buy flowers for Friday" → creates task
"Actually, what else is on Friday?" → checks and responds
"Add a reminder for 5pm" → creates event

The conversation flows naturally because the AI can both read and write.

700+ commits. Solo dev. Production in 5 days.

If you're building voice AI features, the key insight is: read tools change everything. An AI that can only write feels like a command interface. An AI that can read and write feels like an assistant.

I Built a Blog with 31 Articles and AI-Generated Cover Images in One Day — Here's How

TAMSIV — Wed, 18 Mar 2026 09:06:30 +0000

I'm building TAMSIV, a voice-powered task manager, solo. After 670+ commits over 6 months, I had a landing page, a web dashboard, and... zero blog. Google didn't know I existed.

So I decided to fix that. In one day.

The Problem

My site had no indexable content. No articles. No FAQ. No user guide worth the name. Every piece of marketing I'd done (50+ posts across Discord, LinkedIn, Facebook, dev.to) lived on other people's platforms. Nothing on my own domain.

The Solution: 31 Articles, AI Cover Images, 6 Languages

Here's what I built:

Blog Architecture (Next.js)

The blog lives in src/lib/blog.ts — all content is inline HTML, no database. Each article has metadata (title, slug, date, tag, excerpt, cover image) and content in HTML.

// blog.ts structure
export const articles: BlogArticle[] = [
  {
    slug: 'voice-pipeline-architecture',
    tag: 'Engineering',
    image: '/blog/voice-pipeline.png',
    content: {
      fr: { title: '...', excerpt: '...', body: '...' },
      en: { title: '...', excerpt: '...', body: '...' },
      // + de, es, it, pt
    }
  }
]

The listing page uses a Hero (latest article, full width) + Grid (2 columns) layout. Each article gets its own page with generateStaticParams for SSG.

AI-Generated Cover Images (Gemini 2.5 Flash)

Every article has a cinematic cover image generated by Gemini 2.5 Flash Image via OpenRouter:

POST https://openrouter.ai/api/v1/chat/completions
Model: google/gemini-2.5-flash-image

The prompt formula:

Subject: Description of the article topic
Style: Photorealistic, cinematic, shallow depth of field
Mood: Dark background (#101922), blue/cyan accent lighting
Constraint: NEVER include text in the image

The result? Images that look like they belong in a tech magazine editorial, not a solo dev's side project.

SEO Audit

While I was at it, I ran a full SEO audit:

JSON-LD structured data (SoftwareApplication + Organization)
OpenGraph + Twitter cards for every page
Meta descriptions per page and per article
Sitemap auto-generated (listing + individual articles)
Fixed OG image 404 that had been broken since launch
Added x-default hreflang for international SEO

User Guide Overhaul

The existing guide was a single page. I split it into sub-pages:

Voice assistant guide
Folders & organization guide
Gamification guide
FAQ (expanded from 6 to 18 questions)

Other Stuff That Shipped

Since I was in "ship everything" mode:

In-app updates via Google Play (flexible update flow)
Admin dashboard rebuilt from scratch: 5 tabs (stats, services, infrastructure, logs, credits)
Infrastructure monitoring: real-time Supabase, Railway, and Vercel metrics
API credit tracking: OpenRouter, Deepgram, Runware, OpenAI usage dashboards

The Question

Is launching a blog with 31 articles at once a good idea? The SEO argument says yes — Google rewards content-rich domains. The UX argument says maybe not — who reads 31 articles from a brand they've never heard of?

My bet: the articles aren't for reading today. They're for Google to index, for people to find when they search "voice task manager" or "AI productivity app" six months from now. They're planting seeds.

670 commits in. The site is becoming a content hub. The app is becoming a product.

Links:

Blog: tamsiv.com/en/blog
Previous article: How I Built a Referral System in React Native in One Day

What's your approach to blogging for side projects? One article at a time, or go all-in from day one?

How I Built a Full Referral System in React Native in One Day (Deep Links, Stacking Rewards, Push Notifications)

TAMSIV — Tue, 17 Mar 2026 09:03:38 +0000

Yesterday I spent 8 hours building something that has nothing to do with my product's core features. No new UI. No bug fix. No optimization. A referral system.

I'm building TAMSIV, a voice-powered task manager for Android. Solo dev, 660+ commits, 6 months in. I have 12 alpha testers on the Play Store and I need that number to grow — organically.

So I built the full referral loop. Here's how it works, what I learned, and the gotchas you'll hit if you try this in React Native.

The concept

Simple: every user gets a unique referral code. Share it. When someone signs up with it, both get 1 free month of Pro. And it stacks — 10 referrals = 10 months free, queued one after another.

The 3 capture sources (this is where it gets tricky)

The hardest part isn't generating codes. It's capturing them reliably across all the ways someone might arrive at your app.

1. Deep links via the website

When someone visits tamsiv.com/invite/CODE, Next.js redirects to the Play Store with the referral code embedded:

// next.config.ts
async redirects() {
  return [{
    source: '/invite/:code',
    destination: 'https://play.google.com/store/apps/details?id=com.tamsiv&referrer=:code',
    permanent: false,
  }]
}

2. Android App Links (direct open)

If the app is already installed, tamsiv://invite/CODE opens it directly. This requires:

AndroidManifest.xml:

<intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="https" android:host="tamsiv.com"
        android:pathPrefix="/invite" />
</intent-filter>

Plus an assetlinks.json on your website for verification:

[{
  "relation": ["delegate_permission/common.handle_all_urls"],
  "target": {
    "namespace": "android_app",
    "package_name": "com.tamsiv",
    "sha256_cert_fingerprints": ["YOUR_SHA256"]
  }
}]

React Navigation linking config:

const linking = {
  prefixes: ['tamsiv://', 'https://tamsiv.com'],
  config: {
    screens: {
      Signup: 'invite/:code',
    },
  },
};

3. Play Store Install Referrer

This is the sneaky-good one. When someone clicks a Play Store link with &referrer=CODE, Android stores that referrer string. Even if they install the app 3 days later, you can still read it.

npm install react-native-play-install-referrer

import { getInstallReferrer } from 'react-native-play-install-referrer';

const referrer = await getInstallReferrer();
// referrer.installReferrer contains your code

This covers the "click link → browse Play Store → install later → open" flow that deep links can't handle.

Stacking rewards

Most referral systems give you one reward and that's it. I wanted rewards to accumulate. Each referral adds 30 days of Pro, queued after the previous one expires.

The logic: when a referral is validated, the backend checks if the user already has an active reward. If yes, the new reward's start date = previous reward's end date. If no, it starts now.

This required rethinking my subscription logic — RevenueCat handles paid subscriptions, but free months from referrals are managed separately in Supabase.

Push notifications in 6 languages

When someone uses your referral code, you get a push notification. In your language. Because TAMSIV supports 6 languages (FR, EN, DE, ES, IT, PT), the backend checks the referrer's language preference before sending via FCM:

// Backend endpoint: POST /api/push/referral-reward
const referrerProfile = await getUserProfile(referrerId);
const lang = referrerProfile.language || 'en';
const messages = {
  fr: `${referredName} a utilisé votre code ! 1 mois Pro offert 🎉`,
  en: `${referredName} used your code! 1 free month of Pro 🎉`,
  // ... 4 more languages
};
await sendPushNotification(referrerProfile.fcm_token, messages[lang]);

The Invite tab

The frontend has a dedicated Invite section in the Social screen: your unique code, a native share button, referral stats (total invites, pending, rewarded), and reward history. All managed by a ReferralService singleton with caching.

By the numbers

22 files changed across backend, frontend, website, and Android manifest
1,324 lines added
1 day of focused work
6 languages supported
3 capture sources for maximum coverage

What I learned

Android App Links verification is fragile. The assetlinks.json must be served at /.well-known/assetlinks.json with the exact SHA256 of your signing key. Miss one character and it silently fails.
Play Store Install Referrer is underrated. Most tutorials skip it, but it's the only way to capture referrals through delayed installs.
Reward stacking adds real complexity. A simple "give 1 month free" is easy. Queuing multiple rewards requires tracking start dates, end dates, and the relationship between RevenueCat subscriptions and your own reward system.
i18n multiplies everything. 1 push notification message × 6 languages × 2 recipients (referrer + referred) = 12 translation keys. For every user-facing string.

Will it work?

Honestly? No idea. The code is ready, the circuit is complete. Now it's up to the users.

But here's the thing — building the referral system forced me to think about growth for the first time. After 660 commits of pure product work, spending one day on distribution felt uncomfortable. But necessary.

If you're a solo dev reading this: don't wait as long as I did. Build the growth loop early.

TAMSIV is a voice-powered task manager for Android. Try it on the Play Store or visit tamsiv.com.

Follow the journey: GitHub commits in public | Discord

I Built a Voice-Powered Task Manager with AI in 650 Commits — Here's What I Learned

TAMSIV — Mon, 16 Mar 2026 13:26:02 +0000

Five months ago, I had a simple problem: my family of four couldn't keep track of groceries, appointments, and who's picking up the kids. Post-it notes on the fridge weren't cutting it.

So I built TAMSIV — a voice-powered task and memo manager with AI. You speak, the AI understands, and everything gets organized automatically. No typing, no tapping through forms. Just talk.

650 commits later, here's what I learned building it solo.

The Stack

Frontend: React Native 0.81 + TypeScript (New Architecture enabled)
Backend: Node.js/Express with WebSocket for real-time voice streaming
Database: Supabase (PostgreSQL) with Row Level Security
AI: OpenRouter (400+ LLM models), Deepgram (STT), OpenAI (TTS)
Hosting: Railway (backend) + Vercel (website)

The Voice Pipeline

This is the core of TAMSIV. The flow looks like this:

User speaks → PCM audio chunks via WebSocket
  → Deepgram (real-time STT with VAD)
  → LLM via OpenRouter (context-aware)
  → Function calling (create_task, create_memo, create_event)
  → OpenAI TTS → Audio response back to user

The tricky part? Voice Activity Detection (VAD). You need to know when the user stopped talking before you send the audio to the LLM. Too early and you cut them off. Too late and the app feels sluggish.

I ended up with a dual-mode system:

Push-to-talk: User controls when they start/stop. More reliable.
VAD mode: Deepgram detects silence automatically. More natural but harder to get right.

What the AI Actually Does

The LLM doesn't just transcribe — it understands intent. Say:

"Remind me to buy milk tomorrow at 5pm, it's urgent"

The AI extracts:

Type: Task
Title: "Buy milk"
Due date: Tomorrow 5pm
Priority: High
Category: Auto-detected based on context

It uses function calling to create structured data, not free text. The backend returns a function_result message, and the frontend handles the actual database operations.

The Hardest Bugs

1. LLMs Can't Do Dates

Ask an LLM "what's next Tuesday?" and you'll get wrong answers 30% of the time. My fix: inject a date lookup table into the system prompt with the current date, day of week, and the next 14 days mapped out. Accuracy went from ~70% to ~99%.

2. The Singleton Cache Leak

After logout, the next user would see the previous user's data. The singleton services (ConversationService, ContentCacheService) kept stale data in memory. Fix: proper cleanup on auth state change.

3. Six Hooks DDoSing Supabase

Six different React hooks were all calling getGroups() independently on mount. That's 6 concurrent identical requests per screen load. Fix: centralize in a GroupsContext with a single fetch.

Features That Surprised Me

Gamification works. I added levels, badges, streaks, and daily challenges almost as an afterthought. Turns out, getting a "5-day streak!" notification makes you actually want to use the app. 12 levels, 5 database tables, full schema — overkill? Maybe. But engagement went up.

Hierarchical folders are underrated. Most task apps give you flat lists or one level of categories. TAMSIV supports unlimited depth: Work > Project Alpha > Sprint 3 > Backend. It sounds simple but the recursive navigation was a real challenge in React Native.

AI-generated images add personality. I integrated Runware (FLUX.1) for automatic image generation on tasks and memos. But the real trick: a LLM first analyzes your content and generates an optimized prompt before sending it to the image model. Way better results than raw text.

The Numbers

650+ commits in 5 months (solo dev)
6 languages (FR, EN, DE, ES, IT, PT)
400+ AI models available via OpenRouter
12 gamification levels
Real-time collaboration with groups, assignments, comments, reactions
3 voice modes: Standard, Live Streaming, Push-to-talk

What's Next

TAMSIV is currently in closed alpha on Google Play with 12 testers. Production launch is planned for late March 2026.

If you're interested in:

Testing the app (Android)
The technical architecture
How I handle voice streaming in React Native
Supabase RLS patterns for multi-tenant apps

Drop a comment or check out tamsiv.com.

Building in public, one commit at a time. Follow along for more technical deep dives.