Daniel sent us this one — he's in the middle of moving apartments with a twelve-month-old, no family nearby to help, and he's got ADHD. He's trying to hold building codes in his head, to-do lists for moving out of one place and into another, measurements, utility stuff. And he's noticed something — some of this is tasks, some of it is notes, and those usually live in different apps. He's been tempted to just carry a notepad, but he uses voice-to-text heavily and doesn't want to lose that. The real question is — is there a system that bridges both requirements, something that works across Android and Linux?
This is one of those prompts where the framing is already doing half the work. He's identified the exact fracture point. Tasks and notes get split across different tools, and the moment that split happens, things fall through. You have a reminder to call the electric company sitting in a to-do app, but the account number you need for that call is in a notes app, and the photo of the meter is in your camera roll. The system doesn't just fail because you forgot — it fails because the pieces were never in the same room.
It's the productivity equivalent of keeping your socks in one apartment and your shoes in another.
The ADHD piece matters here more than most productivity advice acknowledges. When your working memory is already taxed, the cognitive cost of switching between apps isn't a minor friction — it's the thing that determines whether something gets done at all.
Where do we start? Because I've watched Daniel's systems over the years, and he's not someone who needs Productivity Theory one-oh-one.
Right, so let's skip the obvious stuff. Let's talk about the actual category of tools that handle this hybrid use case, and then get into which ones hold up under the specific constraints — Android, Linux, voice-to-text, tasks and notes in one place.
Before you name names — what's the actual design problem here? Why haven't task apps and note apps merged already?
Because they've been built on different metaphors. Task apps are built on the list metaphor — items that get checked off, ordered by priority or due date. Notes apps are built on the document metaphor — freeform space where you can dump anything. The list metaphor is great for actionability but terrible for context. The document metaphor is great for context but terrible for actionability. You can write a beautiful note about your new apartment's electrical setup, but that note won't tap you on the shoulder when it's time to call the electrician.
The ideal thing is a note that can also be a task. Or a task that can also hold a note.
That's the design spec. And there are two approaches. The task-with-notes model — your primary unit is a task, but each task can carry rich content inside it. The note-with-tasks model — your primary unit is a note, but you can embed actionable items inside it that surface elsewhere.
Which one fits this moving scenario better?
The task-with-notes model wins here. When you're moving, almost everything is time-bound. The electric company needs to be called by Wednesday. The boxes need to be packed before the movers arrive Friday. The building code needs to be referenced multiple times a day but only for the next two weeks. The temporal dimension is primary. If you put all this in a notes-first system, you end up with a beautiful document called "Move" that you have to remember to open. And remembering to open the document is exactly the failure point ADHD is going to exploit.
The system has to push things at you, not just hold them.
And this is where reminders and recurring tasks become essential. The building code thing is particularly interesting — he says he needs to remember it a few times a day. That's not a task you check off once. That's reference material that needs to surface repeatedly at the right moments. Most task apps don't handle that well because they're designed for completion, not recurrence of reference.
What does handle it?
Let me talk about three tools that are genuinely good at this hybrid model. TickTick, Amazing Marvin, and Obsidian with the Tasks plugin. They each solve the problem differently.
Start with TickTick. I've seen you use that one.
TickTick is probably the most polished of the task-with-notes apps. Every task can have a description field that supports rich text, checklists, images, and file attachments. You can add multiple reminders to a single task, set tasks to recur, and it has a dedicated "Notes" feature that exists alongside tasks — you can create a standalone note and later convert it to a task. It also has a built-in habit tracker, a Pomodoro timer, and an Eisenhower matrix view.
That's a lot of features. Does it actually hold together?
It holds together well, though the notes feature feels slightly bolted on compared to the task core. The Android app is excellent — fast, well-designed, full widget support. There's a web app that works on Linux. Voice-to-text works through whatever your phone's native dictation is, so on Android that's Gboard voice typing, which is solid. The free tier is generous — you can do almost everything except some calendar views and advanced filters. Premium is about thirty-five dollars a year.
The building code problem — how would you solve that in TickTick?
I'd create a task called "Building code reference" with the code in the description, set it to recur daily with a reminder at, say, eight AM, and then snooze it each day after I've referenced it. Or, if I need it multiple times a day, I'd pin it to the top of my task list so it's always visible. TickTick lets you pin tasks. That's one of those small features that makes a huge difference in this kind of scenario.
What about Amazing Marvin?
Amazing Marvin is fascinating because it was specifically designed with ADHD in mind. The creator, Mark Koester, has talked openly about building it to accommodate different cognitive styles. The core philosophy is that there's no single right productivity method — so Marvin lets you enable and disable "strategies" like a feature toggle system. You want a Kanban board? You want time blocking? You want the eat-the-frog thing where your hardest task is highlighted?
That sounds like it could be either incredibly liberating or completely paralyzing.
That's the tension with Marvin. The configurability is its superpower and its weakness. For someone who knows their own workflow and wants to build exactly the system they need, it's unmatched. But the setup phase is real — you can spend a week tweaking strategies before you've actually done anything. For Daniel, who's in the middle of a move and needs a system working today, that might be a nonstarter. Unless he's willing to stick with the defaults and customize later.
How does it handle the task-note hybrid?
Every task in Marvin can have a note attached, and the note field supports Markdown. You can also create "notes" as a separate entity. But where Marvin shines is in its category and project structure. You could create a project called "Move" with categories for "Old apartment," "New apartment," "Utilities," "Measurements." Each category holds tasks, and each task holds its own notes. The whole thing is visually structured in a way that reduces the cognitive load of figuring out what you're looking at. Voice-to-text uses native phone dictation. There's a web app for desktop, so Linux is covered. The Android app is good but not as polished as TickTick's. Pricing is higher — about eight dollars a month.
The third option? Obsidian with Tasks?
This is the note-with-tasks model. Obsidian is a Markdown-based note-taking app that stores everything as local files. The community plugin called Tasks turns it into one. You write tasks inline in your notes using a specific syntax — a Markdown checkbox with extra metadata like due dates, priorities, and recurrence rules. The Tasks plugin then queries all your notes and surfaces those tasks in a single view.
The task lives inside the note, but you can see it aggregated elsewhere.
You might have a note called "New apartment building code" that has the code written out, plus a task inline that says "Reference building code before measurements" with a daily recurrence. That task appears in your Tasks query view alongside all your other tasks. You check it off, and tomorrow it reappears. The note and the task are the same file. There's no sync gap.
That's elegant. What's the catch?
First, Obsidian is primarily a desktop app. The Android app exists and works, but it's not as fluid as TickTick or Marvin for quick task capture. Voice-to-text works through the phone's keyboard, but getting a task with the correct syntax via voice is fiddly — you'd be speaking Markdown formatting. Second, the Tasks plugin requires some initial configuration. You're writing queries in a syntax that's not quite SQL but not quite natural language. It's powerful but not immediate. Once set up, it's incredibly reliable — your data is local Markdown files, you can sync with Syncthing or Obsidian Sync, no vendor lock-in. And the note-taking capabilities are vastly better than anything TickTick or Marvin offer. If Daniel's long-term need is a permanent second brain that also does tasks, Obsidian is the strongest foundation.
Let's talk about the Android-Linux constraint specifically. That rules out a lot of the Apple-ecosystem darlings — no Things, no Bear, no Apple Notes.
It also rules out Notion in practice. Notion on mobile is slow. On Linux, you're stuck with the web app. And Notion's task features are still playing catch-up — there's no proper recurring tasks without third-party integrations. For a moving scenario where speed of capture is everything, Notion is the wrong tool.
What about the Google ecosystem? Keep plus Tasks?
That's worth discussing because it's the path of least resistance. Google Keep handles notes with voice-to-text beautifully — you can dictate a note and it transcribes in real time. Google Tasks handles, well, tasks. They're separate apps but live in the same ecosystem. The problem is they're still separate apps. You can't embed a task inside a Keep note or attach a Keep note to a task. You're back to the split-brain problem. And Google Tasks is aggressively minimal — no descriptions, no attachments, no subtasks beyond a single level. It's a checklist app, not a task manager. It fails the core requirement.
I want to go back to something you said about the building code problem, because I think it's the most interesting part of this prompt. He needs to remember a piece of information multiple times a day, but it's not a task — he's not going to "complete" the building code. It's reference material that needs to be ambiently present. That's actually a different category than either tasks or notes. It's what I'd call a temporary constant.
A temporary constant. I like that. It's information that, for a defined period, needs to be as available as the time in your status bar.
None of the tools we've talked about are designed for that. They're designed for things you do or things you reference occasionally. Not things you need to see every time you look at your phone.
The closest thing is TickTick's pin feature, which keeps a task at the top of your list regardless of due date or priority. Or a sticky widget on your Android home screen. TickTick has a note widget — you can pin a specific note to your home screen. So he could write the building code in a TickTick note, pin the widget, and it's there every time he unlocks his phone. That's probably the closest you get to a temporary constant in the current app landscape.
That's actually quite good. Set the widget, it's ambient for the two weeks he needs it, then remove it when the move is done.
That's the kind of thing traditional productivity advice misses entirely. It's not about capturing a task or organizing a project. It's about shaping your environment so the right information is in your peripheral vision at the right time.
The other thing I notice about this prompt is that Daniel mentions he's been tempted to just carry a notepad but can't bring himself to go back to pen and paper. There's something there about the physicality of a single object that holds everything.
There's a whole school of thought around this — the bullet journal people, the index card people. The argument is that a single notebook eliminates the app-switching problem entirely because everything is literally in one place. And for ADHD, there's some evidence that the physical act of writing engages different cognitive processes than typing or dictating. But he's right that you lose voice-to-text, and you lose search, and you lose reminders that push to your phone. A notebook doesn't tap you on the shoulder. When you're moving, you need the shoulder tap. The notebook is a capture tool, not a prompting tool.
The notebook impulse is real — the desire for a single surface — but the solution has to be digital.
And I think that's actually the design principle to evaluate against. Does the tool give you a single surface for tasks and notes? Or does it give you two surfaces that happen to share an icon?
Let's apply that test.
Mostly a single surface. Tasks and notes live in the same app, you can convert between them, the pinned items and widgets create a unified view. The notes feature is slightly secondary, but for a task-heavy period like a move, that's probably the right emphasis.
Single surface, but highly configurable. The risk is that you'll spend the moving weekend configuring the surface instead of using it.
Single surface in theory — it's all Markdown files. In practice, the Tasks query view is separate from the note editor, so you're still switching contexts. And on mobile, those contexts are further apart because of screen size.
TickTick comes out ahead on the single-surface test.
For this specific scenario, I think so. But I want to complicate this, because there's another dimension. This is a temporary, high-intensity period. In two months, the move is done. The building code is no longer relevant. The system Daniel needs during the move might not be the system he needs after it. So there's a question of whether to adopt a new tool for the move and then migrate back, or to find something that scales down gracefully. Moving into a new productivity app is itself a project, and he's already got a project.
If Daniel already has a task manager and a notes app he's comfortable with, the pragmatic solution might be to bridge them with a lightweight integration rather than switching platforms mid-crisis. Android's share sheet lets you send text from almost any app to almost any other app. Two taps and a note becomes a task. It's not as seamless as a single app, but it's zero setup and zero migration. The perfect is the enemy of the moved-in.
If he's going to switch, TickTick?
If I were making a recommendation specifically for this scenario — Android plus Linux, voice-to-text heavy, tasks and notes in one place, ADHD-friendly, low setup time, handles temporary constants — I'd say TickTick. The free tier means he can try it without commitment. The Android app is good. The web app works on Linux. The widget system handles the building code problem. And once the move is done, it scales down to a normal task manager without feeling like overkill.
What about the voice-to-text workflow specifically?
TickTick's voice input uses your phone's native dictation — you tap the mic icon on the keyboard, speak, and the text appears in the task or note field. But if he wants something where he can say "remind me to call the electric company tomorrow at ten" and have it parsed into a task with a due date automatically, that's more of a Google Assistant or Todoist natural language thing. Todoist, however, doesn't handle the notes side — it has task descriptions and comments, but you can't create a standalone note. It fails the notes half of the equation. TickTick actually has some natural language parsing — you can type "call electric company tomorrow at ten" and it'll set the due date — but it's not as sophisticated as Todoist's.
Let's talk about the ADHD angle more directly. You mentioned Marvin was designed with ADHD in mind. What does that actually mean?
A few things. One is "task initiation support" — the app can be configured to show you only one task at a time, which reduces overwhelm. Another is a "reward" system — small celebrations when you complete tasks, which sounds silly but actually engages dopamine pathways relevant for ADHD motivation. There's also a "procrastination count" that tracks how many times you've snoozed or rescheduled a task. That last one could be either motivating or deeply shaming, depending on the person. The configurability of Marvin means you can turn it off if it's not serving you.
What about the overwhelm of seeing a huge task list? That's a known ADHD pain point.
Both TickTick and Marvin handle this reasonably well. TickTick lets you filter by list, tag, priority, and date, so you can narrow your view to "what actually needs attention right now." Marvin has the single-task mode and something called "the jar" where you put tasks you're not working on today. Obsidian with Tasks can do this too through query filtering, but again, you have to write the queries.
I think there's also something to be said for the physical environment during a move. You're surrounded by boxes, your normal routines are disrupted. The productivity system has to work in that context, not in a clean desk scenario.
That's underappreciated. Most productivity advice assumes a stable environment — your desk, your morning routine, your weekly review. A move blows all of that up. Your phone might be the only stable surface you have. So the system has to be phone-first, not phone-also. TickTick's Android widget support is best-in-class. You can have a widget that shows your today list, a widget for a specific list, a widget for a specific note, a calendar widget. You can build a home screen that is essentially your moving command center.
He mentions he's working mostly from Android but also uses a desktop running Linux, usually through a web app. That "usually a web app" phrase is doing a lot of work.
That's actually liberating because it removes the "no Linux client" problem. As long as there's a functional web app, the Linux desktop is covered. TickTick's web app is nearly identical to the desktop app. Marvin's web app is the desktop app. Obsidian has a native Linux app, which is nice but not essential. The real constraint is the mobile experience, because during a move, that's where most of the capture and reference is happening.
What about the building code specifically? Are there any tools that handle this kind of temporary reference material particularly well?
This makes me think about quick-capture note apps designed for exactly this kind of ephemeral information — Google Keep, Simplenote, or even a pinned message in a messaging app. The idea is you have a scratchpad that's always accessible, and you treat it as disposable — it holds whatever you need right now, and you clear it when you're done. So instead of trying to make a task manager handle reference material, you use a separate scratchpad that lives on your home screen. That might actually be the most pragmatic solution for the building code problem.
That simplifies the tool decision. The task manager handles tasks-with-notes. The scratchpad handles temporary reference material. Two tools, but each has a clear job.
The jobs don't overlap, so there's no ambiguity about where something goes. Task with a deadline? Piece of information you need to see repeatedly for a defined period? Ambiguity is the enemy of ADHD productivity systems — you want the capture decision to be instantaneous.
If we're recommending a stack rather than a single tool, what does that look like?
TickTick for tasks and task-notes, plus either Google Keep or a TickTick note widget for temporary reference. Or, if he wants the note-taking to be more robust and long-term, Obsidian for notes and TickTick for tasks, with the understanding that they're separate but each excellent at their thing.
That's two tools. The original prompt was asking for one system.
I know, and I've been going back and forth on this. The single-tool solutions exist — TickTick is the closest — but the building code problem is a different category than the task-note hybrid problem. Trying to solve both with one tool might mean solving neither perfectly. But for someone in the middle of a move, perfect isn't the goal. And on that metric, TickTick alone plus a widget gets you to functional. You've got tasks with notes, voice-to-text through the keyboard, Android and web, the building code pinned or widgeted. It's a single app, free to start, low setup time. For the specific scenario in the prompt, that's probably the answer.
What would you say to someone who's attached to their existing notes app and doesn't want to migrate?
Then the answer changes. If he's already using something like Obsidian or Notion for notes, the recommendation would be to add a task layer that integrates well rather than switching everything. But the prompt says he's looking for something new that bridges both, so I'm reading that as willingness to try a new tool.
Is TickTick something you'd want to keep using long-term?
I think so. It's a mature, well-maintained app with a large user base. The feature set is deep enough that you can grow into it — habits, Pomodoro, calendar integration, collaboration. And if he decides later he wants something different, exporting tasks from TickTick is straightforward. It's not a roach motel. TickTick lets you export to CSV, and there are third-party migration tools. That matters if you're trying something new and don't want to feel locked in.
Let's talk about the voice-to-text workflow one more time. How does that actually work day-to-day in TickTick?
The flow is: you open the app, tap the add button, tap the title field, tap the mic on your keyboard, and speak. The text appears. Then you can add additional details — due date, priority, list — either by typing or by using the natural language parsing. It's not as fluid as a dedicated voice assistant where you can do everything hands-free, but it's as good as any text-input app can be. If he wants truly hands-free task capture, the closest thing on Android is Google Assistant with Google Tasks, but we've already established that Google Tasks doesn't handle the notes requirement.
There's a tradeoff between voice fluidity and notes capability.
And for this prompt, notes capability seems more important than hands-free voice capture. He can tap a button and speak; he just can't do it while carrying boxes. If hands-free capture while carrying boxes is essential, then the recommendation shifts. Google Assistant plus Google Keep plus Google Tasks — three tools, but all voice-accessible without touching the phone. The notes and tasks are still separate, but the capture is frictionless. For ADHD, capture friction is everything. The best system in the world is useless if the thought evaporates before you can get it into the system.
We've got two recommendations, depending on which tradeoff matters more. TickTick for a unified task-note system with good but not hands-free voice input. Google ecosystem for hands-free voice capture with separate task and note apps.
A third, which is TickTick plus Google Assistant for quick capture into a TickTick inbox via IFTTT. But that's an "after the move" project, not a "during the move" solution.
I want to circle back to something you said earlier about the notebook impulse. The desire for a single physical object that holds everything. I think there's a version of this that's actually achievable digitally, and it's not about finding the perfect app — it's about having a single inbox.
The problem isn't that tasks and notes are in different apps. The problem is that capture goes to different places. If everything — task, note, building code, measurement, reminder — goes to the same inbox first, and you sort it later, you've effectively created a single surface for capture. The sorting can happen when you have a moment, not in the moment of capture.
That's essentially the Getting Things Done capture habit applied to a multi-tool reality. And it works if you have one inbox that's frictionless. On Android, that inbox could be a TickTick quick-add tile, or a Keep note, or even a Telegram message to yourself. Daniel already uses Telegram heavily. Use Saved Messages as the universal capture inbox, then process into the appropriate tool during a daily review. The building code gets copied to a widget. The utility tasks go to TickTick. The measurements go to a Keep note. But the initial capture is always the same gesture.
That's the "one surface" solution that doesn't require switching tools. It just requires the discipline to process the inbox regularly.
Which, for someone with ADHD, is both the strength and the weakness. The capture is effortless. The processing requires a routine. If the routine slips, the inbox becomes a graveyard of half-remembered tasks. But during a move, you're probably checking your phone constantly anyway. Processing the inbox might happen naturally because you're in a state of heightened task awareness. During high-intensity periods, the normal ADHD challenges with routine maintenance sometimes resolve themselves because the external pressure is high enough to keep the system running.
Maybe the recommendation is: use whatever capture method is fastest right now, process into TickTick once or twice a day, and don't overthink the tooling until the move is done.
I think that's the honest answer. The prompt is asking for a system, and we've given a recommendation — TickTick, with the building code pinned or widgeted. But the meta-advice is that during a move, the system that works is the one you actually use, not the one with the most elegant architecture. Friction reduction beats feature completeness.
I think we should actually name the specific setup, step by step. If Daniel were sitting here right now, what would we tell him to do?
Install TickTick on Android. Create a list called "Move." Create a task for the building code, paste the code in the description, set it to recur daily, and pin it to the top of the list. Create a TickTick note widget on the home screen with the building code if he wants it even more ambient. For everything else, use the quick-add button to capture tasks as they occur, and use the description field for any notes or context that task needs. Voice-to-text through Gboard. On Linux, use the web app for review and organization. That's the whole system. Setup time: maybe fifteen minutes.
If he wants to use Telegram Saved Messages as a capture inbox first?
Then the flow is: thought occurs, dictate or type into Saved Messages, move on. Once or twice a day, open Saved Messages, process each item into TickTick with the appropriate due date and list. The building code still lives in TickTick as a pinned recurring task. The Saved Messages inbox is just the front door.
That's clean. I like that it doesn't require changing how he thinks, just where he points the firehose.
That's really the key. Productivity systems fail when they ask you to change your cognitive style. Good systems adapt to how you already think and just catch more of what falls out.
I want to address one more thing in the prompt. He mentions that his organizational systems have "already held" — past tense — but the move is creating a new kind of load. There's something there about systems that work under normal conditions breaking under extreme conditions.
Most productivity systems are designed for steady-state operation. They assume a relatively stable set of projects, a predictable flow of incoming tasks, a consistent environment. A move is none of those things. It's a temporary spike in complexity across multiple domains — logistics, finance, administration, physical labor, parenting. The system has to handle a ten-X load increase for a defined period and then return to normal.
The question isn't just "what tool," but "what mode." Maybe he needs a move-specific configuration of whatever tool he uses, with the understanding that it's temporary.
And that's actually liberating, because it means you don't have to build a system for all of life. You build a system for the move, use it intensively for six weeks, and then archive it. The "Move" list in TickTick gets hidden when it's done. The building code widget gets removed. The system contracts back to normal.
I think that's the insight I'd want to leave with. The tool matters, but the temporary, high-intensity mode is the real design challenge. Build the system for the crisis, not for eternity.
The crisis has a known end date. That's actually a gift, from a productivity standpoint. You're not designing for an open-ended future. You're designing for "I need to get through the next two months without losing my mind or the building code." Constraints are helpful. Infinite possibility is paralyzing. "Android plus Linux plus voice-to-text plus tasks and notes together" is a set of constraints that narrows the field to a manageable few options. And "I need it working by tomorrow" narrows it further.
TickTick, with a Telegram inbox if he wants it, and a widget for the building code. That's the recommendation.
That's the recommendation. With the caveat that if he tries it and the voice-to-text friction is too high, the Google ecosystem fallback is right there. No shame in using the tools that are already on the phone.
Practicality over purity. I think Daniel will appreciate that.
I hope so. And I hope the move goes smoothly. Moving with a twelve-month-old is a special kind of exhausting.
I've never done it, but I've watched it. It looks like trying to solve a Rubik's cube while someone keeps handing you additional Rubik's cubes.
That's probably the most accurate description I've heard.
And now: Hilbert's daily fun fact.
Hilbert: In nineteen-oh-two, radio operators in Cape Verde accidentally picked up what they thought was static from a local storm — but it turned out to be the first unintentional detection of radio emissions from a solar flare, something that wouldn't be properly understood for another forty years. The station's logs from that day simply read "unusual interference, no storm visible.
"Unusual interference, no storm visible" is a pretty good tagline for most of human discovery.
Also a solid album title.
This has been My Weird Prompts. Thanks to our producer Hilbert Flumingtop. You can find us at myweirdprompts dot com, on Spotify, or wherever you get your podcasts. If you've got a prompt for us, send it our way.
We'll be here. Probably not moving.
