<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Building in Public by Sineix Labs]]></title><description><![CDATA[Building in Public by Sineix Labs]]></description><link>https://building-aidoo.hashnode.dev</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1593680282896/kNC7E8IR4.png</url><title>Building in Public by Sineix Labs</title><link>https://building-aidoo.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 14 Oct 2026 06:23:28 GMT</lastBuildDate><atom:link href="https://building-aidoo.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Building Aidoo
SHIPATON 2026 · BUILD JOURNAL]]></title><description><![CDATA[From scattered thoughts to a shipped AI productivity assistant.
Aidoo is an AI-powered productivity and planning app built by Sineix Labs. It transforms natural-language instructions, quick notes, bra]]></description><link>https://building-aidoo.hashnode.dev/building-aidoo-shipaton-2026-build-journal</link><guid isPermaLink="true">https://building-aidoo.hashnode.dev/building-aidoo-shipaton-2026-build-journal</guid><category><![CDATA[Flutter]]></category><category><![CDATA[AI]]></category><category><![CDATA[gemini]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[shipaton]]></category><category><![CDATA[RevenueCat]]></category><category><![CDATA[Mobile Development]]></category><category><![CDATA[startup]]></category><dc:creator><![CDATA[Kainat Nadeem]]></dc:creator><pubDate>Wed, 30 Sep 2026 17:29:45 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6abd41250507c7eac1b9d3a3/d0d90d51-eee7-4b19-92e6-12872544a3e0.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>From scattered thoughts to a shipped AI productivity assistant.</p>
<p>Aidoo is an AI-powered productivity and planning app built by <strong>Sineix Labs</strong>. It transforms natural-language instructions, quick notes, brain dumps, and real-time voice conversations into structured, actionable plans.</p>
<p><strong>Status:</strong> Shipped</p>
<p><strong>Product:</strong> Aidoo</p>
<p><strong>Hackathon:</strong> RevenueCat Shipaton 2026</p>
<blockquote>
<p>Published as a retrospective Shipaton 2026 build journal documenting the journey from concept to shipped product.</p>
</blockquote>
<hr />
<h2>The problem we started with</h2>
<p>We kept running into the same problem: our thoughts were everywhere, but our tasks were supposed to be somewhere.</p>
<p>Productivity apps work well once a plan already exists. The problem is that real life rarely arrives as a perfectly organized plan.</p>
<p>Most days start with scattered thoughts, unfinished ideas, reminders, obligations, and conversations. Before a productivity app can help, users are often expected to manually translate all of that into tasks, categories, priorities, dates, and reminders.</p>
<p>We wondered whether that translation step should exist at all.</p>
<p>People do not naturally think in productivity-app fields. They think:</p>
<blockquote>
<p>I need to go to the gym tomorrow morning at 7, finish my report by Friday, and remind me tonight to prepare my clothes.</p>
</blockquote>
<p>That single thought already contains multiple actions, times, priorities, and context.</p>
<p>Why should the user have to translate that thought into a productivity system before the system can help?</p>
<p>That question became Aidoo.</p>
<hr />
<h2>01 · Start with the thought</h2>
<p>Aidoo begins with unstructured human input instead of forcing people to manually construct every task.</p>
<p>Users can:</p>
<ul>
<li><p>Type natural-language instructions</p>
</li>
<li><p>Capture quick notes</p>
</li>
<li><p>Write brain dumps</p>
</li>
<li><p>Speak naturally through real-time voice</p>
</li>
</ul>
<p>Aidoo interprets that input and turns it into structured task information.</p>
<p>The goal is not to make users learn another system.</p>
<p>The goal is to let them begin with the way they already think.</p>
<hr />
<h2>02 · AI that proposes, not silently changes</h2>
<p>One of our most important product decisions was a draft-first workflow.</p>
<p>Aidoo can understand, organize, and propose actions.</p>
<p>It does not silently modify a user's real task system.</p>
<p>The workflow is simple:</p>
<p><strong>Thought → AI Understanding → Structured Draft → Human Review → Action</strong></p>
<p>Before meaningful AI actions are saved, the user can:</p>
<ul>
<li><p>Review</p>
</li>
<li><p>Edit</p>
</li>
<li><p>Accept</p>
</li>
<li><p>Reject</p>
</li>
</ul>
<p>Productivity data is personal.</p>
<p>Giving an AI too much silent control can make the experience feel unpredictable, even when the suggested action is technically correct.</p>
<p>Keeping a person in the loop made the system easier to understand, easier to trust, and safer to use.</p>
<hr />
<h2>03 · Teaching messy language to become structured plans</h2>
<p>Human instructions are rarely perfect.</p>
<p>A user may omit dates, mention multiple tasks in one sentence, use conversational language, or describe something incompletely.</p>
<p>Aidoo uses <strong>Gemini 2.5 Flash</strong> with structured JSON output and schema validation.</p>
<p>The model does not directly operate the database.</p>
<p>Instead, every request follows a controlled workflow:</p>
<pre><code class="language-text">User Input
    ↓
