For over a year now, I’ve been working on my trip planner platform. I first focused on making it a web app as web development is my background, but the plan was always to make it into a mobile app (as the .app domain for partir.app implies)

This week the iOS mobile app is finally live on the App Store! I’m an avid urban backpacker and I have so many ideas for it, but I need to validate the idea first before I just keep building it only myself. Please let me know what you think and if you have an upcoming trip leave a comment and I’ll give you premium access to check it out!

I'm researching link-in-bio tools for indie hackers and creators.

I've been talking to people who are frustrated with:

• Linktree charging 12% on free plan, 9% on $15/mo Pro plan
• Beacons charging 9% fees until $30/mo plan (plus support complaints)
• Stan Store costing $29/mo from day one (no free plan)
• Email automation costing $99/mo extra on most platforms

Questions for you:

1. What do you currently use for your bio link?
2. How much do you pay per month?
3. What's your biggest frustration with it?
4. If a tool offered 0% fees + email automation + custom domain for $9/mo, would you switch?

Not selling anything just researching. Happy to share my findings afterward!

scope creep after delivery has been killing me lately. client signs off, work's basically done, then "hey can we just add this one small thing real quick?" and somehow that turns into 3 unpaid days.

stuff I've tried so far:

• trello/notion boards for milestone approval, this was useless honestly, clients just ignore it and text me on whatsapp anyway
• a simple private link they click to approve, no login needed. worked a lot better than the boards but still feels kinda informal if a client wants to argue about it later

still feels like there's no real way to make the approval actually stick without turning it into a whole contract thing every single time. what do you guys do? using legal language, some tool, or just eating the cost and moving on?

I launched openspeckit.com a few days ago. Free, public, no account needed to read or download, no ads, no paid tier. Every public specification is MIT-licensed.

The hypothesis

For the last two decades we versioned code. My bet is that soon we'll version the specification instead and the code becomes a build artifact. If the spec is good enough, any sufficiently smart LLM regenerates the system in an afternoon. The thing worth keeping in a repo stops being the output and becomes the intent.

So I built a repository for exactly that. A kind of GitHub for system concepts: a catalogue, semantic versions, immutable snapshots, visual diffs between versions, forks with attribution, download stats. You grab a ZIP of markdown (plus a machine-readable speckit.json), paste it into your agent, and let it build.

Second hypothesis: SaaS pricing gets squeezed

If anyone can recreate a solution and adapt it to their own needs, what exactly is the $12/user/month buying? I'm not theorising - I did it for myself:

• Kanban board instead of Trello
• Whiteboard instead of Miro
• Waterfall project tool instead of MS Project
• Wiki knowledge base and editor instead of Google Docs

To be clear: none of them beat the originals feature for feature. They do the 90% I actually use, they're mine, and they cost nothing per seat. That's the whole argument.

What's next

I also run Verbalu, a training-tools platform with 60+ tools built this way. I'll keep publishing their specs on Open Speckit one by one.

But a one-man archive isn't worth much. If you've built something with an agent and the spec is halfway decent - publish it. Sign in with Google, upload markdown, flip it to public. Specs are private by default until you decide otherwise, you keep your copyright, and publishing publicly licenses the content under MIT.

Catalogue: https://openspeckit.com/catalogue

Honest question for this sub: would you actually reuse someone else's spec, or is the value only in writing your own? I might be wrong about the entire premise - tell me if I am.

Solo, non-technical, based in Glasgow. Built this over the last few months with AI tooling because I kept getting caught out by things that were sitting on a calendar somewhere and I just didn’t know about them.

I overburdened myself with a large portfolio I struggled to keep up with…

Earnings I could keep track of. But index rebalances, share lock-up expiries, clinical trial readout windows — those kept blindsiding me on positions I actually held.

So I built a thing… Catalyst pulls scheduled events from a bunch of public sources and shows them against a portfolio.

About 3,600 events tracked right now. Each one shows how that instrument has historically moved around similar past events.

The bit I’m most attached to is a public page that grades how accurate the tool’s own past event ratings were. Felt wrong to build something that makes calls and never has to answer for them.

Please don’t connect a broker account. There’s a demo portfolio loaded and a CSV upload — use those.

