Sway

@copywizard Thanks, i really appreciate that.

Sway focuses less on individual sentences and more on intent over the whole thought flow. Repetition, emphasis, and where ideas turn into decisions matter more than perfectly phrased lines.

Control is intentionally light right now. We want the first summary to feel like someone who listened really well.

More ways to gently shape summaries (without turning it into prompt work) are coming.

And yes it’s built exactly for people who think out loud 🙏 😊

@christian73 Two blocks into a walk, I start thinking out loud, then those voice notes just sit there. Lock screen shortcut plus one tap to start capture would make Sway stick. A quick transcript edit before the summary, key points, and next steps would build trust.

@yulianazarenko That’s a great way to put it. Yes, Sway is closer to a thinking / note taking companion than a classic writing copilot.

The main difference is when the structure happens.

With tools like ChatGPT, you usually still have to sit down, prompt, and “enter writing mode.”

Sway is designed for the moment before that … when ideas are still messy, spoken, and happening while walking for instance.

For thought leadership specifically, many people use Sway to:

• talk through ideas on a walk

• capture the core message + angle

• then turn that into a LinkedIn post later or other socials (sometimes with another tool, sometimes directly)

The no prompts environment is very intentional, cause it removes friction and helps people actually build the habit first.

If your CEO thinks best while walking, this is exactly the kind of use case we had in mind 🙂

Happy to hear how it works for him if you end up suggesting it!

@christian73 I just tested the app and I have to say that I would try it again. It took the second step out of my process by not having to then move the block of text into another AI (Claude) to get the outline output. I also didn't realize until using this app that by not seeing the words I'm saying (like I do in Docs) actually allows me to stay more present in my thoughts. I didn't realize just how much I'm still editing my thoughts and words as I'm going just because I can see the words in the Doc.

@adam_lab Thanks a lot, really appreciate that 🙏

And love hearing that the “thinking while walking” flow resonates.

Right now Sway handles technical / domain specific language surprisingly well as long as it’s spoken naturally (e.g. dev terms, product jargon, acronyms). We don’t try to “simplify away” terminology ... the goal is to preserve intent and meaning, not rewrite it for a generic audience.

That said, there are still edge cases where very dense or highly specialized jargon can get slightly abstracted too much. Improving domain sensitivity (and letting users steer how literal vs. abstract summaries should be) is something we’re actively working on.

If you’re using it in a specific domain (engineering, product, research, etc.), I’d genuinely love to hear how it performs there. That kind of feedback is gold for us.

Thanks again for checking it out!

@leo_aj That’s exactly how it feels for me too.

Preserving momentum first, structure second is the core idea behind Sway. Really appreciate you sharing this.

@suin_moon Great question.

Sway uses a lightweight intent-extraction layer rather than a single “hard” summarization pass. We bias toward explicit signals in the speech (commitments, decisions, open questions) and keep uncertainty when intent isn’t clear.

The goal is to preserve the speaker’s intent, not impose a narrative.