SIDEKICK · IPHONE & MAC
A home for the things I text myself.
A notes app that makes capturing a thought feel like sending a text, with separate chats, checklists, and reminders.
Product strategy, design & SwiftUI development · iPhone & Mac · Working prototype

Why I made Sidekick
I’ve always texted myself little things throughout the day. A quick thought, a note, something I didn’t want to forget. It was fast, easy, and always right there on my phone.
One day, I caught myself thinking, “I love how simple this is. There are so many ways I could make it better.” That thought became the starting point for Sidekick.
As I talked with friends, I realized how many of them did the same thing. Everyone had their own thread full of reminders, links, and stray thoughts. I started to see Sidekick as something that could be useful to people beyond just me.
Mark Summer · Creator of Sidekick
What I wanted to make better
I wanted to keep the speed and familiarity of texting myself, and improve what happened after I hit send.
Capture had extra friction.
Every note arrived back as an incoming copy, adding noise to something I wanted to capture once. Sharing photos or pausing an unfinished thought also took me out of that quick flow.
Everything shared one thread.
Doctor follow-ups, work emails, and everyday plans all lived in the same conversation. Finding one note meant searching through everything else.
Saved thoughts stayed static.
A packing list stayed a block of text, with no way to check items off. Time-sensitive notes needed another step to become scheduled reminders.
THE SOLUTIONS
Keep the habit. Improve what happens next.
I kept the ease of sending a message and focused the improvements on capturing, organizing, and acting on my own thoughts.
01 · CAPTURE
Keep capture effortless.
I kept capture as a single outgoing message, without an incoming echo. Photos stay in the composer, and a saved draft sits above it so an unfinished thought doesn’t block a new one. Drafts remain on the device I’m using.
A saved draft stays above the composer while I capture something new.
02 · ORGANIZE
Give thoughts a home.
Named chats let a familiar conversation carry the organization. I can separate health questions, work follow-ups, and trip plans while keeping capture as simple as sending a message. Saved places keep their address and source message in the same chat, so I can recover both the recommendation and why I saved it.
Separate chats give each topic its own place.
Saved places keep the address, recommendation, and original context.
03 · ACT
Make saved thoughts actionable.
I kept actions attached to the thought that prompted them. A message can become a checklist, with progress saved in place, or a scheduled reminder that returns to its source. That avoids making me recreate the same thought in a separate task list.
Check items off inside the original message.
Schedule a reminder and return to the source thought.
Native development captures with fictional notes.
Useful at my desk and on my phone.
I can write a thought at my desk and pick it up on my phone without starting a separate collection of notes. The Mac companion keeps the same conversations, with a persistent sidebar and a full keyboard for longer thoughts.
I removed automatic incoming copies because they added noise. But sometimes I do want a thought to come back later. Sending a chosen message to Notification Center keeps that useful behavior deliberate: I can leave it there and tap it to return to the conversation.

The Mac companion keeps the same conversation available at my desk. Development capture with fictional notes.
A LITTLE PERSONALITY
If something replies, give it a personality.
Getting my own message back was part of the problem. But it sparked another idea: what if a reply added a little personality instead of repeating my words? I added optional AI responses, from a simple emoji reaction to a short reply in voices like Drill Sergeant, Life Narrator, or Corporate Jargon. They use Apple’s on-device model on supported devices. I can choose the tone or turn responses off entirely, keeping the experience as quiet or playful as I want.
HOW I BUILT IT — AND WHAT I LEARNED
The details had to work in a real app.
I owned the product concept, interface design, and SwiftUI implementation, using AI tools to explore code and iterate on the build. Working natively let me evaluate the keyboard, navigation, storage, and system integrations together. I checked sending, draft recovery, editing, and Undo through focused tests, reviewed larger text and both appearances, and verified live text delivery between Mac and iPhone in both directions.
Add structure without adding noise.
The messaging habit gave me a useful starting point, but it also gave me decisions to make. I removed automatic duplicates, kept notifications deliberate, and made playful replies optional. The goal was to add structure without adding noise. Next, I want to learn whether people can save, recover, and act on their thoughts with less effort through broader everyday use.