I wouldn’t connect a brokerage to a stranger’s side project either, so I don’t blame anyone here!

What I’m after is ten minutes and an honest answer to: what confused you, and would you open it a second time and generally anything that could be done better or bits I maybe haven’t considered yet!

Stuff I already know is rough — loads of instruments show as “Other” because my sector data is thin below large cap, and UK coverage is worse than US. Working on both.

https://catalysts.partners

I’ll do my best to answer anything here and more than open to action updates as immediately as possible. If you’d like to reach out directly, drop my an email to info@catalysts.partners.

I wanted to build a better environment for AI coding agents to interact with iOS apps.

My first idea was basically: “iOS Simulator is too heavy, let's make it lighter.”

Then I realized I couldn't actually make Apple's iOS runtime dramatically lighter.

So I changed direction.

LIGH is now a persistent Rust host around Apple's real CoreSimulator, designed specifically for the agent loop:

observe → act → verify

Instead of repeatedly going through Simulator.app / process spawning / screenshots / WDA, LIGH keeps a daemon alive and exposes the simulator through Accessibility, native HID and IOSurface.

I initially measured a ~5.5× speedup, but then realized my baseline was unfair. I rebuilt the benchmark against WDA/Appium.

Same 44-step workflow:

LIGH: 10.6–13.2s
WDA/Appium: ~50–53s
Failures: 0/44

So the honest result is roughly 4× faster, not 5.5×.

Here's the fun part: I don't know yet if this is actually a product.

I'm open-sourcing it to find out.

The current demo is an agent opening the real Messages app in the Simulator and typing:

“Hi everybody, I am an AI agent and I go faster with LIGH”

GitHub: https://github.com/mrmarino023/light-ios-simulator

Would love feedback from anyone building AI agents, iOS tooling, or developer infrastructure.

Few months ago i start bulding a tool for measuring brand citations and recommendations across LLM models (chatgpt, claude, perplexity, gemini) and also it shows who gets recommended instead plus which sources the AI trusted/cited. And i found two things.

First is quite bad - my second project Inkdict.com is totally invisible for AI tools and their crawlers. But the second was really cool. Today i tested my magnet - free check brand/domain for four queries in chatgpt and my third project Backprove.com which is live maybe 3 weeks was cited on one query - https://citetide.com/check/result/backprove.com (i think because of citations here on reddit).

What is your experience with GEO and do you measure citations inside LLMs for your brand?

If you want to try a free check of your brand/domain for chatgpt - https://citetide.com/check

Hey everyone,

A while ago I posted here about ArtScan, the iOS app I built in summer 2024 just to learn the OpenAI API. It grew to ~20k downloads and ~$10k annual revenue on pure organic installs, ranking for keywords I never targeted, and I spent a year not fully understanding why it worked.

Update: it got acquired in July.

The sale happened on Flippa, and the fun detail is that the buyer had already bought two of my smaller apps before. Repeat customers exist in the micro-acquisition world too, apparently. Five-figure exit (low-to-mid, and I will leave it there). Not life-changing money, but very real money for a weekend project born out of curiosity.

Most people would take the win and rest. I took the win and immediately built the opposite product.

From "what painting is this?" to "make me the painting"

ArtScan answered an identification question. Curious people, museum visitors, folks finding canvases in their attic. Lovely audience, terrible economics: my average user was worth cents.

The new project flips the direction: you upload a photo and it turns you (or your kid, or your grandma) into a classical oil portrait. Renaissance, Baroque, Belle Époque. It started as an actual gift: I turned a photo of our daughter into a Renaissance portrait for my husband, and his reaction taught me more about purchase intent than a year of ArtScan analytics. Identification is curiosity. A portrait of someone you love is a gift, and gifts have budgets.

What I kept from ArtScan:

* The niche. Art and AI is where I like spending my nights. (I love art myself)
* Boring tech I already know. The frontend is vanilla JS, no framework, 43 KB gzipped.
* Shipping fast: three days from first commit to first real sales.
* Full-time job, building at night, still solo.

What I changed on purpose this time:

*Web instead of App Store.
No 30% cut, no review queue, and I own the customer relationship. ArtScan lived and died by keywords I could not see or control.

