By CrushEdge · crushedge.com
TL;DR — FamilyChat is a stripped-down, child-friendly Android messenger that pairs devices with a QR code (no email, no phone number, no account), works offline, and squeezes in just enough features to actually replace the chaotic family group chat. Push-to-talk voice, pinch-to-zoom photos, reply-to-any-message, parent-only delete, and a big red “reset everything” button if things ever get weird. That’s basically the whole pitch.
If you’ve ever stood at the bottom of a staircase yelling “DINNER!” three times in a row while your kid is buried in a Family-Link-locked tablet two floors up — congratulations, you are exactly the person we built this for. Pull up a chair. Let me tell you the story.
The dinner that went cold (a true story, lightly edited)
It was a Tuesday. Curry was on the table. Steam still curling up. The whole family chat had pinged “🍛 dinner!” twenty minutes ago. Everyone showed up except one — the small human upstairs, headphones on, watching some YouTuber narrate Minecraft like it’s a Premier League match.
We tried everything. WhatsApp message? Couldn’t install on a Family-Link-managed tablet without jumping through about six hoops. Google Chat? Sent. Read? No. Phone call? The tablet doesn’t have a SIM. Shouting? See above re: headphones.
By the time we hauled ourselves up the stairs and physically pried the kid off the couch, the curry was lukewarm and the rice had gone weirdly tacky. Which, if you’ve ever had tacky rice, you know is a sin punishable by Indonesian grandmothers across at least three generations.
That night, after everyone had gone to bed, I sat down with a stale cup of coffee and asked the most dangerous question a developer can ask:
“How hard could it be?”
Spoiler: harder than it looks, easier than it should be, and surprisingly fun. FamilyChat is what came out the other end.
Why every messenger we tried let us down
We didn’t want to build another chat app. The world has plenty. But every single one of them failed at least one of the four things we cared about. Let me run you through the gauntlet, because I’m guessing you’ve been there too.
WhatsApp. Brilliant app. Genuinely. But try installing it on a kid’s Family-Link-managed device. Phone-number signup. SMS verification. Some devices don’t even have a number. And even if you wrestle it on, the parental controls layer fights you. Plus do you really want your seven-year-old in the same app where Auntie Sue is forwarding chain messages about lemons curing things? No. You do not.
Telegram. Same phone-number wall. Plus the UI has, charitably, a lot going on. Stickers. Channels. Bots. Secret chats. Folders. It’s a Swiss Army messenger and our kid just needs the little blade.
Google Chat / Messages. It works. Sometimes. The notification reliability on a Family Link tablet is, how do I put this politely, vibes-based. Sometimes the message arrives. Sometimes it shows up forty minutes later in a sad little batch. Sometimes never. Curry-cooling levels of unreliable.
Discord. Hard no for under-13s, age policies aside, the UI is built for raid nights, not “remember to brush your teeth.”
Walkie-talkie apps. Closer to the vibe! Push the button, talk, done. But most of them require accounts, push voice through some ad-supported relay, or simply die in the background after Family Link tightens the screws.
So we made a list. A short, grumpy list:
- No accounts. None. Not even an anonymous one the kid has to remember.
- Reliable. If a message is sent, it lands. Eventually if the network is bad, instantly if it’s good.
- Offline-first. A flaky Wi-Fi router shouldn’t lose a single message.
- Child-friendly. Big buttons, fewer choices, can’t accidentally nuke anything.
- Parent-friendly. A real text input, an “attention” button for emergencies, and the ability to clean up if needed.
- Walkie-talkie energy. Hold a button, talk, release, sent.
- Private. Nobody’s harvesting our family’s chat for ad targeting. Ever.
Most of those things exist in some app. None of them existed in one app. So here we are.
What FamilyChat actually is, in one breath
FamilyChat is an Android 8+ app that pairs two or more devices in your household with a QR code, gives each device a friendly name and an emoji avatar, and lets them text, send pictures, hold-to-talk voice notes, fire off “hey look at this” attention pings, and tap one-tap quick replies — all without an account, an email, a phone number, or a single sign-up form.
The tagline we kept coming back to: WhatsApp reliability + walkie-talkie simplicity.
It’s offline-first (your phone is the source of truth, not some server in Iowa), multi-family safe (multiple households can use it without ever bumping into each other), and the server keeps your messages for a maximum of 72 hours before auto-deleting them — your full history lives on your device, where it belongs.
That’s the whole pitch. Now let me show you how it actually feels.
The first 30 seconds: pairing devices with a QR code
This is the part I’m most quietly proud of, because it took the longest to get right.
When you install FamilyChat the first time, there’s no signup form. There’s no “enter your email.” There’s no “verify your phone number.” There’s a single, fat, friendly button that asks you one question: are you the parent setting up a new family, or are you joining one?
If you’re the parent, you tap “Create Family.” A QR code appears on your screen. That’s it. That’s the whole setup.
You then walk over to the kid’s tablet (or grandma’s phone, or your partner’s old Pixel that lives in the kitchen drawer for reasons), open FamilyChat there, tap “Join Family,” point the camera at your QR code, and click — they’re in. Their name and emoji avatar pop up on your screen instantly. The chat is live.
I tested this with my mother-in-law over a video call once. She held her phone up to the laptop screen, the laptop was showing a Zoom feed of my phone, which was showing the QR code. It still worked. A QR pairing that survived two layers of video compression. I almost cried.
A small but lovely detail: if the parent ever feels weird about who has the invite, they can pop into Settings and tap “Regenerate invite QR.” The old QR is dead instantly. Everyone already paired stays paired. Anyone you didn’t want? They can’t get in anymore. Done.
There’s no concept of “family code” or “PIN.” There’s no list of email addresses to manage. Pairing is a physical act, like handing someone a house key. We liked that. Kids understand it instantly. Grandparents understand it instantly. Even teenagers, who are constitutionally incapable of admitting anything is easy, understand it instantly.
The chat list: where everything lives
The home screen. Big avatars, a clear last-message preview, unread counts that don’t make you squint.
After setup, the app drops you onto the chat list. There’s a default “Family” group chat with everyone in it, plus one-to-one chats with each member if you want a quieter conversation. Each row shows:
- The chat’s avatar (a fat emoji on a colored circle — kids love this)
- The chat name
- A snippet of the last message
- A timestamp that’s smart enough to say “12:42” today and “Yesterday” yesterday and “Tue” three days ago, because nobody wants to read “Mon Apr 28 14:22 GMT+7” on a chat list
- An unread count badge if there’s anything new
Tap a row, you’re in. There’s also a settings cog up top, and that’s basically the whole navigation. Two screens deep. That’s a hard limit we set early: a kid should never be more than two taps away from sending a message. We held the line.
Inside a chat: the place we spent the most love
A chat view with text, emojis, an image, a voice note, and a quoted reply. Big bubbles, comfy spacing, no clutter.
Open a chat and you get the thing you’d expect — a column of message bubbles, your stuff on the right, everyone else’s on the left, each with the sender’s emoji and name. Timestamps are subtle. Bubbles are big and finger-friendly. Photos show as nice rounded thumbnails inline. Voice notes show as a play button with a little waveform. Nothing fancy. Nothing missing.
But the input area is where the parent/child split kicks in, and this is one of my favorite design decisions in the whole app.
Parent input bar
If the device is registered as a parent, you get the full grown-up keyboard:
- A real text field (up to 2000 characters, send all the cooking instructions you want)
- A big camera button for photos
- A microphone button for push-to-talk
- An “Attention” button — the loud one, the one that overrides Do Not Disturb on the receiver, the one for “WHERE ARE YOU IT’S BEEN AN HOUR”
Child input bar
If the device is registered as a child, the input bar is intentionally simpler:
- The text field is still there (kids can type, we’re not monsters)
- A row of giant quick-action buttons: 👍 OK · 📍 On the way · 📞 Call me
- A Quick Camera button that captures and auto-sends in one tap
- A microphone button
The quick-action buttons are the secret weapon. A six-year-old who can’t yet spell “tomorrow” can still tap “👍 OK” the moment Mom asks “did you brush your teeth?” The reply lands instantly. No typing, no spelling pressure, no friction. We watched a five-year-old use this for the first time and the reaction was just… an immediate “oh, I get it.” That was the moment we knew the app was actually for kids and not just marketed to them.
Quick Camera
Quick Camera deserves its own paragraph because it’s that cute. Tap the camera icon as a child, the camera opens, you press the shutter, the photo is sent. That’s the whole flow. No “review your photo” screen. No caption box. No “send to which chat?” picker. The photo arrives in the family chat the second the shutter clicks. Kids use this to send pictures of their drawings, the dog mid-yawn, a particularly impressive Lego, half a sandwich. It is unhinged content and we love it.
Now let’s talk about the new stuff
PROJECT.md captures the bones — what FamilyChat was designed to do at v1. But the app has grown a few extra arms and legs since then, and they’re the kind of features you only realize you need after you ship and watch real humans use the thing. Here’s what’s new.
1. Reply / quote any message
This one came from a single moment. The family chat had drifted, as family chats do, into three parallel conversations: dinner plans, the cat’s vet appointment, and whether Saturday’s birthday party needed balloons. Someone asked “what time?” and no one knew which thread they meant.
So we added quote-replies. Long-press any message — text, image, voice, attention, quick-action, doesn’t matter — and a little menu pops up with Reply as the first option. Tap it.
A small preview banner slides in just above your input bar. It shows who you’re replying to, a little emoji + name label (“👨 Dad”), and a tidy snippet of what they said (the first ~80 characters, or “📷 Photo” if it was an image, or “🎤 Voice 0:12” if it was a voice note). There’s a tiny X to dismiss it if you change your mind.
You type your reply. Hit send. The message goes out with the quoted block embedded inside its bubble. The recipient sees:
┌────────────────────────────────┐
│ ┃ 👨 Dad │
│ ┃ Saturday's birthday — what │
│ ┃ time? │
│ │
│ 3pm. Bring balloons. │
└────────────────────────────────┘The really good bit: tap the quoted block and the chat scrolls to and highlights the original message. No more “what was that about?” archeology. You see context, tap context, get context. If you’ve used Slack threads or WhatsApp replies you know the feeling. We just made sure it works on voice notes and photos too, which is harder than it sounds — for an image the snippet shows a tiny thumbnail; for a voice clip it shows the duration. Small touches, big quality-of-life win.
You can reply to a reply, by the way. The chain doesn’t keep nesting visually — only one level of quote shows at a time, otherwise the bubbles turn into Russian dolls — but the jump-to-original still works through the chain. You can hop your way back to wherever the conversation started.
2. Delete messages (parents only, multi-select, batch)
I’ll be honest. This feature exists because of a single, very specific kind of accident.
Picture it: you’re a parent, you’re texting your spouse about a birthday surprise for your kid, and your thumb fat-fingers the wrong chat. The surprise message lands in the family group chat. The kid is online. The kid has notifications on. The next 3 seconds are the longest 3 seconds of your week.
We needed an undo button. We made one — but only for parents, because letting kids delete their own “I broke the lamp” confession five seconds after sending it would defeat the entire pedagogical point of having a chat history.
Here’s how it works. As a parent, long-press any message → “Select.” The chat slides into selection mode. Tap any other messages you want to add. A delete icon appears in the top bar with a count (“3 selected”). Tap it, confirm, and poof — they’re gone, on every device in the family, within a second or two.
Under the hood the deletion is propagated through the same channel as a normal message: the parent’s device hits the API, the server marks the messages as deleted, and every other device gets a push notification telling it to remove those IDs from its local database. If a device is offline at the time, the deletion is applied as soon as it next syncs. Nothing is left behind.
A child device sees this happen too — the messages just vanish — but a child can never trigger the deletion. The selection mode is gated server-side as well; even if someone rooted the app and faked the request, the server checks the device’s role before honoring it. Belt, suspenders, and a third belt for good measure.
The first time my partner used this in anger, she texted me “OH MY GOD IT WORKS” with seven exclamation marks. The fact that we built a feature that earns seven exclamation marks tells you everything about what kind of app this is.
3. Push-to-Talk voice messages
This one is the heart of the “walkie-talkie” half of our tagline.
Tap-and-hold the microphone button. A full-screen recording overlay slides up — dark background, a big pulsing red dot, a live waveform that dances along to your voice, a counter ticking up the seconds, and at the bottom in unmissable text: “Slide left to cancel.”
Hold the button, talk. Release, sent. Slide your finger away to the left while still holding, the overlay turns red, you let go, the recording is thrown away. It’s the gesture you already know from WhatsApp and Telegram and Messenger because every modern messenger has converged on this pattern, and we’d be silly to invent a new one.
What’s different is what happens to the audio. We use Opus at 16 kHz mono, ~24 kbps on Android 10 and above (most phones). On older devices we fall back to AAC at the same bitrate. Both are tuned for speech, not music — they sound great for human voice and tiny on the wire. A 30-second voice note is around 90 KB. A full minute is under 200 KB. Your data plan won’t even notice.
The other side gets a voice bubble with a play button, a duration (“0:23”), and a precomputed waveform preview baked into the bubble — so you can see at a glance whether this is a quick “yeah” or a 90-second saga about what happened at school today. Tap to play, tap again to pause. Playback is exclusive — start a new one and the previous one stops, so your phone doesn’t turn into a tiny chaotic radio station.
There’s also an auto-play incoming voice toggle in Settings. Off by default, because nobody wants their phone shouting at them in a meeting. Turn it on while you’re cooking dinner and incoming voice notes will auto-play through the speaker the moment they arrive. With wireless earbuds in and auto-play on, it genuinely does feel like a walkie-talkie. Press to talk, listen to the reply, press to talk again. We tested this on a hike with the kids running ahead — it was the first time the app felt magical instead of just useful.
4. Pinch-to-zoom image viewer
Originally, tapping a photo just opened it full-screen and that was that. Functional, boring, and immediately frustrating the moment somebody sent a photo of, say, a school timetable or a handwritten note or a screenshot of a recipe. You couldn’t read the small text. You’d put your fingers on the screen, try to pinch, and… nothing. Just a flat picture mocking you.
So we made the viewer actually work.
- Pinch to zoom from 1× up to 5×.
- Pan with one finger once you’re zoomed in.
- Double-tap to zoom in to 2.5× instantly, double-tap again to zoom back out.
- Single-tap to close the viewer when you’re at 1× zoom — but a single tap while zoomed in does nothing, so you don’t accidentally exit while panning around someone’s homework.
- Smooth gesture handling that respects boundaries (pan resets when you zoom back to 1×, zoom is clamped so the photo doesn’t disappear into a pixel).
It’s the kind of feature that’s invisible when it works and infuriating when it doesn’t, and we sweated the details. The whole thing is built with Compose’s transform gesture detector and a single graphicsLayer modifier — about a screen of code — but it took us four iterations to get the feel right, especially the zoom-while-panning interaction.
5. Save to gallery
Right next to the close button in the image viewer, there’s a small Save action. Tap it and the photo lands in your phone’s gallery, in a folder called Pictures/FamilyChat. That’s it. Done. It shows up in Google Photos, your default gallery, your file manager, anywhere your gallery normally appears.
We use the modern scoped-storage approach on Android 10 and above — no permission prompt, the system just lets us drop a file in the public Pictures folder. On older devices we ask for the legacy storage permission first, but only the first time. After that you tap and it saves silently. A little “Saved to gallery” toast confirms it.
The use case here is mostly grandma sending the kid a photo of a birthday cake she made, and the kid wanting to keep it as a screensaver. Or the kid sending a drawing and the parent wanting to actually print it. The “I want this picture for keeps” moment. Three taps in WhatsApp, one tap in FamilyChat. We’ll take the small win.
6. Reset Family — the big red nuclear button
Settings has a section called Danger Zone at the bottom, visible only to parent devices. Inside, there’s exactly one button: Reset Family.
This is the “I’m starting over” button. It exists for a few real-world scenarios:
- Your kid moved out for university and you want to retire the family chat without leaving stale data behind.
- You messed up the initial setup (wrong roles, wrong names) and want a clean slate without uninstalling.
- You’re handing the device down to someone else and want every trace of the chat gone.
- Worst case: someone got hold of an invite QR they shouldn’t have, and you want to evict everyone and start fresh.
Tap it once and you get the first confirmation dialog: “This will permanently disconnect all family members and delete all messages. Every device will need to set up again from scratch.” Cancel or Continue.
Tap Continue and you get a second confirmation: “Are you absolutely sure? Offline family members will be kicked out as soon as they reconnect (within 72 hours via notification, or immediately when the app is opened). This action cannot be undone.”
Two confirmations is deliberate. One is too easy to fat-finger. Three would be condescending. Two is the right amount of “we really do mean it.”
When you confirm, the parent device hits the server, the family is wiped, and a special push notification — family_reset — is fanned out to every device that was ever a member. The moment any of those devices receive that push (or open the app and check in), they are immediately bounced back to the setup screen. Local database wiped. Settings wiped. They look like a freshly-installed app. The parent’s own device, which kicked the whole thing off, is the first to reset, while the dialog is still closing.
Offline devices get the same treatment as soon as they come back online. There is no escape route. It’s the cleanest kind of “burn it down” that we could engineer, and we tested it more times than I care to admit. (The audit trail of “RESET FAMILY (test #47)” notifications on my devices is genuinely embarrassing.)
The settings screen
Your profile, family member list, message cleanup, voice playback, and the danger zone if you’re a parent.
Settings is intentionally short. There are only a handful of things you can do here, and we like it that way:
- Profile — your name, role (parent/child), and emoji avatar. The basics.
- Family Members — see everyone in the family with their roles. Parents can remove a member here (e.g. an old phone you don’t use anymore) and regenerate the invite QR.
- Messages — three big buttons: clear messages older than 1 week, older than 1 month, or all. Plus a toggle for auto-delete after 30 days that runs as a daily background job. Off by default — your history is yours.
- Voice messages — the auto-play incoming toggle.
- Danger Zone (parents only) — the Reset Family button described above.
- About — version number. That’s it. No “tell a friend.” No “rate us 5 stars.” We respect you.
Every action that destroys data has a confirmation dialog. Every confirmation dialog has a clear “Cancel” that’s the same size as the destructive button. We do not use those tiny grey “cancel” links that some apps love — we treat the cancel button as a first-class citizen, because the only thing more annoying than data loss is having to fight the UI to avoid data loss.
Built for kids, fair to parents
This is the part of the design philosophy that gets the least attention online but matters the most in practice. The role you pick during setup — parent or child — quietly changes about a dozen things across the app. Not in a “child mode is locked down and miserable” way. In a “the right buttons are bigger and the wrong buttons are gone” way.
For kids:
- Quick action buttons are bigger than the text input. The path of least resistance is to tap a preset reply, not to type one.
- Quick Camera is one tap. Photo, send, done. No edit screen, no caption box, no “are you sure” prompt.
- The microphone is right there. Hold, talk, release. No setup, no permission dance after the first time.
- They can read the chat history just like anyone else. They can scroll back, reply, quote, zoom photos. They are not second-class citizens in their own family chat.
- They cannot delete messages. They cannot reset the family. They cannot remove members. The destructive stuff is gone from their UI entirely — not greyed out, not hidden behind a “you don’t have permission” toast, just not there. Cleaner that way.
For parents:
- Full text input, attention button, member management, message cleanup, the reset button, all of it.
- A snackbar pops up if something goes wrong (network, server, permissions) instead of a popup that interrupts. Quiet failures, loud successes.
- Notifications are full-fidelity — actual sender name, actual snippet, actual reply-from-notification quick actions if your Android version supports them.
The split happens at a single setting: the role you picked during pairing. You can’t change it from inside the app, on purpose — it’s not meant to be toggled; it’s meant to be set once and respected. If you really need to change a role, you reset the family and start over. Nuclear, yes. Foolproof, also yes.
Privacy, in plain English
This is the section I want every parent reading this to actually read, because it’s the part most apps gloss over and we want to be different.
There is no account. We don’t have your email. We don’t have your phone number. We don’t have a password we could lose to a breach. The only thing that identifies your device to our server is a random UUID that the app generates on first launch, plus a long random auth token. Neither of those things is tied to you in any meaningful way. If you wipe the app, that identity is gone forever. Reinstall? You’re a brand new device to us.
Your messages don’t live on our server. They pass through it, briefly, on their way from one of your devices to another. We hold them just long enough to make sure every device in your family has received them. After that — and at a hard maximum of 72 hours, no exceptions — they are deleted by an automatic cleanup job. Forever. Unrecoverable. Our server is a relay, not an archive.
Your full chat history lives on your device. This is on purpose. Your phone is the source of truth. You can scroll back as far as you want, you can keep five years of family memories, you can prune by date, you can wipe everything in one tap. We never touch any of it. We don’t even have a copy.
Your family is isolated. Every API request is scoped server-side to the family the device belongs to. There is no API call — not one — that lets a device read or write data belonging to a different family. It’s enforced at the database query level, not just at the application level. Even in the worst-case bug scenario, families cannot leak into each other.
No ads. No tracking. No analytics SDKs. Look, we get why some apps need them. We didn’t want them. There’s no Facebook SDK, no Google Analytics, no Mixpanel, no Amplitude, no Segment. The only third-party service the app talks to is Firebase Cloud Messaging, and that’s because it’s the only reliable way to deliver a push notification on Android. FCM sees that a push happened, not what was in it.
Encryption. All traffic between your device and our server is HTTPS, full stop. The next big roadmap item is end-to-end encryption — meaning even we, in the seventy-two-hour window your message is on our server, won’t be able to read it. That’s planned and it’s coming. If that’s a dealbreaker for you, wait for the version that ships it. We’ll be loud about it when it lands.
Battery and data: built to be a good roommate
A messenger that drains your battery or chews through your data plan is a messenger you uninstall. We thought about this a lot.
Image messages are compressed to WebP at ~80% quality, max dimension 1280px, and capped at 500KB. Most photos come out at 50–150KB. Thumbnails are an extra 5–15KB. You’d have to send a thousand photos to use 100MB of data. (Please do not send a thousand photos.)
Voice messages are tuned for speech, not music. Opus at 24kbps means a one-minute voice note is under 200KB. A full hour of voice notes — which would be psychotic, but bear with me — is about 11MB.
Background sync runs through Android’s WorkManager, which is the OS-blessed way to schedule periodic work. It batches with other apps, defers to the system on battery saver, and survives Family Link’s aggressive background restrictions because WorkManager is the system. The app does almost nothing in the background unless there’s actually something to do.
FCM pushes are high-priority data messages — they wake the app just long enough to fetch new content and post a notification, then go back to sleep. We don’t keep persistent connections open. We don’t poll. The phone is asleep until something actually happens.
The result is an app that, on a normal family’s normal day, is essentially invisible to your battery stats. We checked. It’s well below “Google Maps that one time you used it for fifteen minutes.”
Things we deliberately left out
A short, opinionated list of features we said no to. Each one was a real conversation. Each one was a hard call. Each one made the app better by not being there.
- Read receipts. No little blue ticks. You will never have to wonder why your kid read your message at 4:32pm and didn’t reply until 5:11pm. They were doing kid things. Let them.
- Typing indicators. The “…” bubble of doom. Adds latency, anxiety, and a constant network ping for almost no value. Skip.
- Stories / status updates. This is a chat app. Not a feed. Your family chat is not a content platform.
- Stickers store. Emojis are fine. Custom packs are not why you’re here.
- AI assistants. No, your messenger does not need a chatbot. It really doesn’t.
- Group calls / video calls. Use literally any other app for that. We don’t want to be a half-broken video calling app.
- Public profiles. There is no profile to view. There’s just you, your name, and an emoji.
- Channels / broadcasts / megagroups. This is a family messenger. The largest family realistically is, what, a dozen people? We optimized for that.
- Self-destructing messages. The whole server is self-destructing on a 72-hour timer. Fine-grained per-message TTLs would be a pile of complexity for a problem your “delete this message” button already solves.
We will probably get pushback on at least three of these. That’s fine. There are plenty of apps that do all of the above. We’re trying to be the one that doesn’t.
Who FamilyChat is for
If any of these sound like you, you’re our person:
- A parent with a kid on a Family-Link-managed Android tablet who can’t easily install adult messengers.
- A multi-device household where the kitchen Pixel, the kid’s tablet, and your phone all need to talk to each other reliably.
- Grandparents who’d love to be included in the family chat but get lost in WhatsApp’s settings menu.
- Anyone who’s looked at their phone’s home screen and thought “why are there four messengers and none of them work consistently with my own family?”
- Privacy-conscious parents who’d rather not hand a Meta product to a seven-year-old.
- People who like apps that do one thing and do it well.
If none of those sound like you, that’s okay too. We didn’t build it for everyone. We built it for the curry-going-cold crowd. Welcome.
What’s coming next
Just one item on the roadmap right now, because we want to land it well rather than scatter our attention:
- End-to-end encryption. The next big release. Your messages will be encrypted on your device, decrypted only on the recipient’s device, and pass through our server as opaque blobs we couldn’t read even if we wanted to. We’ll write a proper post about it when it ships.
After that we’ll see what the people who actually use the app ask for. We don’t have a five-year roadmap. We have a “ship it, listen, iterate” attitude. So far that’s served us well.
FAQ — quick answers for the skim-readers
Is it free? Yes. Free to download, free to use, no tier, no premium, no “pro” version. We are not running a SaaS here.
Does my kid need an account? No. Nobody needs an account. There is no account system at all. Pairing happens by scanning a QR code on the parent’s screen.
Will it work on a Family-Link-managed tablet? Yes. That was literally the design constraint. No phone number required, no Play Family approval workflow, plain old Android app permissions.
What happens if I lose my phone? Your local chat history is gone with the device. Pair the new phone with a fresh QR (the parent regenerates it) and you’re back in the family chat. Past messages from before that point won’t reappear, but the family is intact.
Can I use it on more than one device? Yes. Each device is its own member, even if it belongs to the same person. Lots of households have a “kitchen tablet” account and a “my phone” account for the same parent. Totally fine.
How many people can be in a family? We don’t enforce a hard cap, but the app is designed and tested for households of up to ~6 devices. It will probably work fine for more. Probably.
What if the server goes down? Your messages queue up locally in PENDING state and send themselves the moment the server is back. You won’t lose anything. We’ve tested this by, uh, having the server go down a few times. Don’t worry about it.
Is there a desktop version / iOS version? Not yet. Android-only at launch. iOS is a maybe. Desktop is an unlikely.
Is the data really deleted from the server after 72 hours? Yes. There’s an automatic cleanup job that runs every hour. Once your devices have all received a message, it’s eligible to be deleted even before the 72-hour mark. There is no archive.
Where do I report a bug or ask a question? Head over to crushedge.com — the contact info is there. We read everything, we don’t always reply same-day, but we do read it.
Get FamilyChat
Get it on Google Play → FamilyChat
We’re rolling out on Google Play in waves, so depending on your region the listing may take a beat to appear. Hang tight if it’s not up yet — it will be soon. We don’t offer a direct APK download. The Play Store gives you signed builds, automatic updates, and a way to report problems straight to us, and that’s the experience we want every family to have.
If you give it a spin, let us know how it goes. The best stories about FamilyChat have come from real households catching us off-guard with how they use it — the dad who uses Push-To-Talk to tell his teenager dinner’s ready instead of yelling, the grandma who paired her tablet at a Christmas dinner and is still in the family chat eighteen months later, the kid who sends one photo per day of his school lunch and his mom keeps every single one. We love hearing it.
Thanks for reading this far. Go pair some devices. Go let the curry stay hot.
Written by CrushEdge — building small, opinionated apps you can hand to your family. More at crushedge.com.