r/launchigniter

I'm one of the people building Swooni, a relationship app for couples.

We built it because most relationship apps feel either too clinical, too generic, or like homework. Swooni is meant to make relationship growth feel more practical and easier to stick with.

What makes it different:

- Based around the Gottman Magic Ratio and therapy-inspired principles.

- Small daily challenges that help couples stay connected without making it feel heavy.

- Progress, rewards, and a couples community layer that shows in-app actions without exposing private relationship details.

It's not therapy or a magic fix, but it's designed to help couples notice connection patterns and stay more intentional over time.

iOS: https://apps.apple.com/us/app/swooni-relationship-tracker/id6557063166

Android: https://play.google.com/store/apps/details?id=io.honeyroots.app

Would love honest feedback from anyone who tries it.

Managing investments across multiple apps is messy.

Arthavi helps you track your mutual funds and stocks together in one place, without spreadsheets or cluttered dashboards.

### 🚀 What it does

- Unified portfolio view (MF + stocks)

- Clean and minimal interface

- Simple performance tracking (no confusing metrics)

- AI-powered insights (early feature)

### 💡 Why it’s different

Most tools either:

- Focus only on stocks

- Or only on mutual funds

- Or overwhelm users with too many features

Arthavi is built for clarity and simplicity first.

### 👤 Who it’s for

- Long-term investors

- People tired of juggling multiple apps

- Anyone who wants a simple portfolio overview

### 🔗 Try it: https://arthavi.com

Would love feedback from the community 🙌

Today I finally launched "Satro" on Product Hunt.

I'd love honest feedback from builders, students, professionals, or anyone interested in personal growth.

What would make an app like this genuinely useful for you?

Thanks for taking a look 🙌

https://www.producthunt.com/products/satro?utm_source=other&utm_medium=social

Hi everyone! 👋

After 18 months of development, today I'm officially launching Presswork —

the writing tool I dreamed of as a former editorial director (sold Jona

Editore in 2023, started Presswork shortly after).

**The problem I was solving:**

As an editor, I had spent years fighting with 4 different apps to take a

manuscript from draft to print: Word to write, InDesign to layout, Sigil

for ePub, Adobe to sign. Every step manual, error-prone, disrespectful of

creative time.

I built Presswork because I wanted a single tool that respected the writing

flow and produced professional outputs without manual exports.

**What it does:**

- A single `.pwk` document contains: text, narrative branches (Git-style

— try an ending, roll back), version history, automatic outputs

- No more "Save as": when you write, every format is already prepared

in the background (PDF/X-4, ePub 3.3 validated for Kindle, FDX for

Final Draft, ICML for InDesign)

- Offline AI editorial tools (Blurb, Synopsis, Metadata generator,

Consistency check) — NO cloud, NO upload, GDPR-safe

- Digital signature with RFC 3161 timestamp (legally valid in EU/Italy)

- Native cross-platform: Mac (Apple Silicon + Intel), Windows (x64 + ARM64), Linux

- Built with Rust + Tauri + Llama 3 + Typst + Pandoc

**Pricing:**

- Base: €99 — Essential writing + sign + export

- Editorial: €149 — Authors, screenwriters, KDP/Kindle workflow

- Pro: €149 — Professionals, batch PDF signing, analytics

- Studio Complete: €249 — Everything integrated

- Business: €995 — 5x Studio Complete for teams

Lifetime license. No subscriptions.

🎁 Code **LAUNCH20** = -20% off for the first 200 buyers.

**Demos:**

- 🇮🇹 IT: https://www.youtube.com/watch?v=TaIDQVIu9ig

- 🇬🇧 EN: https://www.youtube.com/watch?v=5RJRw650ov4

**Get it:** https://presswork.it (or https://presswork.online for English)

Open to feedback, bug reports, feature requests — pin them here or

DM me. Roadmap discussion welcome.

— Alessandro

I’ve been working on a fitness tracking app called Liftora.