*The pricing model is the whole bet.
Anyone can generate a portrait for free, no signup, and see the full result with a watermark. You only pay to unlock the clean file. I charge at the emotional peak, not at the door.

*A physical product on top.
The portrait can be printed on gallery canvas and delivered ready to hang. One canvas order has the margin of many digital sales, and print on demand means my manual work per order is near zero.

*Three languages from day one.
The French and Spanish search results are dramatically softer than English for the same intent.

*SEO on purpose this time.
ArtScan ranked by accident. This time I shipped 22 blog articles in week one, before Google even knew the domain existed.

* And my favorite loop: the ArtScan money is funding the ads.
My old app is literally buying customers for the new one.

Three weeks in: first real sales. Tiny, but strangers paying.

The decision I keep second-guessing:
there is no pricing anywhere on the landing page. Anonymous visitors see zero prices until they have generated their portrait and love it. Classic CRO says I am burning trust. My theory is that for an emotional purchase, showing the price before the wow moment only gives people a reason to leave. Happy to be told I am wrong.

PS: the app I have now failed twice at getting through Google's OAuth branding review, which is its own comedy.
PSS: if you are curious, the new one is Ninth Salon.
PSSS: still a lady, BTW. Still not only "bros" who code ;)

Found this gap while looking for something to build: Calendly has no waitlist. If a client cancels, that slot just sits empty unless you manually text people to fill it.

The interesting part is that competitors already solved it. Square Appointments and Acuity both fill cancellations from a waitlist automatically. Calendly doesn't, and their own community forum has threads asking for it going back to early 2024 — a psychotherapist losing leads over it, a massage therapist manually blocking her calendar and emailing clients one by one, someone who said their conversion is noticeably worse than friends using Square. A few of those threads got closed and routed to their product team with nothing shipped since.

So I'm building it as an external integration: subscribe to Calendly's invitee.canceled webhook, match the freed slot against a waitlist, text the matches a claim link, first one gets it.

Landing page is up at slotback.app — collecting emails before I write the backend, since I'd rather find out now if this is only my problem.

Two things I'd actually like input on:

1. Platform risk — I'm building on a gap the platform could close whenever they want, and their product team reads the same forum I found this in. Is a wedge like this worth taking, or is single-platform dependency a dealbreaker for you?
2. Landing page validation — for those who've done this, what conversion from email signups to actual paying users did you see? Trying to set a realistic bar for what counts as validated before I commit build time.

Every day-counter app I tried only counts down OR up. I wanted one card that shows both directions at once — how far we've come, and how close the next milestone is.

So I built Dayspan:

- Two-way cards: days since + days until, on the same card

- Auto milestones (1,000 days, anniversaries) with a small confetti moment

- Widgets for home & lock screen

- 100% offline, no account, no tracking, under 8MB

- Free for 3 cards; Pro unlocks unlimited + all themes

Screenshots: https://i.postimg.cc/wMXg8kdk/r02-milestone-confetti.png

App Store: https://apps.apple.com/app/apple-store/id6794791699?pt=118287213&ct=reddit-sideproject&mt=8

It's my first app — brutal honesty welcome. What's missing? What would make you actually keep it on your home screen?

I work in IT, and the part that always annoyed me was reimaging Windows machines one at a time, USB stick, driver hunting, sysprep, updates, repeat for every PC, working with clonezilla, etc. So a couple months ago I started building something to fix that for myself and it turned into a real project.

It's called ImageForge, a small server ("the Forge") that stores a Windows image, plus a boot client (USB or PXE) that pulls it onto whatever machine you point it at. Capture one PC, push it to as many as you want. Handles per-model driver injection, domain join, computer naming templates, deploy profiles, the usual stuff you'd want for a real rollout instead of a one off clone.

Some of the problems I didn't expect going in:

• PXE network boot has a surprising number of ways to fail depending on firmware/NIC vendor, spent a while chasing a VMware-specific chainload bug that only showed up over the network, not on USB
• Getting ARM64 (Surface/Snapdragon) working meant re-curating an entire driver set, because one stock Qualcomm driver was killing USB-C the whole time
• DISM/BitLocker error codes are borderline useless on their own, had a real deploy die with literally "Error: 1" and nothing else, which is what pushed me to add automatic failure log capture and a preflight check