Gemini Understanding
    ↓
Structured Output
    ↓
Validation
    ↓
Editable Draft
    ↓
User Confirmation
    ↓
Fire-store
</code></pre>
<p>This separation helped us make AI actions more predictable.</p>
<p>It also gave us a clear place to handle incomplete or invalid model output before it could affect real user data.</p>
<hr />
<h2>04 · Giving Aidoo a voice</h2>
<p>Aidoo supports real-time voice conversations using Gemini Live and low-latency WebSocket streaming.</p>
<p>The voice assistant can:</p>
<ul>
<li><p>Retrieve tasks</p>
</li>
<li><p>Work with task drafts</p>
</li>
<li><p>Create or adjust task drafts</p>
</li>
<li><p>Complete or delete tasks after verbal confirmation</p>
</li>
</ul>
<p>This became a very different engineering challenge from adding a text prompt.</p>
<p>We had to think about:</p>
<ul>
<li><p>Realtime audio streaming</p>
</li>
<li><p>PCM playback</p>
</li>
<li><p>Interruptions</p>
</li>
<li><p>Conversation state</p>
</li>
<li><p>Tool calling</p>
</li>
<li><p>Latency</p>
</li>
<li><p>Error handling</p>
</li>
<li><p>Reliable app state during active conversations</p>
</li>
</ul>
<p>Voice also changed the interaction model itself.</p>
<p>Conversations move quickly, and users do not always phrase requests like commands.</p>
<p>The assistant therefore needed to remain useful without becoming overconfident about what the user meant.</p>
<hr />
<h2>05 · Turning an AI feature into an actual product</h2>
<p>Aidoo is not simply a chatbot placed on top of a todo list.</p>
<p>The product had to connect the AI experience to the ordinary details that make a planning app useful:</p>
<ul>
<li><p>Tasks and subtasks</p>
</li>
<li><p>Priorities and categories</p>
</li>
<li><p>Recurring tasks</p>
</li>
<li><p>Due dates</p>
</li>
<li><p>Reminders</p>
</li>
<li><p>Quick notes</p>
</li>
<li><p>Brain dumps</p>
</li>
<li><p>Calendar views</p>
</li>
<li><p>Analytics</p>
</li>
<li><p>Completion rates</p>
</li>
<li><p>Category distribution</p>
</li>
<li><p>Daily and weekly streaks</p>
</li>
<li><p>Progress tracking</p>
</li>
<li><p>Authentication</p>
</li>
<li><p>Push notifications</p>
</li>
<li><p>Subscriptions</p>
</li>
</ul>
<p>One of the biggest challenges was connecting all of these pieces into one coherent experience.</p>
<p>A feature could work perfectly in isolation and still feel wrong if it did not fit naturally into the overall planning workflow.</p>
<hr />
<h2>The technology behind it</h2>
<p>Aidoo was built using:</p>
<ul>
<li><p><strong>Flutter &amp; Dart</strong> for the mobile experience</p>
</li>
<li><p><strong>Riverpod</strong> for state management</p>
</li>
<li><p><strong>Firebase Authentication</strong> for account management</p>
</li>
<li><p><strong>Cloud Firestore</strong> for tasks, notes, and user data</p>
</li>
<li><p><strong>Firebase Cloud Functions</strong> for backend logic</p>
</li>
<li><p><strong>Gemini 2.5 Flash</strong> for structured AI planning</p>
</li>
<li><p><strong>Gemini Live</strong> for real-time voice interactions</p>
</li>
<li><p><strong>RevenueCat</strong> for subscriptions and entitlements</p>
</li>
<li><p><strong>OneSignal</strong> and <strong>Apple APNs</strong> for notifications</p>
</li>
</ul>
<hr />
<h2>06 · Building the business layer</h2>
<p>We integrated RevenueCat so subscriptions, entitlements, paywalls, and customer subscription management would not require us to build an entire billing infrastructure ourselves.</p>
<p>Aidoo uses a tiered subscription model:</p>
<h3>Free</h3>
<ul>
<li><p>$0/month</p>
</li>
<li><p>20,000 AI tokens per month</p>
</li>
<li><p>Interactive calendar and tasks</p>
</li>
<li><p>Quick idea-note capture</p>
</li>
<li><p>Firebase cloud backup</p>
</li>
</ul>
<h3>Starter</h3>
<ul>
<li><p>$4.99/month</p>
</li>
<li><p>1,000,000 AI tokens per month</p>
</li>
<li><p>Interactive voice and chat assistant</p>
</li>
<li><p>OneSignal push notifications</p>
</li>
<li><p>Subscription management through the App Store or Play Store</p>
</li>
</ul>
<h3>Pro</h3>
<ul>
<li><p>$9.99/month</p>
</li>
<li><p>2,000,000 AI tokens per month</p>
</li>
<li><p>Unlimited realtime voice sessions</p>
</li>
<li><p>Prioritized Gemini processing</p>
</li>
<li><p>VIP support</p>
</li>
<li><p>RevenueCat Customer Center</p>
</li>
</ul>
<p>One lesson became clear during development:</p>
<p>Monetization is part of the product experience.</p>
<p>It needs to be understandable, aligned with user value, and sustainable, while still leaving a meaningful free experience available to everyone.</p>
<hr />
<h2>07 · Bringing users back at the right moment</h2>
<p>Aidoo's Smart Push Notifications are powered by OneSignal and Apple APNs.</p>
<p>The goal is not notification volume.</p>
<p>The goal is relevance.</p>
<p>When users intentionally create tasks and reminders, Aidoo can bring that information back to their attention at the moment it matters.</p>
<p>This turns tasks from passive information stored in the app into timely actions that help users return to their plans and follow through on what they intended to do.</p>
<hr />
<h2>08 · The privacy decision</h2>
<p>Planning data is personal.</p>
<p>Because of that, privacy had to be part of the product design rather than a final checklist.</p>
<p>Aidoo includes:</p>
<ul>
<li><p>Sign in with Apple</p>
</li>
<li><p>Google OAuth2</p>
</li>
<li><p>Email and password authentication</p>
</li>
<li><p>Password recovery</p>
</li>
<li><p>Account deletion</p>
</li>
<li><p>Deletion of profiles, notes, tasks, and notifications</p>
</li>
<li><p>Considerations for GDPR and Apple Guideline 5.1.1(v)</p>
</li>
</ul>
<p>Personal todo data and voice streams are not used to train public models.</p>
<hr />
<h2>09 · What was harder than expected</h2>
<p>The difficult part was not making one AI interaction work in a demo.</p>
<p>The difficult part was making the complete product reliable enough to ship.</p>
<p>We had to solve for:</p>
<ul>
<li><p>Turning unpredictable human language into reliable structured actions</p>
</li>
<li><p>Keeping AI output constrained and validated</p>
</li>
<li><p>Handling realtime voice streaming and tool calls</p>
</li>
<li><p>Managing state between AI conversations and the user's actual task system</p>
</li>
<li><p>Connecting multiple services without making the product feel fragmented</p>
</li>
<li><p>Building monetization while keeping a meaningful free experience</p>
</li>
<li><p>Preparing for an actual mobile release instead of stopping at a prototype</p>
</li>
</ul>
<p>The final constraint turned out to be the most valuable one:</p>
<p><strong>We had to ship.</strong></p>
<hr />
<h2>From idea to shipped app</h2>
<p>Aidoo's journey looked like this:</p>
<p><strong>Idea → Product Design → AI Architecture → Voice → Data → Notifications → Monetization → Privacy → Testing → App Store → Shipped Product</strong></p>
<p>Aidoo was built to be more than a hackathon AI demo.</p>
<p>We wanted to take the full journey from an idea to a product that could exist beyond a demo environment.</p>
<hr />
<h2>What building Aidoo taught us</h2>
<p>Building Aidoo taught us that an AI product is much more than a model and a prompt.</p>
<p>Structured outputs, validation layers, confirmation flows, and state management become critical when AI can interact with real user data.</p>
<p>A powerful model can generate impressive results, but reliability comes from everything built around it.</p>
<p>We also learned that voice creates an entirely different interaction model.</p>
<p>Latency, interruptions, conversation state, and audio feedback become part of the user experience in ways that do not exist in traditional interfaces.</p>
<p>Most importantly, we learned that trust is a product feature.</p>
<p>Many AI systems try to maximize automation.</p>
<p>Building Aidoo pushed us toward a different philosophy: give the AI enough capability to do the difficult work, but keep the user in control of meaningful decisions.</p>
<blockquote>
<p>AI does not always need more control. Sometimes it needs better boundaries.</p>
</blockquote>
<hr />
<h2>Where Aidoo goes from here</h2>
<p>Aidoo already includes natural-language planning, structured AI drafts, realtime voice, tasks and subtasks, notes and brain dumps, a calendar, reminders, analytics, notifications, and subscriptions.</p>
<p>The next direction is to explore:</p>
<ul>
<li><p>More proactive daily and weekly planning recommendations</p>
</li>
<li><p>Intelligent workload balancing</p>
</li>
<li><p>Context-aware prioritization</p>
</li>
<li><p>Deeper calendar ecosystem integrations</p>
</li>
<li><p>Shared and collaborative planning</p>
</li>
<li><p>More personalized productivity insights</p>
</li>
<li><p>Better continuity between voice and text interactions</p>
</li>
</ul>
<p>Aidoo should not just remember what you need to do.</p>
<p>It should help you figure out how to actually get it done.</p>
<hr />
<h2>We're just getting started</h2>
<p>Shipaton gave us a reason to move quickly, make difficult decisions, and actually ship.</p>
<p>Aidoo is still at the beginning of its journey.</p>
<p>But the product now exists beyond the idea.</p>
<p>It can listen.</p>
<p>It can understand.</p>
<p>It can organize.</p>
<p>It can suggest.</p>
<p>But unlike many AI systems, it does not assume it should make every decision.</p>
<p>The goal was never to replace human judgment.</p>
<p>The goal was to remove the friction between a thought and a plan.</p>
<p>That is the future we are continuing to build toward with Aidoo.</p>
<p><strong>Aidoo</strong> <em>The AI Assistant That Plans for You.</em></p>
<p>Built by Sineix Labs</p>
<p>SHIPATON 2026</p>
<p>Published as a retrospective Shipaton 2026 build journal documenting the journey from concept to shipped product.</p>
<p>Note: This article is a retrospective engineering and product journal documenting the development and launch of Aidoo during RevenueCat Shipaton 2026. It summarizes the project's design decisions, architecture, challenges, and lessons learned after release.</p>
]]></content:encoded></item></channel></rss>