The main idea came from a problem I kept running into with a lot of workout apps: they can log exercises, but they often feel either too cluttered, too generic, or not motivating enough to keep using consistently.

I wanted something that helps people through their fitness journey in a more practical way:

• track workouts step by step
• monitor body measurements in one place
• see progress with simple, useful charts
• stay more aware of training flow instead of just logging numbers

So I started building Liftora with a focus on clarity, structure, and motivation.

Right now, the app is centered around three things:
workout tracking, body metrics, and progress visualization.

The goal is not just to record data, but to make that data easier to understand and more helpful over time.

I’m still improving the product and I’d really like honest feedback from people who actually track their training.

A few things I’d love to hear:

• Does the product feel useful at first glance?
• Which feature would make you try an app like this?
• What feels missing from your current fitness tracker?

If you want, I can also share the Play Store link in the comments.

✨ vibemoji.fun : you pick emojis across themed rounds (audience, problem, platform, vibe...) and AI reads your "emoji trail" and generates a full product blueprint: name, pitch, target audience, features, user flow, tech stack, and mock screens.

No text input, no forms. Just emojis . You get a couple blueprints free to try it out, then it's a credit system.

The part I'm most proud of: I actually built one of the blueprints.

I ran vibemoji myself. The emoji trail I picked pointed at a language-learning cooking app 🍝. The blueprint it generated - here's the actual output - called out a vocabulary popover interaction, video clips cued to exact timestamps in the recipe, even a community photo wall.

So I built it: Cucina Lingua — recipes in Italian and Spanish, tap highlighted words for instant translation, each step paired to a native-speaker video at exactly the right moment.

Blueprint to working app with AI only.

Happy to answer questions about how the emoji → blueprint pipeline works, or how I built Cucina Lingua from the output.

When does it actually make sense to open source something and when is it just a distraction?

For a long time I thought open source meant free software, usually maintained by the community, and something you do when you are not trying to build a business around it.

Building and making a tool open source made me sort of unlearn that.

There is no grand hidden twist in the story: We were frustrated with the state of API tooling, built something for ourselves, showed it to users, and realized very quickly that we shared the same pain with other folks as well.

And because our actual business was elsewhere, we had an unusual amount of flexibility. We didn’t need the open source tool to be a revenue source, and this is what changed the equation for us.

So the decision to open source it was quite practical and I am very happy with it.

Here are my two cents around the debate to open source or not:

1. Open source only works when it doesn’t threaten the core business

If your open-source project needs to become the business, you might eventually start making compromises that feel subtle at first, but can compound over time.

2. Timing matters more than intent

I used to think open source was about intent and ideology, that you believe in sharing, opening etc. But timing is also important, perhaps even more.

In our case, we didn’t open source from, day one. We did it after we:

• used it internally a lot
• validated real demand from real users
• knew and were sure we could support it properly

If we had done it earlier, it would have been performative. If we did it too late, it might have become a closed product by inertia.

3. Open source does not mean “less responsibility”

Again, I often used to associate open source with less ownership but in practice, it’s more like owning in public.

That means:

• decisions are visible
• tradeoffs are questioned
• and you don’t get to silently rewrite history anymore 😄

So perhaps even more responsibility and a different kind of pressure.

4. Distribution is not the same as adoption

Another misconception I had early on: “open source means that it will spread on its own.”

Good luck. You still need clarity of product, positioning, and a reason for people to care.

If anything, it forces you to be more honest about whether people actually want what you built.

5. The important question is not “open source or not” but "what do you want to optimize for?"

• Control or collaboration?
• Revenue leverage or ecosystem adoption?
• Speed of iteration or breadth of feedback?

For us it was easy to decide when we realized our tool will benefit more from being shaped in the open than from being tightly controlled.

And for other founders thinking about it, the only real question I would leave is this:

Are you opening it because it helps the product evolve , or because you are not unsure what else to do with it?

I think this answer changes everything.

Link to our repo: https://github.com/VoidenHQ/voiden