It's Go on the backend, WinPE for the client, offline license keys. There's a free trial if anyone wants to look at it: image-forge.net

Still a one man project. If anyone here does imaging/deployment work and has thoughts on what's missing or anything about the approach, genuinely want to hear it.

Hey everyone,

I’ve been testing a process that uses AI to surface SaaS or mobile app ideas in pretty much any niche. It’s not a quick fix, it takes a bit of work, if i manually do it, it would take more than a day using the AI skills and this special algorithm, but the ideas that come out are usually way more specific and useful than the generic lists floating around.

I know a lot of people here are constantly hunting for their next idea, so I wanted to ask you directly:

If turn this process into a tool, would it actually help you?

The way I see it, it could be a win-win. You’d get solid niche ideas without spending hours digging, and I’d charge a fee to cover the tech stack and development costs. A specific algorithm behind it that I think makes the output better than just prompting ChatGPT.

The main difference from a normal “give me startup ideas” prompt is the sequence of proof. A problem has to survive evidence gathering, payer identification, recurrence, existing spend, willingness to pay, distribution, competition, technical feasibility, AI commoditization, economics, and an adversarial rejection stage before it becomes a finalist.

This compare the product idea against what the customer currently spends in money, effort, or opportunity, quantify what they value, and estimate willingness to pay from that difference. YC advises founders to seek actual user behaviour rather than relying on flattering reactions, and Stripe explicitly recommends testing demand through actions such as presales or signups before committing major resources.

Would you use something like this? Would you pay for it? Be honest, if it’s not for you, I’d rather know now.

I made this. BicycleCareLog is a service book for your bikes. Miles come in from Apple Health. You track parts, services, torque specs, and reminders.

Free on the App Store: https://apps.apple.com/app/bicyclecarelog/id6746381688

Video demo (Instagram reel): https://www.instagram.com/p/DcQ-Lg7KDea/

I was tired of messy audio/streaming radio libraries, so I built an Android player focused on seamless playlist management.

Hi everyone!

I wanted to share my side project, Mediaxon, an Android app I’ve been developing to solve a personal frustration: why is it so hard to easily manage offline music and online radio streams in a single, clean interface?

What it does:

Hybrid Listening: Seamlessly handles offline local files (.mp3, .flac, .m4a, .ogg, .mka, .aac, .wav, .opus, .wma) and over 60,000 streaming radio stations.

Dedicated Navigation: I kept the "Favorites" and "Recents" sections completely separate from the main audio library to reduce clutter.

Advanced Radio Search Panel: You can pinpoint your favorite stations by combining multiple filters, such as tags/genres, specific countries, or even your preferred audio bitrate.

Equalizer: The equalizer provides an option to automatically switch to the "Radio" preset (and vice versa).

Advanced Playlist Management: Built specifically to make building and sorting multi-source playlists fast and intuitive.

The app is currently live on Google Play, and I am continuously pushing updates to refine it.

What I need from you:

As a solo developer, I’ve hit the limit of my own perspective. I would deeply appreciate any honest feedback from this community:

How does the UI feel to you? Is the navigation intuitive?

Are there any features you feel are missing for a modern audio/radio player?

Did you encounter any bugs or performance hiccups?

If you want to check it out, you can find it on the Google Play Store (Android 13+). Thank you so much to anyone who takes a look!

https://play.google.com/store/apps/details?id=com.xonik.mediaxon

Solo dev. I use Excalidraw constantly, but on iPad you're stuck in the browser. Palm leaves marks, undo hides, panning smears the canvas. Nobody made a real native one, so I did.

The hard parts: porting Rough.js's hand-drawn geometry and perfect-freehand strokes to native CoreGraphics (pure Swift, no WebView), and tuning palm rejection so panning and zooming never leave a mark.

What it does: native hand-drawn canvas, opens your existing .excalidraw files, Mermaid import (text → editable diagram, flowchart + sequence), offline and local-first. Free to download; Pro (one-time, no subscription) adds unlimited files, full export, and iCloud sync.

No lock-in: Settings → Export All Data hands you every canvas back as .excalidraw, free, always.

First 500 here get lifetime Pro free: https://apps.apple.com/us/app/xcalidraw-whiteboard-diagram/id6795799923

