Latest / Logosofia no Dia a Dia / The AC Photo That Taunts You
Transcript
- [Prompt] custom: Let's talk about apps and systems for keeping track of little things to maintain around the house. W | Hosts: corn, herman [Response] Corn: You're scrolling through your phone photos and you find it — a close-up of the AC vent from last July, complete with timestamp. And you stare at it for five seconds because you genuinely cannot remember whether you fixed the thing or just documented it. That photo isn't a solution. It's evidence of a system failure. Herman: Oh, I know exactly that feeling. It's the digital equivalent of writing a note on a scrap of paper and then losing the scrap of paper — except worse, because the photo is right there, taunting you with its uselessness. Corn: Here we are, July, peak cooling season. That one missed AC log? That's the difference between a thirty-dollar filter swap and a five-hundred-dollar emergency call when the coil freezes over on a Saturday. Herman: Which the technician will happily charge you weekend rates for, by the way. Corn: So Daniel sent us this one — he's looking for an app, Android and web, that does something deceptively simple. He wants a single place to log every little thing that needs fixing or maintaining around the house. The AC that isn't reaching the bedroom. The moisture in the window. The dripping faucet you've been ignoring since March. And here's the kicker — he wants photo and video attachments, plus multi-user support, so everyone in the household can see and add to the log. Herman: That sounds reasonable. That sounds like something that should exist in a hundred different flavors. Corn: The average renter in the US moves every two and a half years — that's the twenty twenty-five Census data. Which means your maintenance history has to survive phone upgrades, roommate departures, apartment transitions, and the general entropy of life. Most people's system right now is a camera roll full of orphaned photos and a vague sense of dread. Herman: That photo of the AC vent? It's not just a forgotten fix. It's a symptom of a design gap in how we track the places we live. The tooling hasn't caught up to the need. Corn: Where do we even start with this? Herman: Let's frame what Daniel's actually asking for, because it's more specific than it sounds. This isn't a to-do list problem. Corn: A to-do list says "fix AC." You check it off, it disappears. What Daniel wants is a shared, durable record — something that says "here's what the AC vent looked like on July fifth twenty twenty-six, here's what we did about it, and here's who did it." That record needs to survive for years, not disappear into a completed tasks graveyard. Herman: And the "shared" part is crucial. If you're renting with a roommate or living with a partner, you both need to see the same log, add to it, and trust that the photos you took aren't siloed on someone else's account. The moment one person can't see what the other logged, the system breaks. People stop using it. Corn: Then you're back to the camera roll. Herman: The other piece Daniel flagged that's worth sitting with — he mentioned moisture in the window. That's not a binary "broken or fixed" item. Moisture is something you track over time. Is it getting worse? Is it seasonal? Does it only happen when the temperature drops below a certain point? A single photo doesn't tell you that story. You need a sequence. Corn: Which is why video matters too. A ten-second clip of water dripping shows the drip rate. A plumber can look at that and immediately know whether it's urgent or whether you can wait until fall. A text note saying "faucet drips" tells them nothing. Herman: The requirements are actually three things layered on top of each other. One, home-specific structure — fields for category, priority, urgency. Two, rich media — photos and video, enough to track progression. Three, multi-user access — real shared ownership of the log, not a single login passed around like a dorm room Netflix password. Corn: If you've ever tried to find an app that does all three, you already know where this is heading. Herman: I spent the last week testing everything I could find. The landscape is... let's call it fragmented. Corn: That's generous. Herman: Let's start with the home-specific apps, because those are the ones that promise to solve exactly this problem. HomeZada is probably the best-known name in this space. It offers maintenance scheduling, cost tracking, reminders for seasonal tasks. On paper, it's built for homeowners who want a single dashboard for everything. Herman: As of July twenty twenty-six, HomeZada limits photo attachments to five per maintenance item. If you're tracking that window moisture over six months, five photos is nothing. You'd burn through that in the first two weeks of winter. Herman: Not supported natively in the maintenance log. You can upload video to the document storage section, but it doesn't attach directly to a specific maintenance entry. So you'd have a video of the dripping faucet floating somewhere in your account, disconnected from the actual log entry about the faucet. Corn: The thing that makes the record actually useful — the visual evidence linked to the specific issue — is already compromised. Herman: That's before we get to multi-user. HomeZada does not support native multi-user accounts. A couple renting together cannot both log and view the same moisture issue under their own names. The workaround is sharing a single login. Which means when you look at a photo of the AC vent, you can't tell who took it or who said they'd fix it. Corn: You lose attribution, you lose accountability, and you're back to the "was this fixed or just photographed" problem. Herman: And that's the best-known home maintenance app. Then there's Centriq. Herman: Centriq is primarily a home inventory and insurance documentation platform. Its core value proposition is "take photos of everything you own so you can file an insurance claim if there's a fire." The maintenance module is a secondary feature — it exists, but it wasn't built for this use case. Corn: It's like using a spreadsheet to write a novel. It technically works, but everything fights you. Herman: Centriq does support multi-user access, but only for viewing the home inventory. Logging new maintenance items with photos? That's single-user. The person who set up the account is the only one who can add entries. Corn: Neither of the home-specific apps actually delivers all three things Daniel needs. One fails on multi-user, the other fails on multi-user and rich media. Herman: This is where the market gets interesting, because the gap exists for a reason. Home maintenance tracking is what app developers call a thin market. It's too niche to attract a big development team, but also too fragmented for a single winner to emerge organically. Every homeowner's needs are slightly different, and the switching cost of moving your entire maintenance history to a new app is high enough that people just... Corn: You get a bunch of small players, none of them quite getting it right, and the whole category stagnates. Herman: Which pushes people toward generic tools. And this is where it gets interesting, because the generic tools are actually more capable in some ways than the purpose-built ones. Corn: Alright, walk me through that. If I give up on the home-specific apps, what am I looking at? Herman: The two that consistently come up are Notion and Airtable. Airtable in particular is compelling for Daniel's use case. The free tier supports up to twelve hundred records per base and allows unlimited attachments per record, including video. Corn: So that five-photo ceiling in HomeZada just evaporates. Herman: You could attach a fifty-photo timelapse of that window moisture over an entire winter, plus a video, all in a single record. And Airtable supports multi-user collaboration natively. You share a view with your roommate, they can add records, attach their own photos, comment on existing entries. Full attribution — you can see who added what. Corn: Airtable does everything Daniel wants. Herman: Because Airtable is a blank canvas. Out of the box, it has no idea what a maintenance log is. There's no "category: HVAC" field, no "priority: urgent versus seasonal" dropdown. You have to build all of that yourself. Corn: You're trading home-specific structure for raw capability. You get unlimited media and multi-user access, but you lose the guardrails that make a home app actually useful for home stuff. Herman: That tradeoff matters more than it sounds. The reason people stop logging maintenance isn't that the app lacks features — it's that logging feels like work. If you open Airtable and you have to manually type "HVAC" into a category field every time, and remember whether you called it "HVAC" or "air conditioning" or "AC" last time, the friction adds up. After three entries, you start putting it off. Corn: Which is the same failure mode as the camera roll, just with more steps. Herman: The other generic option people reach for is Trello. Trello boards are great for multi-user collaboration — shared access is the whole point. You can create a "Home Maintenance" board with columns for "to do," "in progress," "done." You can attach photos to cards and assign cards to specific people. Corn: Again, no home-specific fields. Herman: No structured fields at all, really. Trello gives you labels and due dates. If you want to filter by "HVAC" or "urgent," you're manually creating labels and hoping everyone uses them consistently. And video attachments on the free tier are limited to ten megabytes per file. A thirty-second video of a dripping faucet in decent quality will blow past that. Corn: Trello gives you the collaboration but takes away the media capacity and the structure. Herman: And this is the core finding from testing all of these — as of July twenty twenty-six, no single app on the market cleanly satisfies all three of Daniel's requirements. Home-specific structure, rich media, multi-user access. Corn: Which is a remarkable thing to say about a problem that affects literally every person who lives in a building. Herman: And I think the reason is structural. Home maintenance sits at this awkward intersection of personal productivity and household management. Personal productivity apps are built for individuals. Household management apps are built for families coordinating chores and grocery lists. Maintenance logging is neither. It's this weird long-duration documentation project that spans years and outlasts the devices you create it on. Corn: Outlasts the roommates. Herman: Which brings us to the second-order problem that nobody talks about. When a renter moves out, what happens to the maintenance knowledge? Herman: The next occupant inherits zero context. They don't know that the AC struggles to reach the bedroom when the temperature goes above ninety. They don't know that the window in the second bedroom seals poorly and leaks cold air in January. They don't know that the bathroom fan sounds like a lawnmower but it's actually fine, it's been doing that for three years, don't call the landlord. Corn: Landlords certainly aren't providing this. I've never met a landlord who handed over a maintenance log with the keys. Herman: Because they have no incentive to. A detailed maintenance log is evidence of problems, and problems are liabilities. If a landlord documents that the basement has had moisture issues for eighteen months and then a new tenant develops a mold allergy, that log is discoverable. Corn: The system is actively disincentivized from creating the very record that would make the system work better. Herman: And tenants, meanwhile, have no portable system. Even if you're diligent — even if you log everything in HomeZada for three years — when you move, what do you hand off? A PDF export that strips the photos? A shared login that you have to remember to transfer? Most people just... And the next person starts from zero. Corn: The absence of a good tool isn't just an inconvenience. It's a systemic failure in how rental housing transfers knowledge. Every move is a hard reset on the building's institutional memory. Herman: The cost of that reset is real. That five-hundred-dollar AC emergency we mentioned at the top? A lot of those are preventable. The coil freezes because the filter hasn't been changed in eight months. The filter hasn't been changed because the previous tenant never mentioned it, and the new tenant doesn't know where the filter even is. A single shared log entry — "change filter every ninety days, it's behind the panel in the hallway ceiling" — would prevent the whole cascade. Corn: What does the person who wants to solve this today actually do? Because we've established that the app store won't save them. Herman: The best current solution is a hybrid stack. And I want to be clear — this is a workaround, not an answer. But it works. You pick a flexible database tool — Airtable is my recommendation — and you build a custom base with the fields you need. Date, category, priority, description, status. You share that base with everyone in the household. That handles the structured record and the multi-user access. Corn: The photos and video? Herman: That's where the second piece comes in. Google Photos shared albums. A shared album supports unlimited photo and video uploads, and you can link to it from anywhere. In each Airtable record, you include a URL field that points to the specific Google Photos album for that maintenance item. Or even simpler — one shared album for all maintenance photos, and you paste the direct link to each photo or video into the Airtable record. Corn: The Airtable record says "window moisture, July fifth, moderate, photo evidence here" and the link takes you to the visual proof. Herman: It's not elegant. It's two apps where there should be one. But it delivers all three requirements — structure, rich media, multi-user — and it costs nothing. Setup takes about thirty minutes. Corn: For the homeowner who doesn't need multi-user? Herman: HomeZada is still the best single-user option for home-specific maintenance tracking. But — and this is a big but — test the export feature before you commit years of data to it. HomeZada's export is a PDF. I tested this. You log three maintenance items with photos, you export, and the PDF contains the text descriptions. The photos are gone. Corn: If you've logged forty-seven maintenance items with visual evidence of a basement moisture pattern over eighteen months, and then you sell the house and want to hand that record to the buyer... Herman: You hand them a text document. All that visual context, all those progression photos showing the moisture getting better or worse — stripped. The buyer gets "basement moisture noted, see photo" with no photo. Corn: That's not a feature gap. That's a trap. Herman: It's a trap. And it's the kind of thing you don't discover until you need it, at which point it's too late. So my recommendation for single-user homeowners is the same hybrid stack, honestly. If you ever plan to sell, or if you ever want to share the log with a contractor or an inspector, you need the photos to survive. Build it in Airtable, link to Google Photos, and you own your data in a format that actually travels. Corn: The actionable takeaway for Daniel, and for anyone listening who's been nodding along because they also have a camera roll full of orphaned AC vent photos — skip the home-specific apps if you need multi-user and rich media. Build the hybrid stack. Airtable for the structured log, Google Photos for the visual evidence, thirty minutes of setup, and you're done. Herman: The deeper point here is that the tool shapes the behavior. When the tool makes logging feel like friction — when you have to share a password, when your photos disappear on export, when you can't attach video — people stop logging. They go back to the camera roll. They forget whether they fixed it or just documented it. A good system isn't just about features. It's about whether you'll still be using it in six months. Corn: Which is the real test. Not "does this app exist," but "will I still be adding to this log when the next thing breaks. Herman: If the answer is no, you're back to scrolling through last July's photos, staring at an AC vent, wondering. Corn: The thing is, Daniel's prompt gets at something bigger than just app recommendations. He mentioned both urgent stuff — moisture in the window — and deferred stuff like the AC not reaching the bedroom. Those are two completely different categories of problem living in the same list. Herman: That's the distinction most apps completely miss. Urgent versus seasonal versus cosmetic. A to-do app treats "water dripping through the ceiling" and "paint touch-up in the hallway" as the same kind of item. They're not. One needs a plumber tomorrow, the other needs you to remember it exists when you're at the hardware store six months from now. Corn: If your system doesn't distinguish between those, the urgent stuff gets buried under the cosmetic stuff — you end up with a list of forty-seven things and no way to know which one is about to cost you five hundred dollars. Herman: The other piece Daniel mentioned that's worth naming explicitly — he wants this for Android and web. Not iOS-only, not Mac-only. That eliminates a surprising number of home management apps right there. A lot of the polished options in this space are Apple-ecosystem-first. Corn: Which makes sense if you're targeting homeowners with disposable income, but it's a nonstarter for anyone sharing a household across platforms. One roommate on Android, one on iPhone, and suddenly the "shared" part of the shared log falls apart. Herman: That's the quiet assumption baked into most of these apps — that a household is a single user with a single platform. But real households are messy. Different phones, different accounts, different levels of technical patience. The app that works for the person who set it up has to also work for the person who just wants to snap a photo of the dripping faucet and forget about it. Corn: The ideal solution may not exist as a single product. That's the honest answer to Daniel's question before we even get into specific recommendations. Herman: I think that's worth saying upfront because the app store will tell you otherwise. You search "home maintenance" and you get dozens of results, all promising to be the one thing you need. But what Daniel's actually asking for — structured, media-rich, multi-user, cross-platform — that combination doesn't ship in a single download as of right now. Corn: Walk me through what actually happens when someone tries to use HomeZada in a two-person household. Herman: It looks like a slow-motion argument about who forgot to log what. Picture a couple renting a two-bedroom apartment. One of them notices moisture collecting on the bedroom window frame. They log it in HomeZada, attach five photos showing the moisture at different times of day, add a note about the humidity reading they took. Corn: Five photos is the ceiling, right? Herman: That's the ceiling. Five photos total for that entry, forever. Now the other person in the household wants to check the log — maybe they noticed the moisture getting worse, maybe they want to add their own photo. They open the app on their phone. Corn: They can't see it. Herman: They cannot see it. Because they're not logged into the same account. The only way to give them access is to hand over the login credentials. So now both people are sharing one account, which means every photo in the log is attributed to whoever originally set up the account. There's no way to tell who took which photo, who added which note, who marked something as resolved when it wasn't. Corn: The accountability function of the log — which is half the reason you'd want it shared in the first place — just evaporates. Herman: And here's where it gets worse. The couple gets frustrated with HomeZada, reasonably, and they switch to something simpler — a shared Google Keep list. Now they can both see the list, both add items. Corn: Except Keep doesn't do attachments the way they need. Herman: Keep does photos, but not in a structured way. You can attach an image to a note, but it's inline — not a gallery. And video attachment on Keep is limited to a single file per note, with a ten-megabyte cap. So the moisture progression photos? The video of the drip rate? They now have a text note that says "window moisture — getting worse?" with no visual evidence at all. Corn: They downgraded from a flawed system to a non-system, and lost the one thing that made the log actually useful. Herman: That's the pattern. People don't usually jump from a bad app to a good one. They jump from a bad app to whatever is easiest, and the easiest thing is usually a notes app or a shared checklist that strips away all the structure. The photos end up back in the camera roll, disconnected from the log. Six months later, nobody remembers whether the moisture was seasonal or permanent. Corn: Let me push on something. You mentioned Trello earlier as a middle ground — it handles multi-user natively, it's free, it's cross-platform. If I set up a Trello board with columns for "urgent," "seasonal," and "cosmetic," and I train everyone to use labels for HVAC versus plumbing versus structural — doesn't that get me most of the way there? Herman: It gets you the collaboration. Trello's multi-user is good — you invite people by email, they get their own account, every action is attributed. For a household of three or four people who are all willing to use it, the social layer works. Herman: Trello has no idea what a maintenance log is. And that matters in two specific ways. First, the free tier limits file attachments to ten megabytes per file. A thirty-second video of a dripping faucet shot in ten-eighty-p is going to be forty or fifty megabytes. You can't attach it. You'd need to compress it or host it somewhere else and link to it, which adds friction. Corn: Friction is the enemy of logging. Herman: Second, the structure is entirely manual. Trello gives you labels and due dates. That's it. One person tags something "plumbing," another tags it "bathroom," a third doesn't tag it at all. Six months in, you've got eighty-seven cards and no way to quickly see all the plumbing issues. Corn: Whereas Centriq, for all its flaws, at least has those categories built in. Herman: Centriq has the categories — "HVAC," "plumbing," "electrical," "structural" — the whole taxonomy. And its maintenance scheduler can send reminders based on those categories. But — and this is the dealbreaker — you can only log new maintenance items as the account owner. The multi-user support Centriq offers is for viewing the home inventory, not for adding to the maintenance log. So you get the structure, you lose the collaboration. Corn: The landscape is basically three buckets. Bucket one: home-specific apps with structure but no real multi-user and stingy media limits. Bucket two: project management tools with great collaboration but no home-specific fields and media caps. Bucket three: blank-canvas databases like Airtable that can do everything but require you to build it yourself. Herman: That's the taxonomy. And bucket three is where the hybrid stack lives — Airtable for the structured log, Google Photos for the media, manual setup for the home-specific fields. It's the only configuration that hits all three requirements, but it's not a product. It's a project. Corn: Which raises the question — why hasn't anyone built the product? This isn't an obscure problem. Every homeowner and renter deals with maintenance. The market exists. Herman: The market exists but it's thin in a specific way that makes it hard to monetize. Homeowners might pay five dollars a month during the first year of homeownership, then forget about it. Renters are even less likely to pay because they can always just call the landlord. So you've got a user base that's price-sensitive and churns quickly. Corn: The people who need it most — renters moving every two and a half years — are the least likely to commit to a paid subscription for something that might not survive the next move anyway. Herman: So the development incentive is to build something broad enough to attract a big user base — which means generic productivity tools — or something narrow enough to charge a premium — which means single-user homeowner apps with insurance tie-ins like Centriq. The middle ground, the shared renter-friendly maintenance log with rich media, falls into a revenue gap. Corn: Daniel's prompt landed right in that gap. He's asking for something the market has structurally failed to produce. Herman: That market failure has real consequences beyond just annoyance. When a renter moves out, the next person inherits zero context. They don't know the AC struggles to reach the bedroom above ninety degrees. They don't know the window in the second bedroom seals poorly in January. They don't know the bathroom fan sounds catastrophic but it's been doing that since twenty twenty-three and it's fine, don't panic. Corn: The institutional memory of the building just resets. Every lease turnover is a hard reboot. Herman: Nobody is incentivized to prevent that. Landlords aren't going to hand over a maintenance log — a documented moisture pattern is a liability, not a selling point. Tenants have no portable system. Even the diligent ones, the people who logged everything for three years, they move out and what do they hand off? A PDF with no photos. A shared login they forget to transfer. The knowledge evaporates. Corn: Which means the next tenant rediscovers the finicky AC by suffering through it. They recreate the moisture photos from scratch. The same problems get diagnosed over and over, in the same apartment, by different people who never speak to each other. Herman: It's a systemic failure in how rental housing transfers information. And the tool gap is what makes it permanent. If there were a portable, shareable, media-rich log that survived moves, tenants could build a running history of the unit — independent of the landlord, independent of the lease. The next occupant gets a URL and suddenly they know everything. Corn: We don't have that. So what's the best approximation for someone who wants to build it themselves? Herman: The hybrid stack — Airtable plus Google Photos. Here's how it works in practice. You create an Airtable base with the fields you need: date, category, priority, description, status, and a URL field for photos. You share that base with everyone in the household. When someone notices the window moisture, they open Airtable, create a record, and in the description they paste a link to the Google Photos shared album where they uploaded the evidence. Corn: The Airtable record is the structured index, and Google Photos is the visual archive. Herman: Google Photos shared albums support unlimited uploads — photos and video, no compression on the free tier if you stay within your storage quota. You can create one album per maintenance item, or one master album for everything and link to individual photos. The album URL lives in the Airtable record. Anyone with the link can see the progression. Corn: When you move out, you can hand the entire Airtable base to the next tenant by transferring ownership or just sharing a read-only link. Herman: That's the theory. In practice, there's still a fragility here. If the person who created the Airtable base is the one who moves out, and they don't transfer ownership, the base goes with them. And if the original creator deletes their Airtable account, the base is gone. Corn: Even the hybrid stack has a single point of failure — the account holder. Herman: Every current solution does. HomeZada's export strips photos. Centriq locks logging to one user. Airtable ties the base to the creator's account. The common thread is that none of these tools were designed for a record that outlasts the person who started it. Corn: Which brings us to the homeowner side. If you own the place and you're not handing off to anyone, HomeZada seems fine on the surface. Single-user, structured, reminders built in. What's the trap? Herman: The trap is the export. I tested this — three maintenance items with photos attached, exported as PDF. The text descriptions survived. The photos did not. They're simply not included. So imagine a homeowner who's used HomeZada for three years. Forty-seven logged items. They documented a basement moisture pattern over eighteen months — photos showing the progression from minor dampness to active water intrusion, then the remediation, then the drying-out period. When they sell the house, they want to give the buyer that record. They export the PDF. Corn: The buyer gets a text document that says "basement moisture noted, see photo" with no photo. Herman: Forty-seven entries of "see photo" with nothing to see. The visual context — which is the entire point of documenting moisture over time — is gone. The buyer has no way to assess whether the moisture was a one-time event after heavy rain or a chronic foundation issue. The eighteen months of documentation achieved nothing. Corn: The homeowner who thought they were being responsible actually built a record that can't travel. They invested three years in a system that betrays them at the moment of handoff. Herman: This is why I keep coming back to the hybrid stack even for single-user homeowners. If you ever plan to sell, or if you ever need to share the log with a contractor or an inspector or an insurance adjuster, the photos have to survive. Airtable lets you export your data in CSV format, and the photo URL field will contain the Google Photos links. Those links work as long as the album exists. You control that. Corn: The actionable principle is: own your media separately from your log. Don't let an app's attachment system be the only place your photos live. Herman: That's the principle. And it shouldn't be necessary. The fact that we're recommending a two-app workaround for something that should be a single product is an indictment of the whole category. Corn: There's one more angle worth pulling on here. The smart home platforms — Google Home, Apple HomeKit — they're starting to creep into this space. I've noticed Google Home now nags me to change the air filter every ninety days. Herman: That's been rolling out over the last year or so. Both Google and Apple are adding maintenance reminders tied to smart devices. Your thermostat knows how many hours the system has run, so it can estimate filter life. These are useful. Corn: They only work for smart-connected things. The window moisture, the dripping faucet, the crack in the ceiling plaster — none of that has a sensor. None of it triggers an automatic reminder. Herman: That's the ceiling on smart home maintenance tracking right now. It's great for scheduled, predictable tasks — change the filter, flush the water heater, test the smoke alarms. But the messy, analog problems that make up most of a maintenance log? The weird smell from the crawlspace, the grout that's starting to crumble, the door that only sticks when it's humid? Those require a human to notice, photograph, and log. Corn: The smart home stuff solves the reminder problem for routine maintenance, but it doesn't solve the documentation problem for emergent issues. Herman: It doesn't solve the multi-user problem at all. Google Home's maintenance reminders go to the account that set up the home. Your roommate doesn't get them unless you manually share. There's no shared log, no collaborative record. It's a notification, not a system. Corn: The optimistic read is that this converges eventually. In two or three years, maybe Google or Apple builds a "Home Log" feature that combines smart sensor data with manual entries, shared across household members, with photo and video support. Herman: I think that's where it's heading. The infrastructure is there — shared albums, smart reminders, cloud storage. The pieces exist. They just haven't been assembled into a single product yet. And neither company has announced anything concrete. Corn: For now, the gap remains. And the person who wants to solve this today has to build the bridge themselves. Herman: Which is the deeper point. The tool shapes the behavior. When the tool makes logging feel like friction — when you have to share a password, when your photos disappear on export, when you can't attach video — people stop logging. They go back to the camera roll. They forget whether they fixed it or just documented it. Corn: A bad tool doesn't just fail to solve the problem. It trains you to give up on solving it. Corn: Given all that, what do you actually do starting tomorrow morning? Herman: First thing — audit what you have right now. And be honest about it. If you've lost track of a maintenance item in the last six months because you couldn't remember where you logged it, your system has already failed. You just haven't admitted it yet. Corn: The camera roll full of orphaned AC vent photos. The notes app with "fix faucet??The text you sent your roommate that says "did we ever deal with the window thing. Herman: That's not a system. That's digital litter. So step one is admitting you need to start fresh. And step two depends on whether you need multi-user or not. Corn: For Daniel's case — multi-user, photo and video, Android and web — the answer is skip the home-specific apps entirely. Build the hybrid stack. Herman: Here's the thirty-minute setup. Create a free Airtable account, start a new base from scratch. Add six fields: date, category as a dropdown with options like HVAC, plumbing, electrical, structural, cosmetic. Priority as a dropdown — urgent, seasonal, deferred. A description field. A status field — reported, in progress, resolved. And a URL field for your photo links. Corn: Then share the base with everyone in the household. Each person gets their own login, their own attribution. Herman: For the media, create a shared Google Photos album called "house maintenance" and drop every photo and video in there. When you add a record in Airtable, paste the direct link to the relevant photos. It's not seamless — you're switching between two apps — but the photos survive. The video survives. Anyone in the shared album can add to it. Corn: If you want reminders, Airtable has automations on the free tier. You can set it to email you every ninety days to check the AC filter, or every six months to inspect the window seals. It takes five minutes to configure. Herman: The whole thing — base, fields, automations, shared album — is thirty minutes of setup and zero dollars. And when you move out, you can transfer the base or share a read-only link with the next tenant. The knowledge survives. Corn: For the single-user homeowner who doesn't need collaboration, HomeZada is still the most polished option for structured maintenance tracking. But before you commit three years of data to it, test the export. Log three items with photos attached, export the PDF, and verify the photos are there. Herman: If they're not — and as of right now, they're not — switch to the hybrid stack. The principle is the same whether you're renting or owning: your media needs to live somewhere you control, separate from the app's attachment system. Corn: The final thing — start today. Not when you find the perfect app, not when you've researched every option. Open Airtable or Google Keep or whatever you're going to use, and log one thing. The moisture in the window. The AC vent. The dripping faucet. The system gets better the moment it exists. Herman: The question hanging over all of this is whether any of the big platforms actually step in and build the thing. Apple and Google both have the pieces — shared photo libraries, smart home hubs, household account sharing. They're already in our homes. They already send us maintenance reminders. The jump from "change your air filter" to "here's your home log" is not a technological leap. It's a product decision. Corn: Neither of them has made it. Herman: And I think the data suggests it's inevitable — the smart home platforms are expanding into more domains every year, and maintenance logging is a natural adjacency. But as of right now, there's no announcement, no beta, no roadmap commitment from either company. We're in the gap. Corn: The more interesting question is what happens when smart sensors start filling in the log automatically. Your thermostat already knows the AC runtime.