{"items":[{"id":"cmp07140a000eow4bya5gnf4e","slug":"why-we-built-the-family-calendar-around-a-kitchen-tablet-not-a-phone","title":"Why we built the family calendar around a kitchen tablet, not a phone","excerpt":"Most family apps assume you're on your phone. We started with the kitchen tablet instead—the screen everyone walks past but nobody really uses.","body":"## The screen nobody designs for\n\nWalk into most kitchens and you'll find a tablet propped near the counter. It plays music while someone cooks. It holds a recipe for twenty minutes. Then it sits idle for three hours showing a lock screen or a frozen YouTube video.\n\nWe kept coming back to that idle state. Here's this piece of glass in the exact spot where the family actually crosses paths—the place where someone asks \"What's happening this week?\" or \"Who's picking up groceries?\"—and most apps treat it like a smaller, worse laptop.\n\n## Kiosk mode first\n\nWhen we started building NestBoard, we made an unusual call: design for the always-on kitchen tablet before designing for the phone in your pocket.\n\nThat decision shaped everything. We added kiosk mode so you can pin the tablet to NestBoard and never worry about kids opening other apps. We built a photo slideshow that cycles through family pictures when the screen is idle, so the tablet earns its counter space even when nobody's actively using it. We made the text large enough to read from across the room while you're unloading the dishwasher.\n\nNone of that matters on a phone. But it matters a lot on the device that sits at the center of the kitchen.\n\n## Sync points, not notifications\n\nPhones are good at interrupting you. Tablets are good at being there when you need them.\n\nWe started thinking about \"sync points\"—those moments when the household regroups. Sunday morning before the week starts. Thursday evening when someone realizes we're out of milk. The ten seconds while the coffee brews and you're wondering if anyone has soccer practice today.\n\nThe kitchen tablet is where those moments happen. So we optimized for glanceability: a week view that shows everyone's color-coded schedule at once, medication reminders with checkboxes big enough to tap without reading glasses, a meal plan that lives right next to the pantry inventory.\n\n## The phone is still important\n\nWe're not saying phones don't matter. You need the phone when you're at the grocery store checking the pantry list, or when you're stuck in carpool and someone asks Robin a question by voice.\n\nBut we built the phone app *after* we built the tablet experience, and that order mattered. The mobile app is designed for quick updates and on-the-go access. The tablet is designed for the conversations that happen when everyone's in the same room.\n\n## A different kind of interface\n\nDesigning for an always-on, shared screen meant rethinking a lot of UI conventions. No personal notifications that everyone can see. No assumption that the person looking at the screen is logged in as a specific family member. No tiny buttons optimized for a thumb.\n\nInstead, we built for a household. The screen shows *everyone's* week, *everyone's* chores, the family meal plan. When someone walks up to it, they see the whole picture, not just their own calendar.\n\nThat's what makes it a household OS instead of a personal productivity app. And it only works because we started with the tablet on the counter, not the phone in your pocket.","category":"Design","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfej2v0000twzgnn18lkpa","publishedAt":"2026-05-27T21:06:30.258Z","scheduledFor":"2026-05-20T13:00:00.000Z","createdAt":"2026-05-10T19:56:17.674Z","updatedAt":"2026-05-27T21:06:30.755Z"},{"id":"cmp071ll5000gow4bcm6f998f","slug":"shared-bottles-shared-meds-why-we-changed-how-supplements-work","title":"Shared bottles, shared meds: why we changed how supplements work","excerpt":"Most medication trackers assume one bottle per person. But couples share multivitamins and magnesium all the time—so we rebuilt the model.","body":"## The problem was obvious once we saw it\n\nWe were testing medications with a few early families when someone said, \"My husband and I both take magnesium from the same bottle. Do I really need to log two separate 60-capsule containers?\"\n\nThe short answer was yes, because that's how we'd built it. One person, one medication record, one bottle count. If two people took the same supplement, you duplicated the entry and pretended you had two bottles.\n\nIt felt silly. Because in the real world, couples share. The costco-size vitamin D sits on the counter. Both of you take one each morning. When it's low, one person reorders. That's one bottle serving two schedules.\n\n## How shared bottles actually work now\n\nWe rebuilt the medication model around a parent record—one entry for the physical bottle, with a name, dose count, and expiration date tracked at the household level.\n\nThen each person who takes that medication gets their own schedule attached to the parent. Maybe you take two magnesium capsules before bed. Your partner takes one in the morning. Different times, different doses, same bottle.\n\nWhen either of you logs a dose, NestBoard decrements the shared count. If the bottle started with sixty capsules and you both took one today, it now shows fifty-eight remaining. The math works the way the cabinet works.\n\n## Why this matters more than it sounds\n\nTracking medications is already a chore. If the app makes you do extra work to model something simple—a single shared bottle—you're more likely to skip it entirely or let the log drift out of sync with reality.\n\nWe want the tool to match your household, not the other way around. Some meds are personal. Some are shared. The system should handle both without forcing you to duplicate entries or do mental math every time you log a dose.\n\nIt's a small change in the interface, but it means one less bit of friction between \"I should track this\" and actually doing it. And for families juggling multiple medications, kids' prescriptions, and the daily-vitamin pile, that friction adds up fast.\n\n## One thing we're still watching\n\nShared bottles get complicated when one person pauses their schedule—vacation mode, ran out of refills, doctor said to stop for a while. Right now the parent bottle keeps decrementing as long as *someone* is taking it, which is correct. But we're watching to see if families want a clearer view of who's active on a given medication when the bottle runs low.\n\nIf you're using shared bottles and something feels off, we'd love to hear it. This model is new enough that we're still learning how it behaves in real households.","category":"Behind the scenes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfej8o0001twzgs9jsbz31","publishedAt":"2026-05-19T13:01:34.682Z","scheduledFor":"2026-05-19T13:00:00.000Z","createdAt":"2026-05-10T19:56:40.458Z","updatedAt":"2026-05-19T13:01:34.885Z"},{"id":"cmp071zs1000how4bw3sxa1vd","slug":"importing-recipes-from-any-cooking-site","title":"Importing recipes from any cooking site","excerpt":"Most recipe sites already publish their recipes in machine-readable format. We just read the structured data — no AI guessing required.","body":"## How it actually works\n\nWhen you paste a recipe URL into NestBoard's meal planner, we don't send it to an LLM to \"extract\" the ingredients and steps. We just read the structured data that's already there.\n\nMost major cooking sites — Bon Appétit, NYT Cooking, AllRecipes, individual food blogs running WordPress — embed schema.org/Recipe markup in every recipe page. It's invisible to you, but it's sitting in the HTML: the ingredient list, the instructions, cook time, yield, everything.\n\nWe parse that structured data, pull out the fields we need, and show you the recipe. No round-trip to a language model. No latency. No hallucination risk.\n\n## What works well\n\nFood blogs using plugins like WP Recipe Maker or Tasty Recipes are perfect. The metadata is clean and consistent.\n\nRecipe aggregators like AllRecipes and Food Network work beautifully. They've been publishing schema.org data for years.\n\nEven smaller independent sites often use the same WordPress plugins, so they work just as well as the big names.\n\n## What doesn't work\n\nRestaurant menus don't publish recipe metadata — they're not recipes, they're listings. If you want to save \"pad thai from the place on 5th,\" you'll need to add it manually or ask Robin to help you build a recipe card from a photo.\n\nSome older or minimal food blogs skip the structured data entirely. If the site doesn't have the markup, we can't import it.\n\nAnd sometimes a site will have the schema.org tags but fill them incorrectly — missing units, ingredients buried in the instructions, that kind of thing. We can't fix bad data.\n\n## Why we like this approach\n\nIt's fast. There's no API call to wait on, no token budget to manage.\n\nIt's honest. If the data isn't there, we tell you. We don't try to guess what the recipe might be.\n\nAnd it respects the work that recipe publishers have already done. They've marked up their content in a standard format specifically so tools like ours can use it. We're just reading what they intended to share.\n\nThis is the same philosophy we take with Robin: we're [clear about what it reads and what it doesn't](/blog/what-robin-actually-reads-and-what-it-never-will). We'd rather give you a reliable tool with known boundaries than promise magic and deliver guesswork.\n\nIf you've found a recipe site that should work but doesn't, let us know. We're always refining the parser.","category":"Behind the scenes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejbn0002twzg1yvgh4zk","publishedAt":"2026-05-18T13:01:34.601Z","scheduledFor":"2026-05-18T13:00:00.000Z","createdAt":"2026-05-10T19:56:58.850Z","updatedAt":"2026-05-18T13:01:34.780Z"},{"id":"cmp072yw2000kow4byxa0y68j","slug":"forwarded-emails-to-robin-what-works-and-what-doesnt","title":"Forwarded emails to Robin: what works and what doesn't","excerpt":"We tested dozens of forwarded emails to see what Robin can turn into calendar events. Here's what worked, what didn't, and why some messages still need a human touch.","body":"## The ones that worked\n\nRobin handles straightforward appointment confirmations beautifully. A dental reminder with \"Tuesday, March 12 at 2:30 PM\" becomes a calendar event in seconds. Same with restaurant reservations—OpenTable confirmations include the date, time, and location in a predictable format, and Robin pulls those details cleanly.\n\nSchool announcements surprised us. We forwarded an email about an early dismissal day, and Robin caught the date and created \"School early dismissal - 12:30 PM\" without being asked. It parsed the context from phrases like \"students will be released\" and understood what mattered.\n\nYouth sports schedules work when they're formatted as lists. A soccer league sent a six-game schedule in bullet points, and Robin created six separate events with opponents and field locations. It even handled the phrase \"rain date TBD\" by adding it to the notes field instead of trying to parse a fake date.\n\nDoctor's office reminders are a solid yes. Those auto-generated \"You have an upcoming appointment with Dr. Chen\" emails have consistent structure, and Robin reads them the same way every time.\n\n## The ones that still need help\n\nConversational emails are Robin's weak spot. When a friend writes \"Let's do coffee next Thursday if that works?\" there's no confirmed plan yet. Robin can see the suggestion but won't create an event from a maybe. That's intentional—we don't want your calendar filled with things that haven't been agreed to.\n\nEmbedded images with schedule information don't work. If a swim team coach screenshots a meet schedule and pastes it into an email, Robin can't read it. The information lives in the image, not the text. You'll need to manually add those, or ask the sender for a text version.\n\nLong newsletters with multiple events scattered throughout are hit or miss. Robin might catch the first date it sees, but a PTA digest with twelve upcoming dates buried in paragraphs isn't something it can reliably parse. Too much noise, not enough signal.\n\nAnything that requires interpretation of house rules or family preferences won't work yet. An email that says \"parent volunteers needed for the field trip\" isn't an event for your calendar unless you've signed up for a specific slot.\n\n## Why it matters which emails work\n\nWe're not trying to make Robin read everything. Some messages are better left as messages—things to discuss, not things to auto-schedule. The goal is to catch the stuff that's already decided and formatted clearly enough that a machine can be confident it's reading correctly.\n\nWhen we built forwarding, we looked at [what Robin actually reads (and what it never will)](/blog/what-robin-actually-reads-and-what-it-never-will) and applied the same principles. Clear structure wins. Ambiguity needs a human.\n\nIf you forward something and Robin misses it, that's useful feedback. We're learning which formats matter most to families, and where the gaps are.","category":"Robin","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejqj0007twzgqx1kmql8","publishedAt":"2026-05-17T13:01:34.475Z","scheduledFor":"2026-05-17T13:00:00.000Z","createdAt":"2026-05-10T19:57:44.355Z","updatedAt":"2026-05-17T13:01:34.697Z"},{"id":"cmp07ubc90012o34bie1mjgy8","slug":"on-warm-and-tactile-cream-over-white-serif-over-sans","title":"On warm and tactile: cream over white, serif over sans","excerpt":"Why NestBoard looks the way it does—cream backgrounds, serif type, and five named themes that all resist the urge to feel like productivity software.","body":"## The first choice was cream\n\nPure white feels clinical. It's the color of hospital corridors and spreadsheet cells. We wanted something that felt like paper—not printer paper, but the kind you'd use to write a letter or sketch a grocery list.\n\nSo we started with cream. A warm, off-white that doesn't glare. Paired with ink (a soft black) and terracotta as the accent. The palette became the foundation for everything else.\n\n## Serif, not sans\n\nSource Serif sits at the center of the interface. It's legible at small sizes, but it carries weight—literally. Serifs have feet. They anchor text to the page in a way that sans-serif fonts don't.\n\nHelvetica and its descendants are clean and efficient. They're great for signage and instructions. But a family calendar isn't a sign. It's a living document, something you return to every day. We wanted it to feel more like a kitchen table than a terminal window.\n\nThe serif choice influenced everything downstream. The splash screen. The cards that hold chores and medication reminders. Even the way Robin's responses render—they inherit that same typographic warmth.\n\n## Five themes, one philosophy\n\nWe built five themes around the same principle: resist the urge to look like productivity software.\n\n**Bone-ink** is the default—cream and charcoal with terracotta touches. **Midnight-studio** inverts to a deep blue-black for evening use. **Linen-scandi** softens everything into pale neutrals. **Garden-path** brings in mossy greens. **Sunday-funday** is warmer still, with ochre and rust.\n\nEach one has a name, not a number. We wanted them to feel like moods, not settings.\n\n## Tactile by constraint\n\nThe palette and type system force us to think about hierarchy differently. Without neon highlights or stark contrast, we rely on spacing, weight, and subtle color shifts. A chore card earns its leaderboard badge through layout, not a fluorescent ping.\n\nThis shows up in small ways. The rounded corners on every card. The way completed tasks fade rather than disappear. The gentle shadows that lift interactive elements just slightly off the canvas.\n\nIt's slower to design this way. But it means the app doesn't shout. It doesn't try to gamify your attention or optimize for engagement metrics. It just sits there, ready, like a notebook on the counter.\n\n## Why it matters\n\nDesign choices compound. Choose white, and you're halfway to looking like every SaaS dashboard. Choose Helvetica, and you're signaling efficiency over comfort.\n\nWe chose cream and serif because a household OS should feel like it belongs in a household. Not floating in some cloud, not optimized for quarterly metrics—just present, sturdy, and warm.","category":"Design","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejkm0005twzgk00q3nxk","publishedAt":"2026-05-16T13:01:34.417Z","scheduledFor":"2026-05-16T13:00:00.000Z","createdAt":"2026-05-10T20:19:00.202Z","updatedAt":"2026-05-16T13:01:34.598Z"},{"id":"cmp07ut180014o34bn4so86qt","slug":"why-kid-accounts-work-differently","title":"Why kid accounts work differently","excerpt":"NestBoard has separate flows for adults and children under 13. Here's why that matters for a family app, and how parental consent gates work.","body":"## Two kinds of accounts\n\nWhen you add someone to your NestBoard household, we ask whether they're an adult or a child. It sounds simple, but that choice triggers completely different paths through the app.\n\nAdults get full accounts—email login, password recovery, the ability to join multiple households or start their own. Kids get something lighter: a seat in the household with no email required, managed by the parents who invited them.\n\nThe law draws a bright line at age 13. In the US, COPPA (the Children's Online Privacy Protection Act) requires verifiable parental consent before we can collect personal information from anyone younger. That includes email addresses, profile photos, or persistent identifiers tied to a child.\n\n## The under-13 flow\n\nIf you're adding a child under 13, NestBoard never asks them to create an account. They don't get a login email. They don't set a password. Instead, the parent who invites them provides consent, and the child gets a household-only profile.\n\nThat child can see shared calendar events, complete chores, check medication reminders, and interact with family meal plans—all the collaborative parts of NestBoard. But their data lives inside the household, managed by the parents who control the workspace.\n\nWhen a child turns 13, we don't automatically flip a switch. Parents can choose to invite them to create a full account, or keep the managed profile as-is. Some families prefer that lighter setup even for teenagers.\n\n## Why this matters for calendar apps\n\nMost productivity tools are built for individuals or coworkers. Adding kids is an afterthought, if it's possible at all. But a household calendar exists specifically to coordinate people of different ages—school pickups, pediatrician appointments, whose turn it is to feed the dog.\n\nIf we treated every family member as a standard user, we'd either exclude young kids entirely or collect data we shouldn't. The two-tier system lets the whole household show up in the app without putting seven-year-olds through email verification or handing their information to third parties.\n\nIt also means parents stay in control. You decide what your child sees, when they graduate to a full account, and whether they interact with features like Robin. (We apply the same care to what Robin can access across the household—more on that [here](/blog/what-robin-actually-reads-and-what-it-never-will).)\n\n## No email, no problem\n\nThe no-email kid seat solves a practical headache, too. Most children under 13 don't have email addresses. Creating a burner account just to satisfy an app's signup flow is busywork, and it trains families to treat consent forms as obstacles instead of safeguards.\n\nNestBoard skips that. Add your child's name, confirm you're the parent, and they're in. One less password to remember, one less inbox to monitor, one fewer terms-of-service click-through.\n\nThe regulations exist for good reasons. We built the kid-account flow to respect those reasons without making family coordination harder than it needs to be.","category":"Privacy","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejtg0008twzguq794y6u","publishedAt":"2026-05-15T13:01:34.334Z","scheduledFor":"2026-05-15T13:00:00.000Z","createdAt":"2026-05-10T20:19:23.133Z","updatedAt":"2026-05-15T13:01:34.517Z"},{"id":"cmp07v7rb0016o34bizg2vgkf","slug":"the-pantry-expiry-notification-that-doesnt-nag","title":"The pantry expiry notification that doesn't nag","excerpt":"Most pantry apps remind you daily when something expires. We tried that. It made people ignore the feature entirely. Here's what worked instead.","body":"## One alert, then silence\n\nWhen we started building pantry expiry tracking, we looked at how other apps handle it. Most send a notification three days before something expires, then again two days before, then the day of, then again after it's expired.\n\nWe tried that cadence in early testing. Within a week, three families had turned off pantry notifications completely.\n\nThe problem wasn't the information. It was the repetition. If you saw the alert on Monday and decided to make pasta that week before the box expires, you don't need to see the same alert Tuesday, Wednesday, and Thursday. The notification stops being helpful and starts being a reminder that you haven't dealt with it yet.\n\n## Crossing the threshold once\n\nWe changed the logic. Now you get one notification when an item crosses into the \"expiring soon\" window. That's it. The item stays flagged in your pantry view—you can see it's still expiring—but we don't send another alert unless something changes.\n\nIf you add a new expiring item, you'll get notified about that one. If you mark the pasta as used or update its date, the alert clears. But we won't remind you about the same static fact over and over.\n\nThis matches how you'd actually talk to someone in your house. You'd mention once that the milk is going off soon. You wouldn't walk into the kitchen every morning and repeat it.\n\n## What people actually do\n\nAfter shipping this version, we saw two things change. First, more households left pantry notifications on. Second, when they did get an alert, they acted on it more often—either using the item, updating the date, or removing it from the list.\n\nTurns out a single, timely piece of information is easier to act on than a drip of repeated reminders. The notification becomes a gentle flag rather than a nag, and the pantry view itself holds the persistent context you need.\n\nWe think about this same principle in a lot of places. Robin will surface something once when it's relevant rather than looping back every day. Chore reminders follow a similar pattern. The goal isn't to maximize notification volume—it's to give you the right nudge at the right moment, then get out of the way.","category":"Design","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejwf0009twzgn4o49luw","publishedAt":"2026-05-14T13:01:34.223Z","scheduledFor":"2026-05-14T13:00:00.000Z","createdAt":"2026-05-10T20:19:42.216Z","updatedAt":"2026-05-14T13:01:34.405Z"},{"id":"cmp07vny30017o34b5i8vm1e7","slug":"why-every-household-calendar-should-have-a-vacation-mode","title":"Why every household calendar should have a vacation mode","excerpt":"When you're on vacation, your household software should know to stop buzzing. Here's why it took us a year to ship vacation mode—and what it pauses.","body":"We shipped vacation mode last month. It's a single toggle that tells NestBoard your household is away, and for how long.\n\nWhen it's on, chores stop buzzing. Daily summary emails go quiet. The calendar shows a visual strip across those dates so everyone in the family sees at a glance that you're gone. Robin won't send reminders about routines that don't matter when you're at the beach.\n\nIt sounds simple, but it took us a year to add.\n\n## The problem we kept ignoring\n\nEarly on, we assumed people would just manually snooze things before a trip. Turn off notifications, archive a few chores, maybe add a calendar event called \"VACATION\" in all caps.\n\nBut that's six different interactions spread across the app. And when you're packing sunscreen and printing boarding passes, the last thing you want to do is audit your household software.\n\nMore importantly, it puts the burden on you to remember what to turn off—and then turn back on when you get home. We watched families come back from a week away to a pile of overdue chore notifications and guilt-inducing leaderboard math. That's not calm. That's punishment for taking a break.\n\n## What vacation mode actually does\n\nYou pick a date range. NestBoard pauses chore notifications, hides overdue badges, and skips daily digests. Medication reminders keep running by default—you can override that per bottle if needed—because some things travel with you.\n\nThe calendar shows a single terracotta-colored strip across the dates. It's visible to everyone in the household, including anyone with view-only access. If someone tries to assign a new chore during that window, the app gently suggests picking a different date.\n\nWhen the vacation ends, everything resumes automatically. No overdue pile. The chore rotation picks up where it left off, and the leaderboard pretends those days never happened.\n\n## Why it took a year\n\nWe debated what \"away\" means. Is a long weekend away? What about a work trip where one parent is gone but the household keeps running?\n\nWe also rewrote how reminders and streaks calculate time. Vacation days needed to become a new concept in the database—not just \"ignored days\" but a recognized household state that every feature could check against.\n\nIt's one toggle now. But behind it is a year of deciding what a household calendar should assume about absence, rest, and what it means to actually be off.\n\nWe think it was worth it. Your home routines should bend when you're gone, not break.","category":"Behind the scenes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejzd000atwzgaupragik","publishedAt":"2026-05-13T13:01:41.253Z","scheduledFor":"2026-05-13T13:00:00.000Z","createdAt":"2026-05-10T20:20:03.196Z","updatedAt":"2026-05-13T13:01:41.437Z"},{"id":"cmp07w71b0019o34bockzba82","slug":"subscription-that-doesnt-punish-small-households","title":"Subscription that doesn't punish small households","excerpt":"We priced NestBoard at $10/month for two people, not one. Here's why per-seat pricing would feel wrong for a family tool—and what we left out on purpose.","body":"## Why two seats, not one\n\nMost subscription software charges per person. That makes sense for workplace tools where every employee is a billable resource. But a household isn't a workplace, and families don't scale like companies.\n\nWe set the base subscription at $10/month for two members because that's the smallest committed household we could imagine: a couple, a parent and teen, two roommates sharing a kitchen. Charging $10 for one person would mean a couple pays $20—and that starts to feel like we're taxing togetherness.\n\nA single-person household gets both seats for the same $10. You might use the second for a co-parent who doesn't live with you, or a grandparent who helps with pickups, or just leave it empty. We're fine with that. The price covers the household, not a head count.\n\n## Why kids count (and why that's fair)\n\nAfter two members, each additional seat is $5/month. That includes kids. We've heard the complaint: \"My six-year-old isn't getting $5 of value from this.\"\n\nWe get it. But here's what we couldn't figure out how to build: a system that decided who counts. Is a teenager with a job and a calendar full of shifts worth $5, but a second-grader with library day isn't? What about a twelve-year-old managing their own medication reminders?\n\nThe moment we tried to define \"real user\" versus \"dependent,\" we were making judgments about whose needs matter. So we didn't. Everyone in the shared calendar costs the same to sync, to notify, to store. Everyone gets their own view, their own tasks, their own profile. If they're in your household, they're a member.\n\nAnd honestly, adding a third person—whether that's a kid, a grandparent, or a partner—brings you to $15 total. That's still less than two streaming services.\n\n## What we left out\n\nWe talked about premium tiers. We could have made Robin a paid add-on, or put meal planning behind a higher price, or limited how many pantry items you can track on the base plan.\n\nWe didn't. Every feature in NestBoard is available to everyone. We don't want you doing math about whether the recipe import is worth upgrading, or whether you can afford the medication tracker this month.\n\nThe only thing that changes your price is how many people you add. That's it. No good-better-best grid, no surprise paywalls when you try to set a savings goal or turn on vacation mode.\n\n## A price that doesn't shift\n\nHousehold composition changes. Someone moves out, a new baby arrives, an older relative moves in. We wanted a pricing model that could flex without feeling like a penalty or a gotcha.\n\nYou pay for the people actively using the shared space. When your household grows, the price grows in predictable $5 steps. When someone leaves, you can remove their seat.\n\nWe built NestBoard because we wanted a household tool that didn't feel like enterprise software in disguise. The pricing is part of that. It's not venture-scale growth math—it's just an attempt to charge fairly for something we hope you'll use every day.","category":"Behind the scenes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfek2b000btwzgks9vc0jx","publishedAt":"2026-05-12T13:03:05.925Z","scheduledFor":"2026-05-12T13:00:00.000Z","createdAt":"2026-05-10T20:20:27.936Z","updatedAt":"2026-05-12T13:03:06.104Z"},{"id":"cmp08vggl001vru4blalj2dbg","slug":"carpool-tracking-without-becoming-a-logistics-app","title":"Carpool tracking without becoming a logistics app","excerpt":"Most carpool apps are built for organizers managing twenty kids. Most families just want to know whose turn it is to pick up on Tuesday.","body":"## The carpool problem isn't complexity\n\nWhen we started thinking about carpool tracking, we looked at what was already out there. Lots of apps built for managing rotating schedules across multiple families, with route optimization and automated reminders and color-coded duty rosters.\n\nThey felt like logistics software. Which makes sense if you're coordinating pickups for an entire soccer league. But most families aren't doing that.\n\nMost families have one recurring question: whose turn is it to drive?\n\n## What people actually need\n\nWe talked to parents sharing school runs and after-school pickups. The pattern was consistent. Two to four families, alternating weeks or days. The question wasn't \"how do I build an optimal route\" — it was \"did we drive last Tuesday or was that them?\"\n\nSometimes the carpool is formal. Sometimes it's just two neighbors who take turns without really naming it. Either way, the need is the same: a shared view of who's doing what, and when.\n\nSo we built carpool tracking that lives inside the calendar you're already using.\n\n## How it works in NestBoard\n\nYou mark a calendar event as a carpool. You add the families involved and set a rotation — maybe you alternate weeks, maybe it's every other day.\n\nNestBoard shows whose turn it is. If you want to see the whole week, that's there too. If you need to check who drove last month, you can scroll back.\n\nThat's it. No separate dashboard. No route planner. No push notifications asking you to confirm your availability three days in advance.\n\nThe rotation lives in your shared calendar where everyone can see it. If someone needs to swap, you just edit the event. If the carpool ends, you stop adding it.\n\n## Keeping track without keeping score\n\nOne thing we didn't add: a tally of who's driven more. We thought about it. Some apps do this, surfacing a count so everyone knows the balance is fair.\n\nBut in practice, that scoreboard feeling made things worse. Carpools work because of trust and flexibility. Someone gets sick, someone's car is in the shop, someone has a meeting run late. You cover for each other.\n\nThe goal isn't perfect equity. It's knowing what's happening this week and having a record if you need to check.\n\n## A note, not a system\n\nCarpool tracking in NestBoard isn't a feature you \"set up.\" It's a note you add to the calendar events you already have.\n\nIf your family doesn't carpool, you'll never see it. If you do, it's just there — answering the question without making you learn a new tool or manage a separate workflow.\n\nBecause the problem was never that carpool logistics are complicated. It's that they didn't need to be logistics at all.","category":"Design","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfekb2000etwzgm02e3bf8","publishedAt":"2026-05-11T15:11:25.046Z","scheduledFor":"2026-05-11T13:00:00.000Z","createdAt":"2026-05-10T20:47:53.110Z","updatedAt":"2026-05-11T15:11:25.706Z"},{"id":"cmp08ugbe001sru4b87l6rv8s","slug":"five-families-five-themes-how-sunday-funday-became-a-real-button","title":"Five families, five themes: how Sunday Funday became a real button","excerpt":"We built five visual themes for NestBoard instead of just dark and light mode. Here's why household personality matters more than technical defaults.","body":"## The problem with dark mode\n\nMost apps give you two choices: light or dark. One is supposed to feel clean and modern, the other easy on your eyes at night. But neither one feels like *yours*.\n\nWe started noticing this when we talked to families about how they wanted their household OS to feel. Some people wanted calm and minimal. Others wanted cozy. A few wanted something that felt like a Saturday morning cartoon or a notebook you'd keep on the kitchen counter.\n\nThe technical answer would have been to ship light and dark and move on. But NestBoard lives on your wall-mounted tablet, on your phone when you're at the grocery store, in your partner's hand when they're adding a chore at 10 p.m. It's not just an app you open and close. It's part of the room.\n\n## Five themes, five moods\n\nSo we built five. Each one has a name and a personality.\n\n**Cream & Ink** is our default. Warm, soft, a little analog. It's the one that feels like paper and a good pen.\n\n**Midnight Studio** is dark mode, but moodier. Deep blue-black, not pure black. It's for people who want the interface to recede.\n\n**Scandi Clean** is bright white and sharp. If you want NestBoard to feel like a very organized kitchen drawer, this is it.\n\n**Garden Path** has a soft green accent. It's earthy without being overly botanical. A few people told us it reminded them of their grandmother's recipe box.\n\n**Sunday Funday** is the technicolor one. Bright, saturated, playful. We almost cut it three times because it felt too bold, but every time we showed it to families with younger kids, they lit up.\n\n## Why this matters\n\nThemes aren't about aesthetics for the sake of it. They're about whether a tool feels like it belongs in your house.\n\nWhen you pick a theme in NestBoard, you're not just toggling a display preference. You're setting a tone. You're deciding if this thing on your counter should whisper or hum. If it should blend in or announce itself when your kid runs up to check the chore leaderboard.\n\nWe've seen households switch themes seasonally. We've seen couples compromise: one wanted Midnight Studio, the other wanted Cream & Ink, so they landed on Scandi Clean. We've seen families start with the default and then, two weeks in, switch to Sunday Funday because \"it makes the morning routine less of a fight.\"\n\n## The technical part\n\nEach theme recolors the entire interface: calendar events, chore cards, meal plan rows, Robin's chat bubbles. It's not just swapping a background. Every component has five states now, which made our design system much more complicated and much more worth it.\n\nWe don't let you customize colors yourself. That might sound restrictive, but it's intentional. We wanted five distinct, well-balanced options instead of infinite mediocre ones. Each theme is designed to work in bright kitchens, dim hallways, and everywhere in between.\n\nSome households will never change the default. That's fine. But for the ones who do, it's one of the first moments NestBoard stops feeling like software and starts feeling like theirs.","category":"Behind the scenes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejnj0006twzg56ty99le","publishedAt":"2026-05-11T15:11:25.046Z","scheduledFor":"2026-05-11T13:00:00.000Z","createdAt":"2026-05-10T20:47:06.266Z","updatedAt":"2026-05-11T15:11:25.645Z"},{"id":"cmp08uxbv001tru4bq101azyo","slug":"turning-an-old-tablet-into-a-kitchen-calendar","title":"Turning an old tablet into a kitchen calendar","excerpt":"A practical walkthrough for repurposing an old iPad or Android tablet as an always-on kitchen display with NestBoard's kiosk mode.","body":"## The drawer full of old tablets\n\nMost households have at least one retired tablet sitting in a drawer. The battery doesn't hold a charge like it used to, or someone upgraded and the old one got shuffled aside. It still works fine when plugged in, though.\n\nThat's exactly the situation kiosk mode was built for.\n\n## What kiosk mode does\n\nWhen you enable kiosk mode in NestBoard, the app takes over the entire screen. No home button, no app switching, no notifications from other apps sliding down from the top. Just your family calendar, meal plan, and chores—always visible, always current.\n\nAfter a few minutes of inactivity, it fades into an idle slideshow of your family photos. Tap the screen and you're back to today's schedule. If there's a lightning storm nearby, the screen lights up with a proximity alert so everyone knows to stay inside.\n\nThe point is to turn a screen into a passive household fixture. It's there when you need to check who's picking up the kids or what's for dinner, but it doesn't demand attention otherwise.\n\n## Setting it up\n\nOpen NestBoard on the tablet you want to dedicate. Go to Settings, then toggle on Kiosk Mode. The app will ask for permission to pin itself (on Android) or stay in Guided Access (on iOS). Follow the prompts—this prevents accidental exits when someone taps around.\n\nPlug the tablet into power. You'll want it connected permanently. If you're worried about long-term battery health, some people remove the case to help with heat dissipation, but we've found most modern tablets handle it fine.\n\nNow decide where it lives.\n\n## Counter vs. wall mount\n\nWe've seen both approaches work well, and it comes down to your kitchen layout.\n\nA tablet leaning on a counter stand works if you have the space and want flexibility. You can angle it, move it for cleaning, or relocate it to the dining table when you're planning the week. The downside is that it takes up counter real estate and accumulates crumbs.\n\nWall mounting feels more permanent but gets the tablet out of the way. A cheap adhesive tablet holder or a swing-arm mount near the fridge works. Just make sure the power cable can reach without stretching across a walkway. We've heard from families who run the cable behind a cabinet or along the edge of a backsplash to keep it tidy.\n\nEither way, place it somewhere central—not tucked in a corner where only one person will see it.\n\n## What we've learned\n\nThe families who get the most out of kiosk mode are the ones who stop checking the calendar on their phones. When everyone defaults to the kitchen screen, it becomes the shared source of truth. Someone updates an appointment on their phone during the commute, and by the time they're home it's already on the wall.\n\nAn old tablet doesn't have to be junk. Sometimes it just needs a single job to do.","category":"Field notes","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfek57000ctwzgwv087j75","publishedAt":"2026-05-11T15:11:25.046Z","scheduledFor":"2026-05-11T13:00:00.000Z","createdAt":"2026-05-10T20:47:28.315Z","updatedAt":"2026-05-11T15:11:25.525Z"},{"id":"cmoyn7gf50011mz4b31m4k06a","slug":"what-robin-actually-reads-and-what-it-never-will","title":"What Robin actually reads (and what it never will)","excerpt":"A plain-language tour of Robin's privacy contract. Voice notes, pasted text, dropped images — yes. Inbox crawling, web browsing, training on your data — no.","body":"## What you give Robin\n\nRobin sees what you deliberately hand it. That's the rule.\n\nYou can tap the mic and ask a question out loud. You can paste a block of text — a recipe, a message from school, a complicated insurance form. You can drop in a photo of a pantry shelf or a medicine bottle label. You can forward an email about soccer practice times or a dinner reservation confirmation.\n\nAll of that is fair game. Robin reads it, answers your question or updates the calendar or adds the item to your pantry, and moves on.\n\n## What Robin never touches\n\nRobin doesn't crawl your inbox. It doesn't browse the web on your behalf or scrape your browser history. It doesn't watch what you do in other apps or listen to conversations unless you press the button.\n\nWe don't train our models on your family's data. Your grocery lists and medication schedules and meal-planning notes stay yours. They're not anonymized and folded into someone else's training set. They're not \"aggregated for insights.\" They just sit in your household database, encrypted, doing their job.\n\nThis is a privacy contract. Robin works for you, not the other way around.\n\n## One conversation, not five\n\nRobin lives in two places: a quick-access popup that floats over whatever you're doing, and a standalone screen where you can see the full thread.\n\nBoth surfaces show the same conversation — one shared household thread. That's intentional. When your partner asks Robin about dinner plans and you ask about the grocery list ten minutes later, Robin remembers both. The context doesn't fragment across individual accounts.\n\nSome AI assistants give every person their own private chat. That makes sense for work tools, but it's wrong for a household. Families don't operate in silos. The question \"Did we already buy milk?\" shouldn't require checking three separate threads to find out who last talked to the bot about groceries.\n\nOne conversation means less repetition, less coordination overhead, and fewer moments where you're solving a problem someone else already solved five minutes ago.\n\n## Why this matters\n\nAI assistants are everywhere now, and most of them operate on the assumption that more data is better. More access, more context, more surveillance.\n\nWe think that's backwards for a family tool. The whole point of NestBoard is to reduce the invisible labor of running a household — and that labor includes worrying about what software knows about you.\n\nRobin is powerful because it's constrained. It only knows what you tell it, and it only shares that knowledge within your household. That's enough.","category":"Privacy","ogImage":null,"metaTitle":null,"metaDescription":null,"authorName":null,"authorAvatarUrl":null,"status":"published","generatedBy":"claude","topicId":"cmoxfejem0003twzgfi62knxh","publishedAt":"2026-05-09T17:57:15.107Z","scheduledFor":null,"createdAt":"2026-05-09T17:53:35.201Z","updatedAt":"2026-05-09T17:57:15.229Z"}]}