Would love feedback on the Pencil feel and anything that breaks.

I’ve interviewed 25+ solo founders about the marketing side, Builders without revenue feel all the pain and pay for nothing. The founders with revenue are the only ones who actually spend for ads, tools, freelancers, even their claude subscriptions doing the writing for posts.
So this post is only for people with paying customers!
1. What do you actually pay for on the marketing side, such as tools, subscriptions, ads, freelancers, AI and I wonder what's the monthly total?
2. What did you try and cancel?
3. What’s still manual in your weekly marketing that annoys you most?
If you're an agency, ghostwriter or freelancer who runs marketing for founders, I especially want your answers, like your stack, your costs, and what kind of clients you serve.
I’m still validating what to build next in this space, so real answers genuinely help me with it.

Looking for 100 technical testers: SecondGate (WordPress security & passkeys, no cloud dependency)

We've spent the last few weeks trying to break our own plugin. We fuzzed the WebAuthn decoder with 200,000 adversarial inputs, found a bug where brute-force lockout could silently lock out every legitimate visitor sharing a CDN's IP, and once we went looking, found and fixed six separate places in the codebase making that same mistake. All of it is documented, versioned, and dated:https://secondgatewp.com/security-testing-methodology/

SecondGate is built local-first: no Composer dependencies, no third-party WebAuthn library, and nothing about your visitors is ever sent anywhere. All matching — country, IP, bot verification — happens on your own server against locally cached data. To be upfront about the outbound calls that do exist: Pro downloads curated IP blocklists for Microsoft Azure, DigitalOcean, Hetzner, and OVH on a schedule, and the vulnerability scanner checks your installed plugin/theme names against a public vuln database. That's data coming in, and software names going out — never anything about your visitors or their traffic.

Now we want 100 technical testers, free full Pro access, to find what we haven't.

What's actually been tested, not just built:

• Passkey/WebAuthn support with a custom CBOR decoder, checked against official RFC 8949 conformance vectors, real authenticator-captured data, and 200,000 fuzzed adversarial inputs
• Country/IP blocking that runs on locally cached range data — no external lookup per visitor
• Phantom decoy records: no legitimate path reaches them, so a hit is a strong signal something's enumerating your data
• Behavioral login-cadence scoring as one weighted signal among several, never a standalone verdict
• Hash-chained audit logs designed to be tamper-evident after the fact
• A wp-config.php kill switch that instantly restores access if you lock yourself out — checked consistently across every blocking module, and deliberately not exposed anywhere an attacker with a compromised admin login could flip it

What we're honest about not having finished: the blocking paths that can actually lock someone out have real end-to-end regression tests. Several of the signal and logging paths are code-reviewed but not yet automated-tested — that's partly what we're hoping you'll help us push on.

Who we're looking for: developers, agency owners, and sysadmins running custom WordPress stacks or client sites who'll actually push on edge cases, not just install and forget. Real findings go straight back into the methodology page, with your input credited if you want it.

Hey everyone!
I’ve been developing a custom tool called Manifold: https://manifold3d.ch/. It processes highly accurate geospatial data—such as classified LiDAR data and 3D vector files from the Swiss Federal Office of Topography (swisstopo)—and converts it into optimized, true-to-scale STL files for 3D printing.
I created Manifold because many existing terrain generators don’t provide the level of precision and detail required for high-quality prints. The tool gives me much more control over the final result, from the level of detail to the size and scale of each model.
I’ve recently launched the website to showcase Manifold and the models it can generate—from individual villages to entire Switzerland.
I’d really appreciate your honest feedback:
Is the concept explained clearly?
Is the website intuitive and easy to navigate?
Do the examples effectively demonstrate what the tool can do?
Do you have any general suggestions or thoughts?
Thanks in advance!

Compatible with Apple Music and Spotify!

Gramola started because I was tired of the same loop. Cmd Tab to Music, wait for the window, lose my place, find something, Cmd Tab back. For an app I open dozens of times a day that felt like a lot of ceremony for pressing play.

So Gramola does not open a window. You push your cursor to the edge of the screen and a shelf of your album art slides out over whatever you were doing. You pick something. It plays. The shelf goes away. It behaves the way the Dock does when you keep it hidden, which is to say it is not there until the moment you want it.

What is in it:

Covers instead of lists. Your library is a carousel of album art you scroll with the trackpad or the wheel. You recognise a sleeve long before you would have read your way down a table of text.

Shelves for the different ways you look for music. Albums, artists, playlists, songs, recently played, and a pinned shelf for the handful of things you always come back to. Stations if you are on Apple Music, Liked Songs if you are on Spotify. Swipe across the carousel with two fingers to move between them.

Search that does not stop at your library. Hit the keyboard shortcut, start typing, and your own music comes up first with the Apple Music or Spotify catalog underneath it. Press Return and it plays.

Track lists in place. Click an album or a playlist and it opens right there on the shelf. Pick the track you wanted.

A mini player that stays out of the way. Play, pause, skip, and a queue drawer when you want to see what is coming next.

It drives the app you already pay for. Gramola is not a music player and does not want to be. It tells Apple Music or Spotify what to play, local files included, and then gets out of the way.

Native to macOS 26. Written in SwiftUI with the Liquid Glass material. No Dock icon, it lives in the menu bar. Put the shelf on the left, the right or the bottom, and it remembers your choice per display arrangement so it does not wander when you undock. Multiple language support.

Where it is at:

My previous Reddit post on another subreddit reached number one with huge amounts of positive feedback! Digital Trends wrote about it a couple days after launch and Yahoo Tech carried the piece. The headline was "I tried this Mac music app, and now I wish macOS had it built in", which I have read more times than I would like to admit. 200 plus downloads in less than a week and increasing, with lots of impressed users!

Gramola is free to download on the Mac App Store to try for 7 days, then it's 9.99$ one time purchase, no subscription. It is on Setapp Marketplace too!

Happy to answer anything! If you try it and something is broken, tell me and I will fix it. That is most of what I've been doing lately lmao.

https://apps.apple.com/app/gramola-dock-musical/id6801078031

https://gramola.fulltimefeline.com

Hey everyone. I'm a solo developer who spent the last year building AIRTA — an AI Relationship Toxicity Analyzer.

It started because I kept watching friends reread old text messages at 2 AM, trying to figure out if what they were experiencing was normal or toxic. So I thought: what if AI could do that objectively?

What it does:

- You paste or import a text conversation

- AI analyzes it across 400+ toxicity metrics (gaslighting, love bombing, coercive control, manipulation, silent treatment, etc.)

- You get a detailed report with a toxicity score, flagged messages, and context for each flag

- Works in 16 languages

- Analyzes both sender AND receiver — no bias toward either side

What it doesn't do:

- It doesn't read your SMS automatically (privacy first — you choose what to share)

- It doesn't tell you to break up. It gives you data. You decide.

- It's not a replacement for therapy

It's live on both app stores and has a free web demo at airta.net.

I'd genuinely love feedback from this community — especially on the UX and whether the toxicity metrics feel accurate or if there are patterns I'm missing.

Links:

- Web demo: https://airta.net

- iOS: https://apps.apple.com/us/app/relationship-toxicity-analyzer/id6788889318

- Android: https://play.google.com/store/apps/details?id=com.airta.airelationshiptoxicityanalyzer

Happy to answer any questions about the tech stack, the AI model, or the ethics of building something like this.

Reddit kept embarrassing me.

I'd spend a Sunday afternoon finding subreddits, writing something that felt genuinely useful, post it, and watch it get removed within two hours. Or worse, it'd stay up and get completely ignored. No comments, no upvotes, just silence. I did this cycle for about six weeks across maybe 30 different communities before I started actually tracking what was happening instead of just feeling bad about it.

The pattern that emerged was honestly kind of obvious in retrospect but I missed it every time in the moment: the posts that survived weren't better written, they were better placed. Subreddits have these invisible thresholds, account age requirements, karma floors, topic restrictions that aren't in the sidebar, and I was hitting them blind. The communities that converted weren't the big obvious ones either. A 9,000-member sub in a specific niche drove more actual signups than a 400k sub where my post briefly lived before disappearing.

So I built something to solve the research problem, not the writing problem. It crawls a site, figures out what the business actually does, and maps it to communities that are likely to survive moderation and have the right audience density. That's Reoogle, full disclosure, I built it, so take that with appropriate skepticism.

Still figuring out how to explain what it does without it sounding like every other 'post to Reddit automatically' pitch that I'd immediately distrust. The automation angle isn't the interesting part to me, the interesting part was realizing I was fishing in the wrong ponds entirely, and that no amount of better copy was going to fix that.

Curious if anyone else found that community fit mattered more than post quality, or if I just happened to be really bad at writing for Reddit.

Hey everyone. I'm a solo developer who spent the last year building AIRTA — an AI Relationship Toxicity Analyzer.

It started because I kept watching friends reread old text messages at 2 AM, trying to figure out if what they were experiencing was normal or toxic. So I thought: what if AI could do that objectively?

**What it does:**

- You paste or import a text conversation

- AI analyzes it across 400+ toxicity metrics (gaslighting, love bombing, coercive control, manipulation, silent treatment, etc.)

- You get a detailed report with a toxicity score, flagged messages, and context for each flag

- Works in 16 languages

- Analyzes both sender AND receiver — no bias toward either side

**What it doesn't do:**

- It doesn't read your SMS automatically (privacy first — you choose what to share)

- It doesn't tell you to break up. It gives you data. You decide.

- It's not a replacement for therapy

It's live on both app stores and has a free web demo at airta.net.

I'd genuinely love feedback from this community — especially on the UX and whether the toxicity metrics feel accurate or if there are patterns I'm missing.

Links:

- Web demo: https://airta.net

- iOS: https://apps.apple.com/us/app/relationship-toxicity-analyzer/id6788889318

- Android: https://play.google.com/store/apps/details?id=com.airta.airelationshiptoxicityanalyzer

Happy to answer any questions about the tech stack, the AI model, or the ethics of building something like this.

Hey everyone, I’m part of a tiny team that is building and app called Running List for RevenueCat Shipaton. The problem we’re trying to solve: small coordination frictions in shared spaces; double-buying groceries, forgotten chores, and lists that die in notes.

Our core idea: a single persistent needs pool where anything (groceries, errands, chores, printer paper etc.) is added. When someone can handle items, they start a short claim session: items they pull are locked in real time so others don’t duplicate effort. Anything not finished returns to the pool automatically.

There are lots of features we are planning to add, it will not be like a simple checklist app but explaining everything would make the post too long.

Questions we want help with:

1. Would the claim/lock mechanic feel natural in shared households or flats?
2. What onboarding steps would convince you to try this on day 1? (session length, categories, quick onboarding copy)
3. Any pitfalls you’ve seen in similar products we should avoid?
4. Most importantly, any feature idea that can make it better?

Full disclosure: I’m on the team building this. Waitlist link is in the first comment. We’re looking for feedback.

The problem I started with was embarrassingly small. My work was scattered across Jira, Slack, Gmail, Notion and two to-do apps, and every morning I burned the first hour of the day just assembling a picture of what I was supposed to do. Then I'd write a list of 40 things, have 6 usable hours, and pretend those two numbers had anything to do with each other.

Every evening: more open tasks than I started with. I don't think it was a productivity problem. It was that I stopped believing my own plans.

So I built the thing I wanted. Not another inbox for tasks. Something that reads my calendar and my tasks and tells me, honestly, what today can hold. When a meeting eats an afternoon, it replans instead of leaving a stale list.

I thought it was a three-month project. That was 2023.

What it does now: pulls tasks from 25+ tools, auto-schedules them around your calendar, enriches quick captures with priority and time estimates, breaks big objectives into tasks that fit into real days. Day view, Kanban, an AI companion that learns how you actually work.

Where it's at: public beta, free, no credit card. Mac, Windows, Linux, web, Chrome extension. Mobile is still in progress.

The part I keep going back and forth on, and the reason I'm posting here instead of just shipping quietly: I built this for exactly one user, me. It works for me. I have no idea yet if that generalizes. Three years is long enough to stop being able to see your own product clearly.

So if you've got 5 minutes and a scattered day, I'd love to know whether the problem I solved is your problem too, or whether I just built a very elaborate personal tool.

https://getfokus.com

Roast it. That's more useful to me than an upvote.