Product Hunt 每日热榜 2026-08-03

PH热榜 | 2026-08-03

#1
AgentSky
Any harness, any LLM — cloud-hosted agents on demand.
392
一句话介绍:AgentSky 是一个托管的智能体平台,让你通过一键点击或CLI,在云端沙箱中启动Claude Code、Codex等长时运行AI代理,并统一接入WhatsApp、Slack、Web等渠道,解决自建代理基础设施复杂、难以跨渠道持续运行的痛点。
SaaS Developer Tools Artificial Intelligence
AI代理托管 MaaS(智能体即服务) 云端沙箱 多模型接入 多渠道集成 长时任务 无服务器计费 开发者工具 基础设施即服务 对话式AI
用户评论摘要:用户普遍认可“仅按运行时长计费”和跨渠道共享上下文的功能,认为这是实用创新。核心疑问集中于:死寂代理与空闲代理的区分(健康检查机制)、状态快照恢复时外部副作用(如已发送消息)的重放风险、以及多用户并发时沙箱的安全与弹性扩展能力。也有用户建议补充更多真实案例。
AI 锐评

AgentSky的聪明之处在于它没有试图再造一个更聪明的“大脑”,而是选择去做“神经系统”和“生命维持系统”——这恰好是当前AI代理从Demo走向生产环境时最肮脏、最费力不讨好的环节。它把异构Harness(Claude Code、Codex等)、多模型切换、状态持久化、跨渠道消息路由打包成一种“基础设施”,本质上是在押注一个趋势:未来的AI竞争不在模型层,而在编排与可靠性层。

从评论反馈看,它确实戳中了开发者的痛点,尤其是“暂停/恢复”计费模式和跨IM的连续对话,这比单纯卖API Key更具吸引力。然而,评论区中创始人坦诚承认“状态恢复是尽力而为,无法避免竞态条件”,这暴露了产品目前的底线:它解决的是95%的常规场景,但对金融、医疗等需要强事务保证的场景缺乏说服力。此外,跨渠道的“同一记忆”虽然酷炫,却也放大了幂等性问题——如果快照恢复到发送消息之前,用户可能收到重复的WhatsApp通知。这是一个介于“基础设施”和“应用层”之间的灰色地带,AgentSky试图将其封装,但最终责任可能还是会落到开发者头上。

总体而言,AgentSky在“让代理活下来”这个维度上提供了有价值且定价合理的服务,10K+会话的实战数据也为其增加了可信度。但它目前的护城河并非技术壁垒,而是对开发者体验的整合深度。随着AWS等巨头推出类似组件,这种独立中间层的生存空间将取决于它能否在事务性、可观测性上建立真正的标准,而不是仅仅做一个“万能适配器”。在模型快速迭代的当下,这种“卖铲子”的逻辑是稳妥的,但铲子需要足够坚硬。

查看原始信息
AgentSky
Managed agent as a service: launch a long-horizon AI agent in one click — Claude Code, Codex, Hermes, or OpenClaw — with full history, managed recovery, and access through WhatsApp, iMessage, Telegram, Slack, web, API developers, and CLI.

Hey Product Hunt! 👋

I built AgentSky because production-ready AI agents require far more infrastructure than most people expect. The idea came from building tycoon.us, where we ran into the same challenges: testing multiple harness/LLM combinations (let alone harness version updates 😱), fast & secure sandboxes, surviving restarts, and connecting them to every channel users expect.

AgentSky does that plumbing for you. Pick a harness — Claude Code, Codex, Hermes, or OpenClaw — pick a model, and launch in one click, or a CLI command. Your agent runs always-on in its own cloud sandbox with full history, artifacts persistence, state snapshots, backup and restore.

It's reachable wherever your users already are — WhatsApp, iMessage, Telegram, Slack, web, CLI, or our developer API's. Same protocol, same memory, every harness, every channel.

Already battle-tested in production, AgentSky powers tycoon.us, where it has handled over 10K+ agent sessions.

Parking an agent is free — you only pay when it's actively working.

Would love your feedback, especially on which runtimes and channels you'd want next!

12
回复

@darren_y_lu I have a feeling this is going to resonate with a lot of builders.

What caught my attention is that AgentSky isn't trying to build another agent—it's building the infrastructure that lets agents actually survive in production. That's a much less glamorous problem, but probably the one that determines whether an AI product scales or falls apart after the demo.

I also like the flexibility of mixing different harnesses, models, and communication channels. It keeps developers from betting everything on a single ecosystem, which feels like a smart long-term decision in how quickly this space is evolving.

The fact that you've already battle-tested it with 10K+ sessions on tycoon.us also gives the product a lot more credibility than infrastructure built only in theory.

Here's what I'm most curious about: after running thousands of real agent sessions, what has been the biggest bottleneck? Is it the models themselves, the surrounding infrastructure, or simply getting users to trust an agent enough to let it work independently? I'm looking forward to seeing how AgentSky evolves from here. 👏

0
回复

@darren_y_lu keeping the same memory across WhatsApp, Slack, and the CLI sounds useful

0
回复

@darren_y_lu Congrats on the launch Darren! Any tool that strives to reach people where they are is a win, thank you "WhatsApp, iMessage, Telegram, Slack, web, CLI"

1
回复

Suspend and resume is the interesting part, and I think it has a blind spot worth designing for now rather than later.

If parking is free and I only pay while the agent is working, then an agent that has quietly stopped working costs me nothing. Which is lovely, right up until a dead agent and a cheap month look identical on the invoice. For long horizon work the bill has historically been the thing that told people something had gone wrong, and this pricing removes that signal on purpose.

From outside, a suspended agent, a finished agent, and one that crashed and never resumed all present the same way. No activity, no cost, nothing in the channel. So what tells the operator which of the three they have? What I would want is for a long horizon agent to declare an expected cadence when it launches, so the platform can say this one should have woken by now and has not, instead of leaving silence to mean whatever the reader assumes it means.

Second one, and it falls out of snapshots combined with messaging channels. If you snapshot state and restore it, what happens when the snapshot was taken partway through an external side effect? An agent restored to a point just before it sent a WhatsApp message cannot tell whether that message went. Redoing it and skipping it are both wrong, and only one of those is visible to the person on the other end, who receives it twice.

Do side effects get recorded outside the snapshot, so a resumed agent knows what already left the building?

6
回复

@dalemooney Great questions!

1. Dead vs idle. Crashed agents fail health check, while idle agents mean that it is healthy but no request incoming to handle. Btw, we have built-in health check for agents.
2. Our state restoring is best effort based, it cannot prevent race condition, but it would at least make the agent remember partially (usually the latest conversation).

What you brought up is very meaningful and sophisticated. I also believe that each product may have different opinions on these behaviors.

2
回复

Love the pay-only-when-working model, that's a smart pricing call.
Curious how you're handling security across sandboxes when agents are running always-on like that?

4
回复

@abod_rehman Great question! The agents are not always on in AgentSky, they suspend/resume base on work load. The sandboxes are based on MicroVM so that it is secure by standard and also fast to boot. Is there any particular security concern your product may care about?

3
回复

This is exactly the kind of infra headache people underestimate until they hit it.
How long did it take you to get restart working reliably across different harnesses?

3
回复

@boyuan_deng1 We dealt with these challenges for months, going back and forth on infrastructure. Eventually we realized this is a problem that deserves its own platform—not something every product team should have to solve from scratch. Do you think this would save your time if you were to build agent product?

2
回复

congratulations! can agents communicate with users across multiple channels simultaneously? for example, could an agent start on Slack and continue the same conversation on WhatsApp?

2
回复

@daniel_harris11 
> could an agent start on Slack and continue the same conversation on WhatsApp?

Yes, that is what we do. Internally AgentSky agent handle all channels uniformly. This is the magic that it can maintain continuous context among channels. This is a feature we needed at our own agent product before, so that we built it.

2
回复

I like that AgentSky puts different models and agent tools in one place. It could save a lot of time when testing ideas, especially for people who don’t want to set up everything themselves. I’d still like to see more real examples before using it for a bigger project.

1
回复

@letitia00 Thanks! Yes, quickly experimenting across different harness/LLM combinations was one of our pain points in the past, that is why we think others may need this too. We have hosted more than 10k agent sessions already in real products.

0
回复

Congrats Darren! The channels part is what sells it for me. I correct my coding agent from the phone mid-run all the time, and that flow is usually held together with duct tape. Curious: when a WhatsApp message lands while the agent is mid-task, does it interrupt the run or queue until the current step finishes?

1
回复

@artem_t Thank you! For now, we support 2 modes, please check out https://agentsky.dev/docs/api

  1. you may request interrupt + another input message (interrupt first, then handle the new message)

  2. you may just send another input message which will be queued

0
回复

Congratulations on the launch!
I like the idea and after reading comments i like that context is shared between agents and channels as well as you don't pay if the agent is not used. I would like to try it next dayse with with some of my tasks.

1
回复

@nkrasko Thanks! Please feel free to join our discord (from landing page) and let me know if you need support

0
回复

Saying state restore is best effort and cannot prevent a race condition is rare on a launch day. You mentioned wanting idempotent agent replies in your own layer. Where do you think that line sits between the infra and the product on top, Darren?

1
回复

@lucasjpols Appreciate the feedback! An analogy I would use is DB backup/restore, there would be no guarantee on a perfect restore with absolute no loss of rows. For most product user cases, I do feel this is sufficient, considering that agent crash should not be a high frequent event. We are still trying to put more common product concerns into our infra layer, while still let developers to keep their own part.

0
回复

Reaching a long running agent from WhatsApp or iMessage instead of yet another dashboard feels like how normal people would actually use this. Congrats Darren, the 10,000 plus sessions on tycoon.us before launching is reassuring too. What does recovery look like when an agent goes sideways, can I roll back to any earlier snapshot?

1
回复

@doganakbulut Yes, that is what we do for developers automatically, if crash happens, restoring from snapshot will happen immediately.

0
回复

Can AgentSky automatically scale when multiple users start interacting with the same agent? how do you handle sudden spikes in agent sessions?

1
回复

@dylan_russell 

Can AgentSky automatically scale when multiple users start interacting with the same agent?

multiple users get their own sessions with same agent (same MDs, same skills, same capabilities)

how do you handle sudden spikes in agent sessions?

Under the hood, we have an elastic sandbox infra which can handle new agent sandbox requests on demand.


0
回复

If you had to recommend one harness for someone building their first long-running agent, which one would you suggest, and why?

1
回复

@samra_habib1 I would suggest Hermes for maximum compatibility of open weight models and no vendor lock-in.

0
回复

congrats! can developers choose different LLM models for the same harness? how quickly can you switch models without changing the agent configuration?

1
回复

@carter_garcia Thanks!

can developers choose different LLM models for the same harness?

Yes, for compatible ones.

how quickly can you switch models without changing the agent configuration

Switching models is considered changing agent configuration. It takes about ~5 sec to deploy the new change.

0
回复

I like that agents stay available across WhatsApp, Slack, and the web. Meeting users where they already work makes a lot of sense.

1
回复

@daniel_henry4 Yes, we spent a lot of time figuring out channels.

0
回复

what runtime or channel are you most excited to add next? are you prioritizing integrations based on community requests or technical demand?

1
回复

@colton_drake I think we're aligned with the trend toward open-weight frontier models, where we're seeing growing demand. Over time, we'd like to support as many stable harnesses and models as possible.

0
回复

Congrats on the launch!
What does the developer API expose compared with the CLI? can teams programmatically create, pause, resume and manage agents?

1
回复

@easton_carter Thanks! Our developer API is basically feature parity to CLI. We gave both options just for convenience, sometimes CLI is a bit more favorable for quick test/demo. For developers, they can use either our REST API or CLI to automate the AgentSky fleet management. Quick start https://agentsky.dev/docs

0
回复

how does AgentSky handle failed or partially completed tasks? can an agent resume from its previous state instead of starting over?

1
回复

@luz_bidelspach AgentSky does recover into latest state from crash. We do not "starting over" any tasks when agent recovers from context backup.

0
回复

congrats! can one agent use different models depending on the task it is performing? for example could it use a cheaper model for simple tasks and a stronger one for complex reasoning?

1
回复

@olivia_bennett7 Thanks! AgentSky does not support harness/model routing, but it is indeed on our roadmap. Do you have any suggestions on what routing framework we should look into?

0
回复

The biggest challenge I see with multi-channel agents is maintaining context. If someone asks a technical question in a community forum today and follows up with the same issue in a private chat tomorrow, how does the agent know it’s the same user and the same problem?

Is the conversation history unified at the agent level, or does each platform maintain its own separate memory?

1
回复

@new_user___140202597473f65134ed0cb Great question. In AgentSky, conversation history is unified at agent instance level, so yeah it is agent level, not per channel. We designed the system so that a single agent can talk to multiple channels at the same time.

1
回复

The multi-channel consistency is the part I want to understand better. If a user starts a thread on Telegram and then messages from Slack the next day, does the agent see a single unified conversation or two separate sessions? For developer communities I manage, people switch channels constantly and that is usually where context breaks happen.

1
回复

@hazy0 Great question. In AgentSky, a single agent session can be shared on multiple channels, but it will only reply to the channel where request was sent. And the session context are all shared for same agent session. We designed specifically for cross-channel smooth experience. Do you think this behavior is the common denominator for most products?

2
回复

how does pricing work when an agent is parked but still maintaining its state? is there any cost for storage, snapshots or backups while it is inactive?

0
回复

@rivendell_chorro We use a ultra low cost solution for parked agent state. So there will be hot restore and cold restore based on the agent activeness. There will be cost for storage in general, as long as the agent had created artifacts that is in ours system.

0
回复

Congrats on the launch! 👏
How does AgentSky handle failed or partially completed tasks? can an agent resume from its previous state instead of starting over?

0
回复

@fletcher_oliver Thanks! We snapshot context sessions while agent is running. If an agent crashed, it will resume from previous snapshot, not starting over.

0
回复

The cross-platform memory is the part I’m most curious about. If a user starts debugging a problem through Discord, then continues the conversation through email or a support portal later, does the agent maintain the same context and history, or does each channel create an isolated session?

For developer communities, users rarely stay on one platform, so I’m wondering how agents handle context continuity when conversations move across different channels.

0
回复

@new_user___176202668afdbb135b4f71f 
> If a user starts debugging a problem through Discord, then continues the conversation through email or a support portal later,

The conversation will be continuous for AgentSky agents.

0
回复
#2
Ctruh Studio
Create interactive 3D and XR experiences without coding
360
一句话介绍:Ctruh Studio是一个AI驱动的无代码平台,让用户直接在浏览器中创建、定制并发布交互式3D和XR购物体验,将平面产品页转化为可旋转、配置和AR试用的沉浸式场景,无需编程或安装插件。
Artificial Intelligence Augmented Reality No-Code
无代码3D创作 AI资产生成 增强现实(AR) 沉浸式电商 3D产品展示 虚拟商店 网页XR 实时3D渲染 产品配置器 虚拟试穿
用户评论摘要:用户普遍认可AI生成有机形状(如植物)的能力,以及材质编辑器对陶器釉面质感的还原度。核心痛点集中在批量编辑变体(当前仅支持逐一操作,官方称已列入路线图)和移动端性能优化上,官方回应称已实现设备自适应及8K-16K高效流送。新手用户反馈上手快,几分钟内即可创建试穿体验。
AI 锐评

Ctruh Studio的定位精准地切入了“3D电商最后一公里”的痛点——资产生产与工具链断裂。其真正的护城河并非浏览器端3D引擎(WebGL/WebXR已是成熟技术),而是“VersaAI”将文本/图片生成可生产级3D资产的能力,这直接抹平了商家从2D照片到3D展示之间最高的转换门槛,相当于为电商平台预装了一个“内容生成器”。从用户反馈看,材质表现(粗糙度/反射率)和有机模型生成已被验证为有效卖点,这比空谈“沉浸式体验”更有说服力。

但必须指出,评论区的“叫好”存在明显的创始人及团队自答或官方互动痕迹(如多条评论的深度回复和内部视角发言),其真实第三方口碑仍需观察。产品切入的电商设计场景(如家具体验)虽然高频,但同时也面临Shopify AR Quick Look等平台原生功能的竞争。无代码降低了使用门槛,但在企业级场景中,与现有CMS/ERP的集成、SKU批量管理(用户已反馈批量编辑缺位)以及后续资产版权问题,才是决定其能否从“体验玩具”升级为“商业基础设施”的关键。若批量编辑和模板生态能按期兑现,其一体化价值将凸显;否则,容易被单一环节的垂直SaaS工具蚕食市场。

查看原始信息
Ctruh Studio
Ctruh Studio is an AI-powered no-code platform that lets anyone create, customise and publish interactive 3D experiences for websites. Generate 3D assets with AI, build immersive product showcases, virtual stores, configurators and AR experiences directly in your browser.
Hey Product Hunt 👋 Sharun here, Director of GTM at Ctruh, posting on behalf of our founder & CEO Vinay (he'll be here through the day too). The problem: online shopping is still stuck in 2D. People spend real money on products they've only seen as flat photos, so they hesitate, buy the wrong thing, and send it back. The fix, letting shoppers see, configure, and try before buying, has always meant hiring developers, stitching five vendors together, and waiting weeks. Most brands want immersive experiences. Almost none can justify the cost. Studio by Ctruh is our answer: an all-in-one, browser-native platform for building immersive 3D, XR & AI shopping experiences, with no code, no plugins, no downloads. It turns flat product pages into experiences customers can explore, configure, and try on, all from a single link: - VersaAI turns text or an image into a production-ready 3D model in minutes - 3D visualizers let shoppers rotate, zoom, and inspect from every angle - Virtual try-on & AR place products in a customer's space, or on themselves - Configurators switch colors, materials, and variants - Virtual storefronts build immersive shopping environments, no code Why Ctruh over the tools that already exist? Three reasons: - Genuinely all-in-one: one asset library, one CMS, not five glued-together vendors - Browser-native engine: instant load, nothing to download, works on any device - AI-native, not AI-added: VersaAI removes the biggest bottleneck by generating the 3D assets for you Weeks of specialist work become minutes for one person. We'd love your honest feedback: if you sell online, what's actually stopped you from trying 3D or AR until now — cost, tooling, asset creation, or something else? We built Studio to remove exactly those blockers. Try it free with launch credits 🚀 Vinay, the team, and I are all here — ask us anything!
31
回复

@sharun_kanan honestly, today feels surreal.

Most of us joined because we believed the browser could do what apps and headsets were promising, without the friction. Watching 3.6 years of engine work turn into something anyone can open from a single link never gets old.

What I'd tell the PH community: don't take our word for it, click into one of the live experiences and try rotating, configuring, trying on. The "wait, this is running in my browser?" moment is the whole product.

18
回复

@sharun_kanan Congratulations on the launch, this is an excellent product.

2
回复

@sharun_kanan For someone selling online today: if you could wave a magic wand and fix one part of the shopper’s journey, what would it be and how would you measure if Studio actually moved that metric for you?

0
回复

I didn't expect the AI asset generator to handle organic shapes this well. My plant models actually look like plants.

21
回复

@madison_marley "My plant models actually look like plants" might be my favorite sentence of the whole launch 😄 Organic shapes are genuinely one of the hardest things for AI 3D to get right, hard-surface stuff like a box or a bottle is forgiving, but anything with irregular, natural geometry usually falls apart. So hearing plants hold up means a lot.

If you keep pushing it, I'd love to know where it starts to struggle, the trickier the organic shape, the more useful your feedback. And genuinely, thank you for trying the thing most likely to break and telling us it didn't. 🌱

10
回复

Vinay here, founder & CEO of Ctruh

I started this company because I kept watching brilliant products get sold through flat photos that did them no justice. We've spent years on a hard technical bet: that immersive 3D and AR shouldn't require a game engine, a specialist team, or weeks of work. It should be as simple as sharing a link.

Studio is the clearest expression yet of that belief. Seeing it in the hands of the community today genuinely means a lot to our whole team.

I'll be here throughout the day, and I'd love to hear what you think, especially the hard questions. Thank you for spending a moment with what we've built.

20
回复

What stood out to me was the material editor. I run a ceramics shop and getting realistic glaze textures on 3D models used to require outside software. Now I adjust roughness and reflectivity directly in the platform and the results are close enough to real photos that customers stopped asking for extra images.

19
回复

@puja_sharma13 Puja, this genuinely made our morning. "Customers stopped asking for extra images" is the exact outcome we hoped the material editor would unlock, that's the whole point of getting roughness and reflectivity right in-platform instead of round-tripping through other software.

Ceramics is honestly one of the harder cases too, glaze has that subtle depth and sheen that's tough to fake, so hearing it holds up against real photos means a lot.

If you ever hit a texture or finish that doesn't translate well, I'd love to hear about it, edge cases like yours are exactly what push the material engine forward. And thank you for sharing something this specific; it helps other makers here picture what's actually possible.

11
回复

Excited to finally launch this after months of building and refining it with the team.

One thing we kept hearing from brands was that they wanted 3D and AR experiences, but the workflow was too fragmented: asset creation, optimization, hosting, web integration, and customization all lived in different tools.

Ctruh Studio was built to simplify that entire process in one browser-native platform. The goal is to make immersive commerce practical, not just possible.

Would genuinely love feedback from the Product Hunt community on what workflows we should improve next.

19
回复

@anand_ghugare Well said, Anand. The fragmentation point is the whole reason this exists, brands weren't missing the ambition for 3D and AR, they were missing a way to do it without gluing five tools together. "Practical, not just possible" is exactly the bar.

And I'll echo your ask to everyone reading: we genuinely want to know which workflows to sharpen next. If you try Studio today, tell us where it flowed and where it snagged, whether that's asset creation, customization, or getting an experience live on your site. That's the feedback shaping our next few releases.

13
回复

No-code is the right call here. I've spent weekends fighting with Blender just to get a basic product spin working. Being able to build that same thing in a browser changes my whole workflow.

18
回复

@ayesha_mughal1 "Weekends fighting with Blender for a basic product spin" is the exact pain we built this to kill 😄 Blender is incredibly powerful, but you shouldn't need to learn a full 3D suite just to let a shopper rotate a product. That gap is the whole reason Studio exists.

Honestly, the best test is to recreate that spin, the one you used to lose weekends to, and see how long it takes here. Drop in a product (or generate the model from a photo with VersaAI), and you've got a rotatable 3D viewer in minutes, no Blender required. Free launch credits to try it.

Would genuinely love to hear how it compares to your old workflow once you've built one. That head-to-head is the feedback that means the most to us.

14
回复

What caught my eye is the AR piece. I run a small furniture shop and letting customers preview pieces in their own room could cut returns significantly.

18
回复

@sheikh_umair1 You've nailed exactly why we built the AR piece, Sebastian. Furniture is honestly the textbook case: big-ticket, space-dependent, and "it looked bigger online" is one of the top reasons things get sent back. Letting someone place a sofa in their actual living room before buying is the difference between hoping and knowing.

Would genuinely love for you to try it with one of your own pieces, drop in a product (or use VersaAI to generate the 3D model from a photo), then view it in AR in your own space. Takes a few minutes and there are free launch credits.

If you do, I'd love to hear how it holds up with real furniture, scale accuracy especially. That's the feedback that helps us most, and it sounds like your shop is the perfect real-world test.

11
回复
Honestly, still processing that this is live! I joined this team back when Ctruh Studio was barely a prototype, just an idea on a whiteboard and way too many late nights. I remember us saying “you should be able to go from an idea to a 3D scene without opening a single tool you don’t already know” and half the room wasn’t even sure that was actually buildable. Today it just…works. No app, no headset, no waiting on team of specialists. Just a link on a browser. That’s the part that still doesn’t feel real to me. Go check it out. We’d genuinely love to hear what you think.
18
回复

@ivy_bisht This one got me a little, not gonna lie. That whiteboard line ("go from an idea to a 3D scene without opening a single tool you don't already know") was the whole bet, and half the room being unsure it was buildable is exactly why today feels the way it does.

To everyone reading: this is the kind of thing that doesn't come across in a screenshot. Go open one of the live experiences, rotate something, try it on, and see the "wait, this is just running in my browser?" moment for yourself. We genuinely want to know what you think.

15
回复

Anyone found a good workflow for batch editing multiple product variants at once? Doing them one by one is slow.

18
回复

@ado_audu You've pinpointed exactly what's next on our list, Michael. Right now batch editing across variants is one-by-one, which, you're right, gets slow the moment you're working at any real scale. It's genuinely a gap today.

The good news: bulk/batch variant editing is already on our roadmap for our next release, precisely because this friction kept coming up. So you're not missing a hidden setting, it's actively being built.

Would help us a lot if you'd tell me more about your case, how many variants you're typically working across, and what you're changing (materials, colors, dimensions)? That detail directly shapes how we design it. And if you're open to it, happy to ping you when it ships so you can put it through its paces.

11
回复

The product is fabulous! Any brand looking to create 3D assets, or launch a virtual storefront or offer Virtual Try-ons, Ctruh Studio makes it extremely easy to do that.

Even a non-techie like me was able to create a try-on in a matter for few minutes. If you have not already, try it out and have your mind blown!

18
回复

@jagrit_gupta Thanks Jagrit! The "non-techie made a try-on in a few minutes" part is honestly the bar we care about most, if it only works for 3D specialists, we've failed. Really glad it clicked for you.

14
回复

One thing kept coming up in almost every conversation: We love immersive experiences, but they're just too difficult to build.

That became our starting point.

So we built @Ctruh Studio: a platform that lets anyone create and publish interactive 3D experiences for the web without the usual complexity.

We're just getting started, and I'd genuinely love your feedback.

If you get a chance to try it, let us know what you'd build first. Every comment helps us make the product better. 🚀

18
回复

It's amazing to see something we've spent years building finally out in the world.

From the very beginning, our goal was simple: make immersive commerce easy to create and even easier to experience without downloads, plugins, or unnecessary complexity.

If you're visiting us on Product Hunt today, spend a few minutes exploring the live demos. The best way to understand the product is to experience it yourself. We'd love your feedback and support!

17
回复

I'm curious how it handles file size optimization for mobile users. Rich 3D experiences often load slowly on phones. If you've solved that, it's a real edge over competitors.

17
回复

@billy_boy Great question, and it's the one that separates a demo from something a brand will actually ship. A rich experience that takes 8 seconds on 4G loses to the flat photo it replaced.

Straight answer: the experiences are device-agnostic and load beautifully on any device with a browser, budget Android, laptop, kiosk, or headset. And it's not a stripped-down version on phones, shoppers get the same high-fidelity 8K-16K visuals everywhere; the engine just streams and renders it efficiently so it stays fast and smooth whatever they're on. That's the whole point of building it browser-native.

Would genuinely love your eyes on it, you clearly know what "good" looks like here, and that's the feedback that sharpens it fastest.

12
回复

Watching Ctruh Studio go from an idea to a product that is now live on Product Hunt has been an incredible journey. Having worked alongside the team, I've seen the countless hours spent solving complex challenges to make 3D and XR creation simple, accessible, and browser-native.

What excites me most is that we're not just launching another tool. We're enabling creators, brands, and businesses to build immersive experiences without needing specialized technical expertise. Proud to be part of a team that's pushing the boundaries of what's possible in digital experiences. Congratulations to everyone who made this happen. 🚀

17
回复

@janet_david Thank you, Janet, "not just another tool" is exactly the bar we held ourselves to. Grateful to have built this alongside you.

10
回复
Most stores probably have the photos already. 3D stuff, not so much. So yeah, making it from the photos makes the whole thing less annoying to even try. Congrats on the launch!
16
回复

@etiennegarcia You've put your finger on the exact thing, thank you. The 3D itself was never really the barrier; it was "go commission or build 3D assets before you can even start." That's what killed it for most stores. Starting from the photos you already have removes the reason to not try.

Best way to feel it: grab a product photo you've already got and drop it in, VersaAI turns it into a 3D model in a couple of minutes, no starting from scratch. Free launch credits if you want to test it on your own catalog.

Would genuinely love to hear how it does with your real product shots, that's the feedback that matters most to us. And congrats-back on spotting the actual point 😄

4
回复

The spec I'd put on the page is mesh weight, not render quality. A configurator that takes 8 seconds on mobile 4G converts worse than the flat photo it replaced, so the number that matters is poly count and texture size after your optimizer runs, not what VersaAI generates before it. If you're already holding a per-product budget, say it loudly. That's the line that decides whether a brand ships this or shelves it after the pilot.

16
回复

@asadmalik901 This is the most useful comment on the page, and you're completely right. Render quality is table stakes now; delivered mesh weight after optimization is the number that actually decides whether a brand ships or shelves it. A gorgeous asset that takes 8 seconds on 4G loses to the flat photo every time.


For what it's worth, that's exactly why the pipeline auto-optimizes what VersaAI generates rather than serving raw, decimation, texture compression, and LODs before anything hits a shopper's device. The generated poly count matters far less than what actually streams.

But you've called out something real: we talk about that on the engineering side and don't say it loudly enough on the marketing side. The per-product performance budget is exactly the line a serious brand cares about, and we should be leading with it. Genuinely grateful, this is the kind of feedback that changes how we position the whole thing.

13
回复

Watching Ctruh Studio go from an idea to a product that's now live on Product Hunt has been an incredible journey.

It's amazing to see years of hard work finally out in the world. The goal has always been simple: make immersive 3D, XR and AI experiences easy to create and experience right in the browser, without downloads or unnecessary complexity.

Proud to be part of a team that's making immersive technology more accessible for creators, brands, and businesses.


If you're visiting us on Product Hunt today, take a few minutes to explore the live demos. We'd love your feedback and support! 🚀

14
回复

Big congrats to the whole team

Really love how you are making immersive shopping far easier for everyone

Wishing you a huge launch day and plenty of momentum

What has been the biggest surprise from early users so far

13
回复

@suryansh_tiwari2 Thank you, Suryansh, means a lot coming from a fellow maker 🙏

Honest answer on the biggest surprise: how fast non-technical users have jumped in. We built this to remove the specialist barrier, but I half-expected people to still approach it cautiously. Instead, someone earlier today (runs a ceramics shop) told us the material editor got her glaze textures close enough to real photos that her customers stopped asking for extra images. Another was surprised the AI handled organic shapes, "my plant models actually look like plants." Those aren't the easy cases, so seeing regular users push it there on day one has been the happy surprise.

The other one: how much people care about the "start from photos you already have" part. We thought the wow was the 3D; turns out the relief is not having to create assets from scratch.

How's it going on your side, EverTutor's a great space to be building in. Rooting for you too!

3
回复

Just tried it out, and I was genuinely impressed! I converted almost every item I've bought online just by clicking a photo, and it turned them into 3D models so quickly. The experience was incredibly smooth. I could zoom in really close, rotate the models from every angle, and explore every little detail.

Whenever I wanted to make a change or try something different, the AI chatbot was there to help. The AR feature was just as impressive. I could place each item on my desk and instantly see how it would look in my space.

I honestly can't wait to see where this product goes from here. Huge credit to the CTRUH team for building something this exciting!

12
回复

The platform feels simple to use, even without much technical knowledge, and the 3D, AR, and AI features save a lot of time. There is still some room for improvement, but the overall experience has been smooth and genuinely useful for presenting products in a more engaging way.

12
回复

Really impressed with the experience so far. The no-code 3D workflow is smooth, the editor feels polished, and it's great to see a product making immersive content creation more accessible. Congrats on the launch!

11
回复

Ctruh is building the infrastructure for the immersive web.

We make it easier for businesses to create and deploy interactive 3D, AR, and XR experiences — from virtual try-ons and 3D product configurators to virtual showrooms and immersive walkthroughs.

With browser-native 3D technology and AI-powered creation tools, Ctruh is making immersive experiences more accessible, scalable, and easier to experience without apps or complicated hardware.

We’re helping brands turn products into experiences.

11
回复

Ctruh Studio makes creating interactive 3D product experiences incredibly simple with AI. I am impressed by how seamlessly it transforms product visuals into immersive experiences, it's a powerful no-code platform that helps brands stand out and drive engagement.

11
回复

Ctruh is genuinely solving a real e-commerce pain point by letting shoppers see products in 3D/AR before buying and doing it without forcing brands into clunky app downloads or dev-heavy integrations, team has built something people actually want, not just a flashy demo.

I personally like there Versa AI outputs

11
回复

The 2D to 3D AI blew my mind. I went from a 2D image to a full fledged XR experience in just a couple of minutes. Superb!

11
回复

What stood out to me is how accessible this makes 3D and XR for people without a technical background. Using AI to generate a model from a prompt and previewing it directly in the browser feels like a genuinely useful workflow, especially for smaller brands wanting to showcase products in a more interactive way.

10
回复

@Ctruh Studio is an impressive platform that enables brands to create interactive 3D, AR, virtual storefronts, and immersive product experiences with ease. I’m proud to have contributed my time and effort to building this product at Ctruh, and it’s exciting to see how it is helping brands showcase their products in a more engaging and innovative. Its powerful all in one browser based workflow is a game changer for brands looking to deliver immersive customer experiences.

10
回复

Ctruh Studio is great to make product pages immersive with the AI models that can generate 3D assets from images and also create multiple variations using the tools available in the Studio, being able to make AI content as well on the same platform where all the product assets lie makes it very easy to use.

10
回复

Ctruh Studio looks like an exciting platform at the intersection of 3D, AI, and XR. Making immersive experience creation more accessible could unlock huge possibilities for brands, creators, and businesses. Excited to see how Ctruh Studio evolves.

10
回复

I've integrated a few 3D, AI, and XR experiences built with Ctruh Studio into my website, and the impact has been impressive. Visitors are actually exploring the experiences instead of just scrolling past, which has noticeably increased engagement and time on site. That extra interaction has translated into better conversions and ultimately more sales. It's refreshing to see a platform that makes it so easy to create immersive experiences that deliver real business value. Excited to see where Ctruh Studio goes next! 🚀

10
回复
#3
Airtop for Google Ads Automation
Build campaigns, optimize spend, and create reports.
270
一句话介绍:Airtop 将Google Ads的账户管理、关键词研究、预算优化和报告生成浓缩为一段自然语言对话,让不懂PPC的小团队和独立营销者也能像有专家顾问一样操作广告,无需再面对复杂界面和浪费预算的风险。
Marketing Advertising Artificial Intelligence
AI广告自动化 Google Ads管理 PPC优化 对话式营销 广告预算审计 CRM数据联动 自动化报表 智能关键词研究 企业级Web自动化 SEM工具
用户评论摘要:用户普遍认可其“对话式管理”和“AI非炫技”的实用价值。核心追问集中在三处:一是预算调整的决策透明度和可审计性;二是转化事件(尤其是远期退款/取消)如何逆向反馈给优化模型;三是针对小预算账户的适用性及网页布局变动时的“自愈”能力。创始人回复坦诚,承认“退款闭环”是下一步方向,赢得了信任。
AI 锐评

Airtop的聪明之处在于,它没有试图再造一个“更聪明的竞价算法”,而是精准切入了PPC行业权力结构中最脆弱的一环——**专业知识的黑箱与信任的崩塌**。它卖的不是AI,是“把黑箱翻译成人话”的能力。当小商户被Google Ads的复杂界面和无效点击烧掉预算时,Airtop用对话式交互和“先审批后执行”的授权机制,重构了“专家-雇主”之间的代理关系,把控制权交还给用户。

其真正的护城河并非语义化网页交互,而是**基于CRM数据的“高价值事件”回传**。让优化目标从“注册”升级为“激活/付费”,这抓住了广告浪费的核心根源。但正如评论者一针见血指出的,其价值闭环仍有缺口:转化一旦触发即算“完成”,远期的取消或退款无法逆向修正出价模型(Google的转化调整窗口仅55天)。这意味着它优化的是“即时行为”,而非“长期客户终身价值”。

因此,Airtop目前的定位更像是一位高效的“战术执行官”,而非“战略分析师”。它能让预算花得更精准,但无法解决业务模型本身的缺陷。对Airtop而言,下一步若不能打通与CRM的双向实时数据流,以应对退款和自然流失带来的模型污染,其宣称的“智能优化”在长周期、高客单价的业务中仍会遭遇信任挑战——这恰恰是它最初想要消灭的那个问题。

查看原始信息
Airtop for Google Ads Automation
Airtop builds, monitors, and optimizes your Google Ads campaigns from a conversation. Keyword research, campaign creation, waste audits, and performance reporting — no expertise required.

Running Google Ads is difficult. The interface is confusing, proper optimization requires special expertise, and it is very easy to waste thousands of dollars on campaigns that result in junk clicks instead of real conversions. Unless you’re a PPC expert, the cards are stacked against you.

We wanted to make Google Ads less frustrating for small teams and solo marketers. So we built native Google Ads automation directly into Airtop. Connect your Google Ads account, and Airtop will:

👉Research keywords
👉Build themed campaigns based on best practices

👉Audit and optimize spend

👉Create automatic scheduled reports

👉Send updates directly to Slack, email, and more

Airtop works like a PPC consultant would. It understands context, connects to your CRM, and makes changes directly in Google Ads once you approve them. Any change that can affect spend requires your explicit approval first. 

We’ve been running Google Ads with Airtop since May, and it’s suggested many optimizations that we otherwise would have missed. We also don’t have to spend hours buried in the Google Ads interface anymore. We’re excited to share this tool with you!

You can try Airtop’s Google Ads integration out here: airtop.ai/google-ads.

Use promo code GAPH29 for a free month of Airtop’s Starter plan.

We’re here all day. Ask us anything!

8
回复

@amir_ashkenazi I've hired agencies for exactly this and the reporting layer is where trust usually breaks, since the numbers never match what I see in the platform. When Airtop moves budget on its own, how much visibility do I get into why, not just that it happened? Wondering whether an operator can actually audit those decisions.

3
回复

@amir_ashkenazi For someone who’s burned budget before on junk clicks, what’s the first thing Airtop would do differently in my account; and how quickly would I see that change after connecting?

0
回复

This feels like a practical use of AI rather than AI for the sake of AI. Turning Google Ads management into a conversation could save marketers hours every week, especially when launching or optimizing campaigns. Excited to see how it performs with real-world accounts. Congrats on the launch!

5
回复

@1mirul Thanks so much! We've gotten a lot of positive feedback on the integration so far. And personally, it's saved me a lot of time not having to e.g., come up with 15 headline variations per ad. I don't even have to copy and paste them from Claude anymore :D

0
回复

I run a small e-commerce shop and Google Ads has always felt like a black box to me. I set a budget, watch it disappear and hope something works. What I like here is the "no expertise required" angle, that's usually marketing fluff but if it genuinely walks a beginner through campaign structure, that's the real barrier for people like me.

4
回复

@thomas_jack4 Appreciate that, and you've actually named why it feels like a black box. Two things are usually going wrong under the hood: the account has no real campaign structure, and conversions aren't being tracked properly. So Google is optimizing toward nothing in particular and the budget just quietly leaks.

The "no expertise required" part is aimed straight at that. It walks you through what actually counts as a conversion and makes sure Google can see it, then groups your keywords into tight themes so each ad and landing page is relevant instead of generic (relevance is literally the thing that lowers what you pay per click). It won't turn you into an expert overnight, but it means you stop guessing and start seeing why the budget goes where it goes.

If you want, tell me what you're selling and I'm happy to point you at where to start. That first bit of structure is usually what turns it from a black box into something you can actually steer.

0
回复

the crm connection is the interesting bit tbh. an optimizer is only ever as good as the event you point it at, and signups or checkout starts will happily train the bidding to buy more of the clicks that refund later. does a cancellation weeks down the line flow back and devalue the click that caused it, or is a conversion final once it fires?

3
回复

@alex_watson2110 Great question, and it's the exact distinction that matters. You're right that an optimizer only inherits the quality of the event you point it at, and signups will happily train bidding to buy more refund-prone clicks.

What the CRM connection buys you today is moving that event up the funnel: instead of firing on the raw signup, you fire on the CRM-qualified event keyed to the gclid (activated, SQL, paid, whatever your real value moment is). So you're not rewarding the click that signs up and bounces in the first place, which is where most of the waste comes from.

To answer the actual question though: today a conversion is effectively final once it fires. A cancellation weeks later doesn't yet flow back and devalue the click that caused it. Closing that loop with Google's conversion adjustments (retract / restate against the gclid, inside their ~55 day window) is exactly where we're headed next. Genuinely curious how you've seen teams handle the churn-outside-the-window problem, since that's the part that never fully closes.

0
回复

Congrats @amir_ashkenazi and team. The hard part is often not understanding the task but actually interacting with websites and completing the steps. How Airtop handles websites that change their layouts frequently?

2
回复

@hamza_afzal_butt Thanks, appreciate it.

You've hit the exact thing that separates a demo from something that runs in production. Most tools interact with a page structurally, through CSS selectors and XPaths, so the moment a site renames a class or reshuffles its DOM, the path breaks even though the actual content hasn't changed.

Airtop works off the page semantically instead, resolving what you asked for by meaning rather than a hardcoded path. And we've built self-healing on top: when a page changes enough to trip the agent, it detects the break and repairs itself, no rewrite from you.

That maintenance tax is usually the real cost of web automation, so it's the part we set out to eliminate.

0
回复

Congratulations on the launch! I run Google Ads on a small budget, so reporting and spend checks are what actually eat the time. Does the agent work through the Google Ads interface or through the API, and how does it hold up when Google changes the layout? I would also like to know whether this is worth using below a certain monthly spend, or whether it is built for larger accounts.

1
回复

@alieksia Thanks! And you're pointing at the right pain: on a small budget it's the time spent checking, not the spend itself, that hurts.

On your questions:

Interface or API: the API. For Google Ads it connects through the official Google Ads API, not by clicking around the visual interface. You authorize it once against your account, and the agent pulls spend, performance, and search terms straight from the source.

Spend size: the value here is time, not account size. Pulling reporting and running spend checks takes about the same effort whether you're spending $500 or $5k a month, so it pays back based on how often you check, not how big the budget is. Definitely not built only for large accounts.

If reporting and spend monitoring are the main things eating your time, that's squarely the use case.

Happy to walk through what a daily or weekly digest would look like for your setup.

2
回复

Late to this one but the auth part is the decision I keep thinking about. Most web agents stop at the public web, and the useful data is almost always behind a login. Question from the content side: when a site changes its layout, does the agent work it out again by itself, or does the instruction need a rewrite? Our scrapers break every few weeks and that is the real cost, not the setup.

1
回复

@saied_alimoradi Glad you went straight to this, it's the exact problem the architecture is built around.

Your scrapers break because they target the page structurally: CSS selectors and XPaths. Rename a class or reshuffle the DOM and the path is wrong, even though what you're actually trying to read hasn't changed at all. That's the every-few-weeks tax.

Airtop works off the page semantically instead, resolving what you asked for ("get the price," "pull the contact's title") by meaning rather than a hardcoded path. And on top of that we've built self-healing: when a page changes enough to trip the agent, it detects the break and repairs itself. So to answer your question directly, the agent works it out on its own. No instruction rewrite from you.

Which is the whole point, for exactly the reason you named. The real cost was never the setup, it was the constant re-fixing. That's the part we set out to kill.

0
回复

The way Airtop turns plain English into a working browser agent feels like real magic, not a gimmick. Love that it actually logs in and navigates instead of just pretending to.

0
回复
#4
Qwen3.8-Max
Qwen’s most capable model for coding and cowork
253
一句话介绍:Qwen3.8-Max是一款拥有2.4T参数MoE架构、支持1M上下文与多模态Agent能力的大模型,专攻编程、科研协作与长周期自动化任务,解决开发者在复杂项目中“AI无法持续跟进、意图漂移、上下文断裂”的痛点。
Productivity API Artificial Intelligence
大模型 MoE 编程助手 多模态Agent 长上下文 开源权重 自动编程 科研协作 代码生成 Qwen
用户评论摘要:用户高度认可开源行为,称“全量权重发布是给社区的礼物”。核心疑问集中在16天自主Agent测试的可信度:是否追踪了意图保持、返工率、回归率与上下文漂移?另有用户好奇模型在超长任务中与人类处理问题的差异。
AI 锐评

Qwen3.8-Max的发布,本质上是一次“技术秀肌肉”与“生态卡位”的双重动作。2.4T总参数、95B激活、1M上下文——这些数字在行业内确实顶尖,但“最能打”的标签需要更苛刻的检验。社区最尖锐的质疑恰恰命中了命门:16天自主运行产生265个commit,这听起来惊艳,但若缺乏对“意图保值率”和“返工成本”的量化跟踪,该测试只能证明“能跑”,而非“跑得靠谱”。OpenAI、Anthropic不敢开权重,Qwen敢开,这确实值得尊敬——但也要看清,开源既是情怀,也是对抗闭源阵营的差异化武器。真正价值不在参数规模,而在“长任务场景下的状态一致性”能力,这决定了Agent能否从Demo走向生产环境。如果Qwen能公开那16天里context-drift的发生频率与应对策略,将比任何发布会都有说服力。否则,这不过又是一次“参数通胀”式的狂欢。对于开发者而言,别急着欢呼,先拿真实业务项目去跑一个月,再判断它究竟是同事,还是玩具。

查看原始信息
Qwen3.8-Max
Qwen3.8-Max is Qwen’s most capable model to date, a 2.4T-parameter MoE with 95B active parameters, 1M context, and multimodal agent capabilities for coding, research, cowork, and long-horizon tasks.

Hi everyone!

Qwen3.8-Max is @Qwen3’s most capable model to date, built around coding, cowork, and long-running agent tasks.

One of the tests ran for 16 days straight. Qwen3.8-Max started with an empty repo, built a coding harness, and kept working on it as new issues, feedback, and test results came in. The final repo had 265 commits, 127 PRs, and 151 issues.

It is a 2.4T-parameter MoE with 95B active parameters and a 1M context window. It already works with the major harnesses you use.

The API is live now on QwenCloud.

Open weights arrive next week. This will be the largest open-weight release in Qwen’s history!

11
回复

The 16-day agent run is the most interesting claim here. As a first impression, the useful test is not only task completion but whether the model preserved intent while new issues and feedback accumulated. Did you track rework, regression rate, or context-drift failures across the 265 commits?

0
回复
1
回复

@zaczuo When you let Qwen3.8‑Max run unsupervised for that long, what was the most surprising way it handled a problem differently than a human developer would have?

0
回复

The fact that you keep open-sourcing these models at this scale is honestly wild. Most labs gate everything behind APIs, so seeing Qwen3 drop with full weights on GitHub feels like a genuine gift to the community.

0
回复
#5
Appllama
Study 25,000+ screens from top-earning iOS apps
193
一句话介绍:Appllama 是一个面向App创作者的“设计调研平台”,聚合App Store头部高营收应用2.5万+界面截图,让用户能按流程、UI元素、配色字体等维度拆解竞品设计,并在上下文中关联营收与下载数据,解决“知道好设计长什么样,却不懂它为什么有效”的痛点。
iOS Design Tools UX Design
设计调研 竞品分析 应用界面截图 高营收App 移动端UI 转化流程拆解 设计灵感 App Store数据 产品决策 增长研究
用户评论摘要:用户认可“按结果而非美学筛选样本”的思路,并追问流程历史版本、排名下滑样本及营收数据来源;有人指出付费墙前预览不足,建议开放3-5张截图试用;另有用户对比Mobbin,创始团队回应差异在于提供营收数据与交互式探索;API/MCP需求在评论区出现,官方称一周内发布。
AI 锐评

Appllama聪明地切中了“设计参考”品类的一个真空白:不是让你看好看的设计,而是让你看**赚钱的设计**。把营收、下载量、评分和界面截图放在同一画布,等于把“A/B测试胜出者”的半成品答案端到了用户面前——这比Dribbble或Mobbin那种纯审美陈列高了一个维度,更接近“竞品逆向工程”工具而非设计素材库。

但它的护城河并不深。Mobbin已经在做同类聚合,Figma社区的免费屏风插件也不缺,而Appllama目前的核心差异点——营收数据——恰恰是评论区最先被质疑的地方(数据来源不清、数值与第三方预估偏差)。这不是小问题:一旦数据可信度被证伪,产品就退化为一个交互稍微好一点的截图库。

更值得警惕的是“持续追踪”的缺失。用户明确问到“能不能看一个支付墙的四次改版历史”,团队没有正面回应——而**改版历史才是真正的战略价值**。当前版本只是“当下高手的静态快照”,无法回答“这个高手之前走了哪些弯路”。没有时间维度,用户看到的仍是结果,而非路径,这让“研究”的含金量大打折扣。

至于免费陷阱:宣称“Start free”却让用户注册后找不到入口,直接被评论者点破,这种体验伤的是早期口碑。好在一个MCP即将上线,如果有API接入AI建站流程,它有机会成为“AI生成高转化UI”的训练数据层——这才是真正的想象空间。

总结:方向对了,但当前版本只是MVP的皮,数据可信度与历史追踪是真问题。若不补上“时间维度”,它始终只是Mobbin的挂件,而非替代品。

查看原始信息
Appllama
Appllama is a design-research platform for app creators. Search 25,000+ screens from 600+ of the App Store’s top-earning iOS apps; follow complete onboarding, paywall, home and in-app flows; inspect UI elements, colors and fonts; and see revenue, downloads and ratings in context. New apps arrive weekly, captured live from the store. Start free no card required.
Hey Product Hunt, I’m Jaimin, Co-founder of Appllama. app creators make the same difficult decisions every day: what should onboarding show first? when should a paywall appear? what happens before and after someone upgrades? a beautiful screen is useful, but it rarely explains why it is there, what came before it, or what happens next. we wanted the whole product decision in context. so we built appllama as a design-research tool centered on the apps that already earn at the top of the App Store. you can search 25,000+ screens from 600+ iOS apps, follow complete onboarding, paywall and in-app flows, inspect UI elements, colors and fonts, and see revenue, downloads and ratings alongside the design. new apps arrive every week. this is our third startup attempt. the first two failed. they taught us that working hard is not the same as creating value and that a launch is only the moment users get to decide. our team spent days and late nights capturing, organizing and refining details most people will never see. today, we’re proud to finally put that work in your hands. For the Product Hunt community, code PHUNT2026 unlocks the full Pro experience at 25% off. we’d genuinely value one unpolished answer: which iOS app or which part of an app flow should we capture next, and why?
11
回复

@jaimintf This is our third attempt, the first two failed" is the line I'd have put at the top. Working hard not being the same as creating value is the lesson that costs the most to learn.

On the product, the part I find interesting is that you're indexing screens from apps that already earn, so the sample is selected on outcome rather than on aesthetics. That's a different thing from a design gallery.

Question: can you see how a flow changed over time? A paywall that's been through four revisions at a top-earning app tells you more than the current version does, since you're effectively reading the results of their A/B testing for free.

Also 25,000 screens across 600 apps captured live weekly is a lot of scraping. Curious how you handle apps that restructure their onboarding between captures.

0
回复

@jaimintf If you could rewind and capture one “messy middle” moment that most apps hide, which app and flow would you start with, and what decision do you think it would clarify for builders?

0
回复

Amazing, congrats on the launch. Do you have any apps in the set that ranked and then fell off, or that shipped a flow and lost conversion?

1
回复

That’s a really interesting use case! We’re currently focused on design and app discovery, so we don’t track conversion or retention changes yet.

0
回复

Hi, @jaimintf Very cool site, I could see it being useful, but can you tell me how does it differ from Mobbin?

1
回复

Thanks @abhinav_prakashan, two key differences:

  • We help founders discover what to build, not just how to design it, by showing app revenue data.

  • Our Explore feature offers a unique, interactive way to discover app screens.

2
回复
Looks really really cool. Do you guys have API or MCP? We’re running a mini app builder, can be very good way to suggest our builders flows that win
1
回复

@markookhman Thanks for your kind words, we're shipping out a MCP ~1 week - stay in touch :)

2
回复

Congrats on the launch! Quick question — where is the revenue data coming from? For a few of the apps I looked at, the numbers seem a bit off compared to what I'd expect. Curious if it's estimated from a third-party source or pulled directly from somewhere.

0
回复

I wasn't able to test it without paying, even though it initially seemed like that might be an option. I wanted to see whether there were apps with maps. Searching by keyword returned several apps with "maps" in their names, but it wasn't clear whether they actually included maps in their interfaces or how important maps were to the overall experience.

I'd suggest allowing users to open at least 3–5 mockups after signing up, but before requiring payment. Personally, I might have subscribed if I had some confidence that the platform contained something useful for my needs.

0
回复

Hey @natalia_iankovych, that’s completely fair feedback.

This is what a search for map-based interfaces looks like on Appllama. Once you open a screen, you can also explore similar screens across other apps.

We’ll definitely improve the preview experience so users can better understand the value before subscribing.

Would love to know whether this example is useful for what you’re looking for and if we can win you back.

1
回复
#6
Plethora
Youtube for interactive content
183
一句话介绍:Plethora是一个将“短视频信息流”替换为“微型互动体验流”的内容平台,用户可在碎片时间里直接玩迷你游戏、解谜、互动艺术或数字减压玩具,解决“被动刷视频却越刷越累”的注意力消耗痛点。
Android Art Puzzle Games Free Games
互动内容平台 微型游戏 信息流替代 数字解压 交互式艺术 休闲益智 内容消费 创作者生态 Web交互 注意力经济
用户评论摘要:用户普遍认可其成瘾性与创意,特别提到吃豆人、解绳等游戏令人印象深刻。核心疑问集中在技术实现:是否用WebAssembly/Canvas沙盒运行。有用户反馈落地页在Safari中卡顿,另有用户询问如何将自己的互动体验接入平台,官方回应可通过create.plethora.studio提交,并支持用AI编码助手生成内容。
AI 锐评

Plethora的定位聪明地踩中了两个正在生长的交汇点:AI降低编程门槛后,软件从“工具”变为“消费品”;以及社交媒体用户对被动沉浸式信息流的倦怠。它看似在做“互动版抖音”,实际上是在尝试定义一种新内容范式——程序即内容,互动即阅读。

从产品逻辑看,“微型体验”确实比短视频更能带来主动参与感和多巴胺刺激,且天然适合移动端的碎片时间。但这也暴露其核心结构性风险:内容供给的可持续性。当前平台依赖少数创作者或早期发烧友用AI大量生成“小玩意”,但这类内容极易陷入同质化——玩一个月后,“puzzle”和“mini-game”的壁垒会迅速模糊,用户的新鲜感将快速衰减。更关键的是,这种轻量互动缺乏短视频那种“社交货币”属性,用户很难因为“玩了一个优质逻辑谜题”而产生分享或社交绑定。

其次,官方屡次提及“注意力回归”和“对抗焦虑”,但本质上其产品机制仍在争夺用户时间,只不过从“刷视频”换成了“戳玩具”。如果Plethora不能建立“有限时长+深度心流”的硬性护城河,它很可能成为一个高级版“在线游戏站”,而非媒体平台。技术层面,用户的质疑也切中要害:若微体验都依赖webview和JavaScript解释执行,性能和电池损耗将成为移动端体验的隐形天花板。

最值得肯定的是它明确构建了创作者生态(create.plethora.studio),且支持AI辅助创建,这使其具备成为“互动内容早期分发渠道”的潜力。但前提是它必须下定决心与“开放标准”绑定,比如支持通用互动内容协议,否则很容易沦为AI生成玩具的仓库。一句话:好概念,缺机制,且要警惕成为“高级糖果”而非“内容新物种”。

查看原始信息
Plethora
Plethora is a platform for interactive content: a feed where micro-experiences live. Mini-games, puzzles, digital fidgets, interactive art, tiny worlds, educational simulations. Every bit can be touched, moved, poked, and played with. The content responds to you.

Hey ProductHunt,

We built Plethora to be the next home for interactive content.

Our bet - As AI democratizes programming, programs become the consumables of tomorrow.

Our feeds have been full of videos, and our attention is being rented to big tech estates.

Plethora aims to bring back attention, and let the user consume with control and agency.

Plethora offers an alternative scrolling experience. Your feed consists of -

•⁠ ⁠classic games you miss - arcades and candy crush and piano tiles.

•⁠ ⁠games you have never seen and will enjoy enjoying.

•⁠ ⁠hundreds of puzzles to scratch your brain

•⁠ ⁠fidget toys for when overstimulated.

•⁠ ⁠interactive art - to interact with like god intended.

•⁠ ⁠interactive stories.

•⁠ ⁠simulations and zero-player games and worlds to hang out in.

•⁠ ⁠educational content / active learning - to finally help you see.

•⁠ ⁠utility like tuning your guitar.

•⁠ ⁠experiences waiting to be figured out.

Every bit on Plethora responds to you.

Early love for Plethora has people using it in-between moments, to get into flow state and to deal with overstimulation and anxiety.

Early creators see Plethora being the defining platform for the medium.

Follow us along our journey.

9
回复

@pranay_dongre nice launch , congrats🙌 Is Plethora running these micro-experiences in lightweight webviews or using a custom WebAssembly / HTML5 canvas sandbox runtime?

2
回复

@pranay_dongre For someone who’s feeling overstimulated right now and just wants 2–3 minutes of calm, what’s the one type of “bit” you’d recommend they start with on Plethora; and why that one?

0
回复

@pranay_dongre It's surprisingly addictive! :)

P.S. Your landing page feels a bit sluggish in Safari.

0
回复

I have poured the entirety on my childhood on this app.
You will find creating for Plethora as a newfound joy.

4
回复

This is such an amazing app, with so many interactive games

I especially liked pacman and another intuitive game where we had to unentangle knots/strings between points 🧠

2
回复

very interesting concept. reminds me of some games like until dawn

1
回复

I love the idea of this! i like this because when it comes to art, my favorite type is interactive. One day when i become a physical artist (3D mediums), i want my art to be interactive. Fun fact, im a dancer and an AI engineer, so hopefully that helps with the demographic, im very much a polymath, just stopping at those 2.

0
回复

Oh wow! This looks so cool... just downloaded. I wonder if there's some room for us to put some of our interactive experiences onto your platform?

0
回复

@maria_wall_ball Yes ofcourse, please checkout create.plethora.studio.
Make bits by taking to your coding agent.

0
回复
#7
claudemon
Wild Pokémon appear while you wait for Claude Code
145
一句话介绍:claudemon 将 Claude Code 的等待时间转化为宝可梦捕捉游戏——你的每一条提示词都是草地里的一步,AI 每工作 20 秒就前进一步,随机遇到野生宝可梦后,你可以在第二个终端标签页里与它战斗,全部 151 只宝可梦完全本地运行,无需账户。
Developer Tools Artificial Intelligence GitHub Games
开发者工具 终端游戏 Claude Code 效率工具 等待时间消磨 宝可梦 开源 本地运行 游戏化插件 命令行应用
用户评论摘要:用户普遍称赞创意有趣,认为“等待变游戏”解决了终端等待时的无聊与分心问题,且完全本地、开源是加分项。有用户提议将遭遇触发机制从“计时”改为“绑定任务退出码”,这样失败的任务就无法捕捉宝可梦,增加游戏与真实工作的强关联;开发者回应称可多次遭遇以避免长任务中等待单一战斗导致的无聊。另有用户咨询是否影响任务性能,开发者明确回复对 Claude 运行无任何影响。
AI 锐评

claudemon 的本质是一个“注意力安慰剂”,它没有减少等待,也没有加速任务,而是让用户的大脑从“焦虑的空白”切换到“主动的狩猎”。这在心理学上是成立的——宝可梦的即时反馈恰好补偿了 AI 工作中无法预期的长尾延迟。但从产品逻辑上看,它存在一个根本性的矛盾:游戏进度与 AI 工作耗时强绑定,这意味着 AI 越慢、任务越卡,游戏收益越大。用户会被诱导去欣赏“久拖不决的失败”,而非推动任务快速完成,甚至可能无意识中偏好更慢的 agent 配置。更有价值的改进方向,是评论中提到的:以任务退出码作为触发条件,失败即失去捕捉机会,胜利则加速遭遇频率,让游戏奖励与工作结果对齐。否则,这只是一个精致的“等待美化器”,而不是真正的生产力游戏化。开源和本地化虽是美德,但不足以掩盖它在“价值驱动”上的缺位——目前它只奖励时长,不奖励质量,长期使用后用户在新鲜感消退时,会意识到自己用生产工具的耐心换了一场无意义的收集。

查看原始信息
claudemon
Half of Claude Code is waiting. claudemon makes that time a game: your prompts are steps through the grass, every 20s of work another step. Something jumps out, the status line says so, you fight it in a second terminal tab. All 151, fully local, no account.
Hi PH 👋 Half my day in Claude Code is watching it work. Not long enough to switch tasks, too long to just sit there. claudemon lives in that gap. It's a Pokémon game that only advances while Claude does. Your prompts are steps through the grass; every twenty seconds Claude works is another step. Something jumps out, the status line tells you, you fight it in a second terminal tab. OpenSource, Free, MIT, fully local.
2
回复

hey this sounds really fun! im wondering if it has any effect on wait times?

1
回复

@ethan_cheng Haha nope, absolutely none! It doesn't speed up or slow down Claude at all. Purely cosmetic (and much more fun to watch than a loading spinner)!

0
回复
@zamarrowski Turning the AI waiting gap into a Pokémon loop is genius! Context switching usually kills productivity, so keeping the user engaged in the terminal without losing focus is a great solution. Super cool concept for open-source excited to see where this goes!
0
回复

The completionist in me sees "all 151, fully local" and immediately wants to leave long agent runs going just to fill out the Pokédex lol. You've somehow built the one dev tool that makes me want MORE waiting — nicely done.

0
回复

the second terminal tab angle is so weird it kind of works. caught myself actually looking forward to checking back in.

0
回复

Going to give it a spin! Now the waiting while claude works is a real pain and I don't see it going away for the next few years. So loved this idea, super builder centric.

0
回复

@himanshu_garg Thanks! Exactly, waiting is just part of the deal for a while, so might as well make it fun. Let me know what you think when you give it a spin!

0
回复

Congrats on the launch, @zamarrowski🚀

Converting idle wait time into a Pokemon game is such a clever idea. Context switching for 20-second waits usually kills focus, so keeping it right in the terminal is super smart. Love that it's open source and fully local too.

Good luck with the launch today!

0
回复

@founder_daksh Thanks a lot! Appreciate it 🙌 Exactly, the goal was to keep you hooked on the terminal instead of alt-tabbing while Claude takes a minute. Hope you enjoy checking it out!

0
回复

The thing that makes this work is that the game only advances while Claude does, which is also the trap. You're paying people in Pokémon for waiting, so a run that spins for 20 minutes and produces nothing still feels great. I'd tie the encounter to exit code rather than elapsed time. Then a failed run costs you the catch, and you've accidentally built the only test result anyone would actually watch for.

0
回复

@asadmalik901 Good idea, thanks! The idea is that several encounters can happen per agent run so that if the run is very long, people don't get bored with just waiting for one battle while Claude Code finishes to find out if it was caught or not

0
回复
#8
yapyap
Own your voice again. Local-first voice & meeting recorder.
142
一句话介绍:yapyap是一款本地优先的语音与会议记录工具,在无需订阅、保护隐私的场景下,解决用户对音频数据外泄和持续付费的痛点,实现全离线录音、转写、说话人识别及AI摘要生成。
Notes Meetings Audio
本地优先 语音记录 会议转写 隐私保护 离线AI 买断制 说话人识别 智能摘要 无订阅 生产力工具
用户评论摘要:用户主要赞赏本地处理与隐私保护理念,认为“数据不离开设备”和“无订阅”极具吸引力。部分用户询问客户评价对获客的影响,隐含对市场推广和商业可行性的关切,但整体反馈积极,未见功能缺陷或使用问题。
AI 锐评

yapyap的“反云端”叙事精准切中了当前SaaS订阅疲劳与数据隐私焦虑两大情绪,其“买断制+本地推理”的定位在Product Hunt上获得142票和正向评论,说明这一差异化策略在早期采用者中有效。但冷静看,产品价值并非无懈可击。

首先,本地AI转写与摘要的质量天花板取决于用户硬件,尤其长音频、多人对话场景下,消费级设备的处理速度与准确率必然弱于云端大模型。所谓“不妥协”在体验层面实则是一种妥协,只是用户用隐私换取了便利性,而yapyap用算力换取了主权。

其次,“无订阅”意味着产品需靠一次性买断覆盖长期维护、模型更新和兼容性适配成本。本地模型迭代速度远慢于云端,若OpenAI、Anthropic的本地化离线模型能力滞后,yapyap的“Lenses”生态将面临插件质量参差、开发者动力不足的困境。没有持续收入流,社区生态和核心引擎升级都将是隐患。

此外,产品宣称“可选连接云端大厂”,这实际上承认了本地推理的局限性——当用户需要更强分析时,仍得依赖云端,只是从“被迫”变为“可选”。这削弱了“完全本地”的纯粹性卖点,但也务实地保留了进阶需求出口。

真正的价值点在于“记忆管理”而非“录音转写”。可搜索的历史语音库、自定义分析视角,将工具从一次性处理提升为个人知识资产库。若能将本地数据与设备端智能体(如Apple Intelligence、Windows Copilot)深度融合,或可成为个人语音数据的“本地中枢”。但目前来看,产品仍停留在“隐私优先的效率工具”层面,尚未形成不可替代的护城河。建议团队尽快开源Lenses协议,引入更多离线模型适配,并以企业本地化部署为突破口——那里“数据不出域”是硬性刚需,愿意为一劳永逸的模式付出更高价格。否则,小众的隐私极客圈子,撑不起一款“永久”产品的长期主义。

查看原始信息
yapyap
Every meeting recorder ships your audio to the cloud and bills you monthly. yapyap does neither. It records, transcribes, names your speakers, and turns talk into summaries and action items entirely on your own machine. “Lenses” reshape each recording into whatever you need: a summary, a to-do list, or a decision log. You can install more or build your own. Prefer the cloud? Optionally connect any major provider: OpenAI, Anthropic, Groq. Either way, yapyap is yours forever. No subscription.

👋 Hey Product Hunt!

I got sick and tired of paying subscriptions for everything in my life.

The latest addition? A transcription app that was charging me every month to upload my conversations to their servers.

So I built the opposite.

yapyap records and transcribes conversations entirely on your machine. Speaker identification, summaries, action items, custom analysis. All local. No account.

No bot is joining your calls, and no audio is leaving your device.

The parts I'm most stubborn about:

🔒 Nothing leaves your device.
Transcription, diarization, and the AI analysis all run on your hardware. Not “encrypted in transit.” Not “we don't train on your data”. Just: it never goes anywhere.

💸 You buy it once.
No monthly fee, no lock-in, and no archive holding your words hostage. Your recordings stay searchable, exportable, and yours. Forever.

🔍 It's a memory, not a transcript dump.
Everything you've ever recorded is searchable, and you can point custom analyses (“lenses”) at any conversation.

📱 There's a phone app too
For the conversations that don't happen at your desk. It syncs to your desktop over your network and no cloud in between.


Software used to work this way. I still believe it can.

I'd genuinely love your feedback!

Own your voice again.

8
回复
@xiduzo Out of curiosity, how important are customer reviews when it comes to winning new clients for your business?
0
回复

@xiduzo love the idea that it's keeping everything local, mate! I think people really value privacy of your data and this sounds pretty useful!

1
回复
#9
Snapdown
Turn anything on your Mac screen into clean Markdown
137
一句话介绍:Snapdown是一款macOS本地OCR工具,通过快捷键截取屏幕任意区域,将表格、列表、标题等视觉结构直接转换为干净的Markdown格式,解决“看得见但选不中”内容的复制与整理痛点。
Mac Productivity Developer Tools
Mac效率工具 OCR识别 Markdown转换 屏幕截图 本地隐私计算 苹果芯片 表格结构识别 文档处理 生产力工具 开发者工具
用户评论摘要:用户认可其结构保留能力,尤其是表格与列表转化质量。核心疑问集中在:1) 跨滚动表格的 Aggregate Mode 拼接准确性;2) 完全离线可用性确认;3) 对不确定的OCR结果是否提供置信度标记,以防数据篡改风险;4) 是否依赖浏览器DOM或纯视觉识别(已确认纯视觉,不读DOM)。
AI 锐评

Snapdown的切入点精准且克制——它没有重造OCR轮子,而是针对“结构丢失”这个OCR行业长期被忽视的痛点做深做透。把表格变成Markdown表格、列表保持层级,这看似是格式问题,实则触及了知识工作者最核心的“信息可复用性”需求:当截图内容能无缝粘贴进Notion、GitHub Issue或LLM对话时,它就完成了从“像素”到“结构化资产”的跃迁。

但产品要走的坎也很明显。第一,纯视觉重建结构存在天花板:复杂嵌套、合并单元格、颜色语义(如红色警告)会被无差别抹平,而评论中用户对“置信度标记”的需求直指要害——在合规审查或医疗数据场景下,一个悄悄造出来的假单元格比整段报错更危险。目前回应只强调“本地运行”,却回避了错误暴露机制,这是未来B端客户买单前必过的信任关。

第二,“Mac-only+Apple silicon”是双刃剑。一方面模型优化和隐私卖点统一,但团队是否准备了应对Windows或Intel Mac的溢价方案?若TAM(可寻址市场)被限定在少数派用户中,长尾需求(如浏览器DOM解析增强)的开发优先级就会变得尴尬——目前坚持“纯视觉”虽然安全,却也主动放弃了精确性作弊码。建议后续至少提供“DOM增强模式”作为可选项,让用户在隐私和正确率之间自行权衡。

总体而言,这是一款“小而锋利”的工具,适合独立开发者长线打磨。短期赢面在于产品细节的极致打磨(比如响应速度、快捷操作流),中期胜算取决于是否敢在“结构可信度”上做文章——比如推出校对视图或差异对比,这才是从“好用的小工具”晋级为“工作流基础设施”的钥匙。目前投票数不高,但评论区质量极高,说明触达的正是那个沉默的高价值用户群体,建议Broden沿着这条深水区继续挖。

查看原始信息
Snapdown
Snapdown turns any part of your Mac screen into structured Markdown, preserving headings, lists, tables, and text instead of flattening everything into plain OCR. Capture with one shortcut, paste anywhere, and keep every screenshot local on Apple silicon.
Hey Product Hunt 👋 I’m Broden, and I built Snapdown because I kept needing to copy things that were visible on my screen but weren’t actually selectable, like tables, documentation, error messages, and slides. Most OCR tools recover the words but lose the structure. Headings become ordinary lines, lists turn into paragraphs, and tables become difficult to use. I wanted output I could paste directly into a note, document, issue, or LLM chat without rebuilding it first. That’s why Snapdown produces structured Markdown. Privacy was also a must for me. Everything runs locally on Apple silicon, so your screenshots stay on your Mac and Snapdown works offline. I spent a lot of time making the capture loop as fast as possible, while still producing accurate, useful results. The goal is to press a shortcut, select a region, and get your Markdown without interrupting your flow. Two tips that usually improve the output: • Instead of capturing a whole screen, split it into smaller, natural sections and combine them with Aggregate Mode. This reduces noise and improves accuracy. • Zoom in before capturing dense text, tables, or formulas. Clearer source pixels give Snapdown more detail to work with. I’d love to hear your feedback and feature requests. I’m looking forward to improving Snapdown based on how people actually use it. Thanks for checking it out!
4
回复

@bsuffern Hey Broden - good work! Tried it out and like it! Happily paid the license! Wishing you lots of success!!

0
回复

@bsuffern 

The structure-preserving part is the bit that matters. I deal with a lot of scanned compliance documents, certificates, permits, inspection reports and every OCR tool I've tried turns a table of expiry dates into a paragraph of numbers with no way to tell which date belongs to which row.

Two questions: does Aggregate Mode handle a table that spans a scroll, where you capture it in two passes? And does running locally on Apple silicon mean it works on a machine with no network at all, that's a real constraint in some of the sites my users operate in.

Upvoted. Nice to see something shipped for a boring problem

0
回复

@bsuffern  I’ve found structured OCR becomes risky when it silently invents table cells. Do you preserve block-level confidence or source coordinates, or mark uncertain Markdown sections as needing review? That would make it much safer for personal-data screenshots.

0
回复

The Mac-only caveat I’d want to know before recommending this to my team: when you capture from a browser window, does it pull the rendered text from the DOM or does it run the OCR pipeline on the screenshot? For Notion and Coda docs specifically, the difference shows up in whether nested blocks and toggles come out flat or preserve their structure.

0
回复

@hazy0 Great question! Snapdown currently works purely from the screenshot—it doesn’t access the browser DOM or application data. That means it only processes what’s actually visible on screen. For things like Notion or Coda, collapsed toggles wouldn’t be captured because they’re not visible in the screenshot, while visible nested blocks are reconstructed from the visual layout by the OCR pipeline rather than the underlying document structure.

0
回复

Yeah Broden! Markdown era is here and you're a doing an amazing job on it. Congrats on this impressive launch

0
回复

@german_merlo1 Thank you very much for the support! I really appreciate the kind words.

0
回复
#10
Hand Wave
Turn sign language into speech with smart glasses
129
一句话介绍:Hand Wave 利用Meta智能眼镜的摄像头,将手语实时转化为文字和语音,帮助听障人士与健听人群在面对面交流中打破语言隔阂,实现无延迟、无需手机的跨平台沟通。
iOS Artificial Intelligence Lifestyle
智能眼镜 手语翻译 实时语音合成 端侧AI模型 无障碍沟通 开源神经网络 跨平台应用 隐私保护 听障辅助 FSBoard数据集
用户评论摘要:用户赞赏本地运行模型的低延迟与隐私优势,以及开源、离线可用的设计。核心疑问集中在:FSBoard是指拼数据集,是否只能逐字母识别,能否处理完整ASL手语语法?呼吁明确功能边界,避免“手语转语音”的过度承诺。
AI 锐评

Hand Wave的价值不在“翻译精度”,而在“场景重构”——它把无障碍工具从手机App的低头操作,迁移到眼镜的平视交互,这是体验维度的降维打击。本地模型+开源路线,直击AI助残产品“隐私付费墙”和“联网依赖”两大行业痛点,方向正确。

但产品目前最大的短板是技术边界不清。FSBoard本质是手指拼写数据集,对应的是逐字母拼读,而真实手语(如ASL)包含大量手势、表情、空间语法,两者复杂度相差一个量级。标语“turn sign language into speech”在营销上讨巧,却会让用户产生错误预期——聋人群体往往使用自然手语而非拼写,若实测仅支持手指拼写,口碑会迅速反噬。

另一个隐患是硬件绑定Meta Glasses。虽然声明跨平台,但主赛道绑死单一生态,一旦Meta调整政策或眼镜销量不及预期,项目将失去依托。建议团队尽快明确两件事:一是公开演示区分“拼读”与“手语语法”的支持级别,避免社区质疑;二是尽早发布Web版实用体验,脱离对特定硬件的依赖。

总体而言,这是少见的“硬件场景+边缘AI+开源”三位一体案例,但还需从“Demo级亮点”走向“残障用户真正日常可用的工具”。在无障碍领域,信任比技术更稀缺,别让过度承诺毁掉这个好起点。

查看原始信息
Hand Wave
Hand Wave turns sign language into text and speech using the camera on Meta smart glasses. It also works cross-platform (iOS + web). Under the hood is a lightweight, open-source neural network trained on Google’s FSBoard dataset and built to run locally across devices (wip).

I’m building Hand Wave to make sign-language conversations more accessible with the camera already on Meta glasses (and other devices too). Let me know what you think!

1
回复

running the model locally on-device is genuinely a cool move, keeps the latency low and the privacy story clean. love seeing open-source sign language work actually ship to glasses instead of staying in demo hell.

0
回复

Love that you built this on an open-source local-first model, since accessibility tools like this should never depend on a paywall or a connection to work.

0
回复

FSBoard is a fingerspelling dataset if I remember right, individual letters rather than full signs. so is this reading fingerspelled words letter by letter, or does it also handle actual ASL signs and grammar? those are pretty different problems and "sign language into speech" reads like it's promising the second one.

0
回复
#11
mpai
Make existing Codex and Claude Code sessions multiplayer
114
一句话介绍:mpai 是一款开源的终端多人协作工具,让开发者能直接加入队友正在进行的 Codex 或 Claude Code 原生会话,共享真实上下文并以实名身份参与提示,解决 AI 编程会话长期“单机”无法协作的痛点。
Open Source Developer Tools Artificial Intelligence
AI编程协作 终端多人会话 Claude Code Codex 开源工具 Tailscale组网 会话共享 实时上下文 MIT许可 macOS开发工具
用户评论摘要:用户普遍认可“免上下文交接”的价值,称其为自然协作方式。主要疑问集中在使用场景(是否仅为绕限额)、多人分工适配性、以及长链路归属问题。创始人回应:主场景是循环提示编排,保留宿主执行权,人类提示作为归属锚点。另有用户确认MIT许可支持商业使用,创始人建议客户端自控环境并谨慎试点。
AI 锐评

mpai 在“AI 编程协作”这块拥挤赛道上选了一个异常刁钻且务实的切入点:不试图重建 IDE,不做聊天聚合层,而是直接钻进 Codex 和 Claude Code 的原生终端会话里,把人作为“带名字的提示源”注入正在运行的 agent 上下文。这个定位精准踩中了当下 AI 编程最尴尬的裂缝——大模型能力越强,单人会话的信息孤岛越深,上下文交接成本反而越高。产品在信任与安全模型上展现出了老练的克制:宿主 Mac 保留执行权威,Guest 只能发提示,远程审批默认拒绝,且明确不伪装 agent 链式行动的归属权。这种“设计边界即产品哲学”的做法,让 mpai 更像一个会话放大器,而非又一款多人 pair tool。

但必须泼一盆冷水:当前实现深度绑定 macOS + Tailscale + 显式会话共享,这套组合实质上把产品限定在了高信任度的极客小团队场景。评论中关于“10人同项目分工”的核心质询并没能从创始人回复中获得令人信服的答案——用“循环提示编排”来回应协作场景,回避了多用户同时活跃修改同一会话时状态冲突和替换模型的根本问题。此外,Claude Code 受支持、Codex 仅托管模式可提示且独立版本只读,这一不对称表明产品能力受制于上游工具扩展性,而非自身意愿。MIT 开源和公开构建是加分项,但开源同样意味着大厂随时可以拿这套模型做进官方产品。真正值得关注的后续指标是:首批 10 个双人团队的中位加入耗时是否真能低于 5 分钟,以及这批用户一周后的留存率——这比任何 Demo 都更能说明 mpai 是否击中了真需求。

查看原始信息
mpai
Open-source terminal multiplayer for Codex and Claude Code. Join a teammate's explicitly shared native session from another Mac, arrive with the real context, and prompt with your name attached. Tailscale stays private; the host Mac stays in control.
AI coding got dramatically better, but the session stayed single-player. My cofounder Hudson and I already had our Macs connected with Tailscale. The missing layer was not another IDE or chat app—it was a way to enter the exact Codex or Claude Code conversation already in motion, understand the context, and add a turn with a real human name attached. That is what mpai does. I sent an attributed prompt from my Mac into Hudson’s existing Claude Code session; Claude received the teammate label and answered inside that exact session. This is an honest public alpha: macOS + Tailscale, explicit session sharing, Claude Code support, and managed-mode Codex prompting. Standalone Codex stays view-only by default because we will not race an active desktop task for a prettier demo. It is MIT licensed and built in public. I would especially value feedback on install friction, the sharing model, and the terminal interaction.
4
回复

That's pretty cool, but what are the actual use cases? We use Claude Code, and on our team, up to 10 people can work on the same project simultaneously, but each person is responsible for their own part. Or is this mainly designed to work around usage limits?

1
回复

@natalia_iankovych The primary use case for us has been running loop prompts and having mpai prompt teammates computer’s in accord with the earlier context. It broadens the orchestration possibilities and enables you always to have context on what your team’s working on without any friction or switching your existing AI interface.

1
回复

Love the idea of collaborating inside the same AI coding session instead of constantly sharing context back and forth. Feels like a much more natural way to work as a team. Congrats on the launch!

1
回复

Thank you — eliminating the context handoff is exactly the bet. We just shipped v0.4.11 so a host can create a private invite and ready room for one exact session in a single command. If you already have two Macs on Tailscale, would you be open to timing one real room? The five-minute checklist is here: https://github.com/godfaddaai/multiplayer-ai/issues/7

0
回复

@devyatkin Thank you, Alex—that handoff pain is exactly what pushed us to build it. The key for us is that nobody has to abandon Codex or Claude Code: a teammate joins the session already in progress, and their turn is named. If you try the alpha with a teammate, I'd genuinely love to know where setup feels rough.

0
回复

the decision to keep host execution authority is the right call, the second you let the guest drive, you've built a pair programming tool, not a session amplifier. curious how attribution surfaces when one person's turn kicks off a 20-step agent chain: does each sub-action stay attributed to the human who prompted it, or does the chain appear as agent output with a single human-turn anchor?

0
回复

@rnagulapalle Exactly—the human prompt is the attribution anchor. Today mpai records that turn under the guest's identity in the native transcript and audit; the downstream 20-step chain remains provider/agent output anchored to that turn, not falsely relabeled as 20 human actions. Remote approvals stay denied, so the host still decides execution. Per-tool-call provenance is a useful next layer, but we don't claim it yet.

0
回复

Launch-day update: v0.4.13 is live. The host still installs once; the teammate now pastes one version-pinned npx line and lands in the exact shared room — no global install, no setup, and no background service. Both founder Macs are upgraded, and the clean Homebrew lifecycle passed on macOS and Linux. The metric that matters next is outside use: first 10 two-person teams, median invite-to-room under 5 minutes, then a later-week return. Test checklist: https://github.com/godfaddaai/multiplayer-ai/issues/7

0
回复
Great work, so can I commercially use tailmate to run a prompt in my clients environment
0
回复

Yes—if you mean mpai, it is MIT-licensed, so commercial use is allowed. For a client environment today, I’d run it only on a client-owned Mac and tailnet the client controls, have them explicitly invite you and share the exact session, and start with a non-sensitive pilot. The host keeps execution authority; mpai exposes no arbitrary shell and cannot bypass approvals. It is still a macOS public alpha, not an enterprise SLA product yet. If you test it, I’d love your install-to-first-room time and where the flow breaks.

1
回复

@arun_prasad06 If you want to run the client-controlled pilot, the exact two-Mac checklist and privacy-safe feedback template are here: https://github.com/godfaddaai/multiplayer-ai/issues/7 lmk

0
回复
#12
MascotAI
Animated SVG mascot studios for apps that need a personality
109
一句话介绍:MascotAI 是一个为 App 提供可定制动画 SVG 吉祥物的工作室工具,专解决产品界面中“通用头像无灵魂、定制插画太贵”的痛点,让开发者在空状态、加载、错误等关键交互节点用低成本赋予产品人格化表情。
User Experience Developer Tools Artificial Intelligence
动画吉祥物 SVG组件库 产品UI设计 空状态设计 加载动效 错误提示 开发者工具 品牌人格化 可交互组件 商业授权
用户评论摘要:用户关注点集中在:1) 吉祥物应优先覆盖空状态、加载、错误等“挫败场景”而非单纯笑脸;2) 付费模式上,希望“先看结果再付费”,担心支付前流失;3) 询问同一角色在多手势间的风格一致性及商业授权范围。
AI 锐评

MascotAI 的切入点很聪明——它没有去和 Midjourney 拼“生成一张好看的脸”,而是把吉祥物拆解成可编程的“状态机组件”。这实际上是在赌一个隐性共识:当 App 出错或加载时,用户需要的不是视觉愉悦,而是“被陪伴的耐心”。这个洞察在评论区被精准点出,说明核心用户确实有痛感。但真正的风险在于,它目前可能只是“高级的素材包”,而非“产品人格的生成系统”。评论中关于“角色一致性”“授权范围”的追问,暴露了它离“工作室”的定位尚有差距——如果只是预制件拼装,那和买一套现成的 Lottie 动画有何本质区别?更致命的是付费墙设计:吉祥物是典型的“感性消费”,用户必须看到自家产品上的实际效果才能产生信任,而“支付后才生成”的流程恰好扼杀了这种冲动。建议 MascotAI 把免费试用区做成“口红试色机”——允许用户上传自己的 UI 截图,实时看到不同角色在真实界面里的互动效果,再决定付费。另外,它应该瞄准那三个“尴尬时刻”(空/错/加载)做深度模板,而不是贪多求全做庆祝动画。否则,它最终只会沦为 Figma 社区里一个好评但低频的插件,成不了“人格化基建”。

查看原始信息
MascotAI
Hey hunters! I’m the maker of MascotAI. I kept seeing apps launch with great products and forgettable faces. Illustration budgets are huge; generic AI avatars feel lifeless in product UI. So we built studios the way we’d ship them ourselves: animated SVG packs with gestures, themes, and parts you can actually toggle not one-off PNG images.

The gestures worth shipping aren't the happy ones. Empty state, loading, and error are the three moments an app actually needs a face, because that's when it's failing the user and the mascot is the only thing buying patience. Everyone builds wave and thumbs up first, then ships a plain grey spinner anyway. And agreed with Christoph on the paywall. A mascot is a taste purchase and you can't sell taste off someone else's sample character.

1
回复
Would love honest feedback on the generate flow and what gestures you wish every app mascot had. Happy hunting.
0
回复

@guccibase Would love a setup where I pay only once I see the results. Animated a mascot before for https://donethat.ai with a freelancer and was curious to see how it compares but I'd assume a lot of people drop off at the payment screen for an app they don't trust

1
回复

Congratulations on the launch!
Does a pack keep one character consistent across all gestures, or is each gesture generated separately? Also, what does the license allow for commercial use inside a paid product?

0
回复
#13
PassiveShorts
AI Faceless Video Generator for TikTok & YouTube
109
一句话介绍:PassiveShorts 是一款面向 TikTok 和 YouTube 的 AI 无人出镜视频生成器,用户只需选定主题、声音和发布时间,即可全自动完成从脚本撰写、配音、配图、字幕到定时发布的完整视频生产闭环,解决了普通人做短视频频道坚持不下去、日更太累的痛点。
Social Media Artificial Intelligence
AI视频生成 无人出镜短视频 自动化发布 TikTok工具 YouTube Shorts 内容自动化 被动收入 AI配音 批量内容生产 视频模板
用户评论摘要:用户认可其解决日更疲劳的价值,但集中担忧两点:一是全自动发布缺乏人工审核环节,可能因AI内容出错导致账号信誉受损;二是平台对AI生成、低质量批量内容的打击政策趋严。另有用户询问最佳表现赛道及真实观众反馈,开发者回应称已有频道单视频达1.5k+播放,并强调可设置草稿或私密发布以规避风险。
AI 锐评

从产品形态看,PassiveShorts 与其说是一个视频生成器,不如说是一个“内容生产资料代工厂”。它精准捕捉了“想靠短视频赚钱但懒得动手”的投机性需求,把脚本、配音、剪辑、发布这四座大山压缩成一次性的“设定动作”,本质上是在出售时间杠杆——这是它最核心的价值,也是它最致命的软肋。

评论区的质疑非常致命:没有任何人工干预的“自动驾驶”模式下,脚本内容的真实性、合规性与账号长线生存能力完全被置于风险之中。平台对“mass-produced, low-effort AI content”的算法围剿是真实存在的,一味强调“全自动”等于主动给平台递刀。开发者的回复透露出一种“给用户提供草稿/私密模式”的补救措施,但这是工具功能的便利,而不是产品逻辑的根本修正——如果默认状态不是“先审后发”,那这个工具培养出来的,大概率是批量制造的低质账号,而非可持续的创作者。

真正的价值洼地不在于“替用户发完所有视频”,而在于“帮用户把制作流程压缩到10分钟以内但保留人工决策权”。如果PassiveShorts能把默认流程改为“AI生成后强制人工确认”,并内置事实核查或来源标注功能来对抗“一本正经胡说八道”的AI幻觉,它就能从“批量内容垃圾站”升级为“创作者的高效合伙人”。否则,这只是一个加速账号死亡的工具,用户省下的时间最终会以更快地被平台限流的代价偿还。就目前而言,它更适合用来做测试选题和填充频道的“第二阵容”,绝不能作为主力账号的唯一内容来源。

查看原始信息
PassiveShorts
AI faceless video generator that auto-posts to YouTube and TikTok. Pick a topic, a voice, and a schedule. We write, voice, caption, and post every Short for you.
Hey Product Hunt 👋 I'm the maker of PassiveShorts, and I'm really excited to finally share it here. This started with a simple frustration: everyone says "just start a faceless YouTube or TikTok channel," but nobody tells you it's a daily grind. Write a script, generate a voiceover, find visuals, edit it, add captions, export, upload, repeat. Most people (me included) burn out in the first two weeks, long before the algorithm ever rewards them. So I built PassiveShorts to run that entire loop for you. You set it up once: Pick a topic from 5 ready-made niches (Scary Stories, Jokes, Life Pro Tips, Today I Learned, You Should Know) or write your own Pick a look from 19 visual styles (Photorealistic, Cinematic, Anime, Kurzgesagt, Claymation, and more) Pick a voice from a library of natural AI voices, and a caption style that matches your brand Pick a schedule, connect YouTube or TikTok, and choose your days After that it runs itself. We write the script, generate the voiceover, create the visuals, add the captions, and publish every video to your channel automatically. No editing, no face, no manual uploads. A few things I care about that make it actually usable: You stay in control. Post public, private, or straight to your TikTok drafts so you approve each one before it goes live. Run up to 10 series at once across different niches or channels, all from one dashboard. The videos are yours with full commercial rights. I'd genuinely love your feedback, especially on the visual styles and voices. What niche would you point it at first? And if there's a platform or feature you wish it had, tell me, I'm reading every comment today. Thanks for checking it out 🙏 Vijayabhaskar J
1
回复
@vijayabhaskar_j Congratulations on launching PassiveShorts I can definitely see this helping creators stay consistent with content. I'm curious, which niche has produced the best results so far finance, motivation, tech, storytelling, or something else? Would love to hear what you've learned from your early users.
0
回复

the fully-automated pipeline is the part that gives me pause, not the AI voice or captions specifically. YouTube and TikTok have both been tightening enforcement against mass-produced, low-effort AI content this year, and "pick a topic and a schedule, we post everything" sounds like it's optimized to get a channel flagged rather than to build one that lasts. is there a human review step anywhere before something goes live, or does it genuinely post on autopilot end to end?

0
回复

The risk here isn't video quality, it's that nothing in the loop has a human before publish. One Today I Learned script that states something false confidently goes out under the user's channel name and they find out in the comments. I'd make hold for review the default for the first 10 videos, then let people switch it off once they trust the scripts. Costs you nothing on the demo and saves the accounts that would have churned angry.

0
回复
@asadmalik901 True, that's why I've added option for users to write custom script and they can set it to post only to private or draft mode, so people can verify the content before posting. And the slideshow creator is completely manual.
0
回复
Do you have any results how people react on these AI generated videos?
0
回复

@busmark_w_nika Hi, I've been running 3 YouTube channels for a week now, and honestly, about half the videos get 1.5k+ views, while the other half struggle to reach even 10 views. Might be because they're new channels, but as far the reactions, judging from the comments alone, they're well received, just as any normal video would've received.

0
回复
#14
Inventory
Search every AI Agent & IDE Conversation
104
一句话介绍:Inventory 是一款本地优先的开发者工具,通过统一索引所有 AI 编程助手(如 Cursor、Claude Code)的对话记录,解决开发者跨工具查找历史技术决策和调试思路时“搜不到、找不到”的痛点,提供一站式离线全文搜索。
Productivity Artificial Intelligence Tech
本地索引 AI对话搜索 开发者工具 隐私安全 IDE插件 会话管理 知识库检索 付费买断 本地优先 效率工具
用户评论摘要:用户高度认可本地化存储对敏感代码的保护价值,但集中担忧:1) 当前仅限个人使用,团队协作与权限管理亟待支持;2) 工具更新后本地格式变动可能导致索引失效;3) 明文索引文件会成倍放大单机泄露风险,建议加密存储。开发者已回应将修复格式兼容性并考虑团队功能。
AI 锐评

Inventory 踩中了 AI 编程浪潮下的一个隐蔽但高频的痛点——对话资产的“熵增”。当开发者每天在多个 Agent 之间切换时,真正的智力成果散落在各自孤岛中,信息贬值速度极快。它用“本地独享+买断制”精准切入了企业级用户对保密性的敏感神经,这比任何云同步方案都更具说服力,也避开了一大堆 SaaS 合规麻烦。

但产品的护城河远谈不上稳固。评论中暴露的两个短板恰好命中了死亡三角:存储格式依赖与隐私悖论。前者意味着只要 Cursor 或 Claude Code 更新存储结构,Index 就会瞬间瘫痪,这决定用户是否敢把它当“正式记忆”用;后者则是逻辑硬伤——本地单一索引让原本分散的低价值碎片,聚合成了极易盗取的“高层级情报”,没有加密的明文索引反而是帮黑客做了数据清洗。团队承诺下个版本解决,但路线图过窄。

更严峻的是,当前产品完全困在“单机工具”维度。用户评论区已明确点出团队协作与权限隔离的需求,这不仅是商业化的破局点,更是从“个人插件”升级为“团队基础设施”的唯一路径。如果不尽快定义 AI 辅助编程的团队记忆权限层级,大厂随时可能在 VS Code 或 IDE 底层原生实现同等搜索功能,届时买断制工具的生存空间将被瞬间碾碎。总的来说,方向值得肯定,但执行深度和战略视野决定了它究竟是过渡期的临时补丁,还是真正的记忆层奠基者。

查看原始信息
Inventory
Inventory is the private, local index for every Cursor, Claude Code, Zed, Codex and Kiro conversation. No signups, no cloud, one-time fee.

This is a real gap for teams, not just individuals. Half the useful context in my company now lives in one-off chats nobody can find two weeks later. Does Inventory work across a team's conversations with permissions, or is it scoped to a single person's history for now?

2
回复

@artem_fedorovich for now it is focused towards individuals like me, as using multiple tool i was not able to find chats. Hence build this which is simple, local and easy to use.

But the use case which you told is excellent and i have noted it down. I will plan to implement it next release.

Would appreciate a share with your friends or colleague who uses multiple agents and have this same concern. Thanks

0
回复

Got there from your comment! :) Wishing GL!

1
回复

@busmark_w_nika Grateful 🤝

0
回复

The local-only decision is the interesting one. I've got two years of Cursor and Claude Code history sitting in places I can't search, and the reason I've never tried a cloud tool for it is that those conversations contain client context I'm not willing to upload.

Two things I'd want to know: does it index historical conversations or only from install onwards? And when a tool changes its local storage format in an update, how much breaks?

Second one matters because that's the failure mode for anything indexing someone else's files, and it's the thing I'd need to trust before paying a one-time fee.

Upvoted, saw your five in Nika's thread, which is how I found this.

1
回复

@fasathor Hello, thank you for the agreeing with my decision of local-one. To answer both of your questions

Firstly Yes it indexed Historical, all of it. If one tool breaks it localstorage that tool's index will stop working for now. This is first public release and this concern i also had on which i am working on finding a solution that will work local only. I am hoping in next update i will try to solve that problem first as its on top of my checklist.

Thank you again for pointing this out.

0
回复
@fasathor Good News, your concerned has been addressed and new release shipping soon🚀
0
回复

no cloud is a real answer to one worry but it kind of creates a smaller version of the same problem: right now my secrets and half-finished thoughts are scattered across five separate tools' storage, which is annoying but also means no single file on disk is that valuable. an index of literally every agent and IDE conversation in one place, searchable, is a much juicier single target for anything else running on the machine. is the index itself encrypted at rest, or is it plain text once it's built?

0
回复

Hey Product Hunters 👋

I'm Neil, maker of Inventory.

What inspired me to build this

I kept losing conversations. Not because I deleted them. Just because they pile up across Cursor, Claude Code, Zed, Codex, Kiro... and there's no way to search any of it.

I'd vaguely remember solving something in a session from two weeks ago. Which tool was it in? Which project? No idea. So I'd spend 20 minutes hunting, or just solve it again from scratch.

Browser history doesn't help. The apps themselves have weak or zero search. And honestly I didn't want some cloud tool indexing my private dev conversations anyway.

So I built Inventory. It runs locally, indexes everything on your machine, and gives you one search bar across all of it. No account, no sync, no subscription. One time and it's yours.

The problem

If you use more than one AI tool, you know how this goes. A conversation where you figured out a gnarly bug. A prompt that finally worked. An architectural decision you reasoned through with Claude. It's all sitting somewhere on your machine but it might as well be gone.

AI agents are becoming a real part of the workflow now and nobody built the memory layer for it. That's what Inventory is.

Happy to answer anything.
Would love to hear how others are managing this 🙌

0
回复
#15
Doxy
Markdown & HTML editor, without the LaTeX pain
100
一句话介绍:Doxy 是一款基于浏览器的 Markdown 与 HTML 编辑器,旨在让用户无需掌握 LaTeX 语法或忍受编译等待,即可快速撰写并实时预览格式规范的文档,解决科研、求职等场景下“轻量排版”与“复杂模板”之间的效率痛点。
Design Tools Productivity Tech
Markdown编辑器 HTML编辑器 在线文档编辑 LaTeX替代 实时预览 浏览器工具 文档排版 轻量写作 学术写作 效率工具
用户评论摘要:用户普遍认可其轻量、即时预览和零配置体验;核心质疑集中在数学公式渲染缺失(对比 Overleaf 的硬伤),以及 LaTeX 模板(如期刊、简历)导入导出不完整可能导致“写一半还得回 LaTeX”的切换阻力;作者确认完整 LaTeX 导入导出在规划中。
AI 锐评

Doxy 的定位精准地踩在 Overleaf 的“烦”与纯 Markdown 的“弱”之间,用零编译、即时预览的流畅体验收割了 LaTeX 的“轻度叛逃者”。但其产品价值目前停留在“编辑器”而非“解决方案”层面——评论中两条最高质量的反馈直指命门:其一,数学公式支持缺失,等于砍掉了 Overleaf 用户最核心的肌肉记忆;其二,对期刊/大学模板的兼容性含糊其辞,意味着它无法成为文档流程的终点站,而仅仅是“看起来更舒服的草稿纸”。这种“95% 的完成度”反而制造了更糟糕的双重劳动:用户在 Doxy 写初稿,再回 LaTeX 补公式和调样式,切换成本比纯用 LaTeX 更高。Doxy 真正该赌的不是“替代 LaTeX”,而是瞄准“不需要公式、不需要强制模板”的垂直场景——比如技术博客、内部 wiki、产品文档、简历(非学术版)。在这些领域,它的即时预览和轻量感才是决定性优势。如果团队把路线图优先用于完善 LaTeX 导入导出和基础公式渲染(哪怕只是兼容常见子集),并明确列出“可完全产出的文档类型清单”,它才有资格从“有趣的玩具”进阶为“可靠的生产力工具”。否则,它将永远活在 Overleaf 的阴影下,成为又一个“看起来不错但没人敢依赖”的编辑器。

查看原始信息
Doxy
Doxy is a browser-based editor for creating clean, professional documents with Markdown and HTML without the complexity of LaTeX or the frustration of compile times. Write, format, and preview your work in one simple, fast editor.
Hey PH! 👋 I'm ilies, the builder of Doxy. The idea came from using Overleaf during uni , I loved the workflow but always wished I could just write in markdown instead of LaTeX. So I built it. Happy to answer anything. What would make you actually switch your writing workflow to Doxy?
3
回复

@ilies_mraihi the honest blocker for me isn't the markdown vs latex syntax, it's math. overleaf's real value for a lot of people is that inline equations render properly, and skipping that to dodge latex's complexity solves the part people didn't mind and drops the part they'd actually miss. does doxy handle equations at all, or is this aimed at docs that were never going to have them anyway?

0
回复

Omg, finally! I've been wishing for an easier way to edit LaTeX resumes for ages. Definitely giving this a try... Wondering if full LaTeX import/export is supported?

1
回复

@beebombshell Thanks! Full LaTeX import/export is planned for an upcoming feature, so you’ll be able to work with your existing LaTeX resumes more seamlessly. Stay tuned! 🚀

1
回复

The live preview is instant and the markdown rendering looks clean out of the box, no setup needed. Honestly surprised how lightweight it feels compared to opening a full LaTeX editor for quick docs.

0
回复

The switch won't be decided by the writing, it'll be decided by the one page you can't reproduce. Anyone submitting to a journal or a university has a template they didn't choose, so if Doxy gets 95% of the way and then can't do the numbered equations or the bibliography style, they write in Doxy and finish in LaTeX, which is worse than never switching. I'd name the document types you can fully produce today and say nothing about the rest. Shorter page, much easier decision.

0
回复
#16
MacDupl
Clone any Mac app into a fully isolated instance
99
一句话介绍:MacDupl 是一款 macOS 工具,能将你已安装的 Mac 应用克隆出完全独立的副本,实现同一应用的多账号、多数据并行使用,摆脱频繁登出登入的困扰。
Mac Productivity SaaS
macOS 工具 应用克隆 多开应用 多账号管理 数据隔离 Keychain隔离 效率工具 本地应用 开发者工具 付费软件
用户评论摘要:用户关注克隆后的凭据与通知是否真隔离、应用更新后克隆是否失效、固定路径写入与许可证激活问题。开发者回应称通过改 bundle ID 隔离 Keychain,Electron 应用用 user-data-dir,原生应用用 $HOME 覆盖,但硬编码路径和许可证激活因应用而异。
AI 锐评

MacDupl 切中了一个真实且高频的痛点:同应用多账号切换的割裂体验。它的价值不在于“虚拟机级隔离”或“容器级安全”,而在于用一个轻量、快速、符合 Mac 直觉的方式(APFS 写时复制 + bundle ID 改写)让用户“多开应用”像复制文件一样简单。这本质上是对 macOS 应用沙箱机制的一次巧妙绕行,换取的是极速克隆与近乎为零的磁盘占用。

但“隔离”这个卖点需要谨慎对待。从开发者回复看,它对 Electron 应用(Slack、Claude 等)效果尚可,因为这类应用有统一的数据目录参数;对原生应用则依赖是否硬编码路径,兼容性难以保证。更关键的是,它明确不支持 Mac App Store 沙盒应用,这直接砍掉了一大批主流工具(如很多 MAS 独占应用)。所谓“完全隔离”更像是一个理想上限,实际体验取决于每个应用的脾气,而非 MacDupl 自身的稳定性。

另一个被轻描淡写的点是许可证。对于依赖在线激活或有 node-locked 授权的商业应用,克隆后可能要求重新激活甚至被封。MacDupl 对此并未有系统化方案,而是“看应用心情”,这对企业用户或重度付费用户是个不小的顾虑。

价格策略值得肯定:19 美元一次性买断、送一个永久免费克隆,且无遥测、无订阅,在这个订阅泛滥的 mac 工具圈算清流。但它的目标市场其实是“专业多开玩家”——Freelancer、远程工作者、运营人员,而非普通用户。若兼容性列表不能快速扩大、对原生应用的隔离失败率不能降到个位数,它很容易沦为“每天都能用但关键时刻不敢用”的工具。本质上是把 macOS 的灵活性做成了产品,但系统的边界就是它的天花板。

查看原始信息
MacDupl
MacDupl clones the Mac apps you already use into fully isolated instances — separate logins, separate data, separate Dock icons. Work and personal, side by side.

Hey Product Hunters 👋
I'm Sigit, maker of MacDupl.

What inspired me to build this
I was tired of logging out of my personal Slack just to log into a client's, over and over 😭

Tried browser profiles, separate Mac users, extra browsers — all annoying in their own way.

What I actually wanted was dumb simple: another copy of the app, its own icon, own login, sitting right next to the original.

So I built it. macOS actually makes this possible with APFS copy-on-write — cloning a 700MB app costs basically nothing on disk.

A few weekends later, MacDupl was born 🚀

The problem
If you use the same app for work and personal — or juggle multiple client accounts in one tool — you know the loop: log out, log back in, log out again. Browser profiles half-solve it for browsers, but there was nothing for native Mac apps. I wanted a real second instance of the app itself: separate login, separate data, its own icon in the Dock — not a workaround.

How the approach evolved
Early on I looked at container/VM-based isolation to sandbox apps more heavily — more "bulletproof" in theory, but it added real complexity and UX tradeoffs that worked against the whole point (this was supposed to feel instant, not heavy). I ended up going with a lighter approach: unique bundle identifiers plus separate data directories per clone, using `--use-mock-keychain` so credentials stay isolated without ever touching the shared macOS Keychain. It's simpler, and it's fast — clones build in about 2 seconds.

That constraint also shaped what MacDupl *won't* do: some App Store / sandboxed apps (their entitlements and shared containers make real isolation impossible without Apple's own provisioning) just can't be cloned. Rather than fake it and quietly share the original's data, I decided to exclude them outright and be upfront about it. Sandboxed apps aren't supported — accuracy mattered more to me than a longer compatibility list.

Where it landed:

  • 7-day free trial, unlimited clones

  • After that, 1 clone stays free forever

  • $19 one-time unlocks unlimited — no subscription

  • Zero telemetry, zero analytics — the only network calls are license and update checks

    Would love your feedback, especially on apps not yet on my https://macdupl.app/compatibility or anything odd on the native-app tier. I'll be around all day 🙏

2
回复

@sigit_kusuma The multi-account case caught my eye, since juggling logins across clients has always meant a mess of browser profiles and a second laptop. Does each clone keep fully separate credentials and notifications, and does it survive an app update without breaking?

0
回复

Two Slack accounts is the honest use case, but the interesting one is what "fully isolated" means to an app that assumed it was alone. Keychain items are shared by bundle ID, and a lot of Mac apps write to fixed paths in Application Support rather than their own container. Do you rewrite the bundle ID per clone, and if so what happens to the license — does the second instance ask to be activated again?

0
回复

@ark_y_k Since the bundle ID changes with each clone, Keychain isolation is essentially free because macOS already uses bundle ID to identify keys. 🙏

The tricky part is apps that write to a fixed path instead of using their own bundle ID. For Electron/Chromium apps like Slack and Claude, i use —user-data-dir, which works well. For native apps still in beta, i use a $HOME override. This is where things get a bit tricky if the app hardcodes paths. 😅

Whether the clone asks for its own license activation depends on the app, and I haven’t audited that across all of them. MacDupl’s license is per-Mac, so it’s not related to this

0
回复
#17
CoachAI
Your iPhone camera watches your form, rep by rep
99
一句话介绍:CoachAI 利用 iPhone 摄像头实时追踪用户的动作轨迹,在力量训练场景中自动计数并纠正姿势,解决健身爱好者“无人指导、动作易错、易受伤”的核心痛点,且全程数据本地处理不上传。
iOS Health & Fitness Artificial Intelligence
AI健身教练 动作识别 姿势纠正 实时计数 iPhone应用 计算机视觉 力量训练 本地隐私计算 健身科技 运动分析
用户评论摘要:用户认可产品创意与“先体验后填表”的交互改进,但重点担忧两点:一是手机单角度拍摄无法捕捉深蹲/硬拉等复合动作的深度与脊柱形态,可能给出“看不见但正确”的误判;二是建议未来拓展至网球等挥拍类运动,并探索AirPods实时语音反馈的可能。
AI 锐评

CoachAI 的诚意在于它务实回答了“手机能否看见坏动作”这一关键命题,并大胆采用了“单次动作证明价值”的引导流程,值得肯定。但它的短板恰恰也藏在“看见”这个词里——当前的 AI 视觉方案本质上是对二维视频流的姿态估计,这决定了它对“深度”与“遮挡”的感知是先天残缺的。评论中那位用户提出的担忧极其专业且致命:当手机架在侧面无法判断脊柱是否圆屈时,系统给出的“合格”判断会成为一种危险的权威背书,诱导用户盲目加重,这比不给反馈更危险。

更深层的问题是,产品目前的壁垒是“API调用”而非“数据飞轮”。姿态估计算法早已开源化,真正的护城河在于能否覆盖更多动作变体、更复杂的训练环境,以及积累足够多的“错误动作”标注数据。早期的粗糙可以原谅,但在“误判导致受伤”这一高风险场景里,粗糙不是体验问题,是责任边界问题。建议团队优先开发并展示“视角置信度提示”——在系统看不清时应明确说“不知道”,而不是硬猜。这是从“玩具”走向“工具”的门票,但目前在产品介绍和评论回应中未见这一功能的具体说明。方向正确,但距离一个真正值得信赖的“口袋私教”,还有一整个“明知不可为而不为”的技术伦理跨越。

查看原始信息
CoachAI
CoachAI uses your phone's camera to count your reps and correct your form in real time - a personal trainer's eyes in your pocket.
I built CoachAI because of a gap I kept watching in gyms: people show up consistently, train hard, and still get hurt or plateau — not because they lack discipline, but because nobody is watching how they move. trainers are expensive or don't fit into the schedule. Most people just guess. So the core question became: can a phone actually see a bad rep? Turns out yes. CoachAI uses the iPhone camera to track your movement in real time and tell you when your form breaks down — all on-device, nothing uploaded. Around it sits a program engine that adjusts properly instead of shuffling random exercises. The biggest shift in my process was order of operations. My original onboarding asked for goals, height, weight, injuries — five screens before you ever saw the thing that makes the app different. People bounced. I've since flipped it: you do one tracked rep first, then we ask questions. Show the magic, earn the form fill. On process: I shipped this before I was comfortable. There are rough edges I'd normally have spent another three months sanding down in private. But a polished app nobody has used is just a very expensive opinion. I'd rather have real people telling me what's wrong than keep guessing on my own. Still early, still rough in places. If you try it, I want the harsh feedback — especially on the tracking accuracy. Try it and see if it catches your form breaking down. That's the part I'm proudest of, and the part I want people to try out. iOS 17+, free to start: https://apps.apple.com/app/coach...
5
回复

I love the idea. I am curious if you have thought about using this for other sports? I recently started playing tennis again and would love something that could analyze my swing and give me feedback. The setup my be a little tricky but you could have airpods in and get realtime feedback.

0
回复

respect for shipping this rough and asking for harsh feedback. the part I'd worry about is camera angle on the heavier compound lifts - a phone propped up to one side can miss depth or spinal rounding on a squat or deadlift that a trainer standing at the right angle would catch immediately. if the app gives a thumbs-up on form when the angle just didn't have visibility into the thing that actually matters, that's arguably worse than no feedback at all, since people will trust it and load up more. is there anything that tells the user when the angle itself isn't good enough to judge a given movement?

0
回复

congrats on the launch! I'm wondering what the different applications of this tool are or if it can analyze all types of movements.

0
回复
#18
Murmell
Cloud canvas where your team and AI agents works together
99
一句话介绍:
Software Engineering Developer Tools Artificial Intelligence
云端协作画布 AI代理编排 多人协同编程 远程开发环境 文件锁机制 Git集成 多代理并行 团队AI工作流 浏览器IDE 智能体调度
用户评论摘要:用户核心疑问集中在三处:一是文件锁粒度,质疑整文件锁只会把冲突下推到下游,希望支持函数或代码块级锁定;二是代理崩溃后锁释放问题,担心无人值守时死锁阻塞他人;三是工作可视性不足,认为仅“在场状态”无法预防两个代理做同一件事后静默重复提交,缺乏任务级声明机制。
AI 锐评

Murmell切中的痛点真实存在,但它目前解决的是“痛点的一半”。产品核心理念——把代理和人类搬进同一云端房间,用文件锁避免互相覆盖——本质上是将传统IDE的协作模式平移到AI代理场景。这不是坏主意,但它的护城河浅得一眼见底。

从用户评论可看出,真正的技术深水区并非“抢文件”,而是冲突定义。整文件锁是粗暴的互斥信号量,只阻止了写入碰撞,却拦不住逻辑层面的语义冲突。两个代理各持不同文件,一个改调用方、一个改被调方,代码合并零冲突,构建却炸了——这是分布式系统中最经典的“无碰撞但错误”问题,Murmell目前没有给出比Git更聪明的答案。

更致命的是死锁与失效管理。云端代理无人值守,一旦持有锁的代理崩溃,锁如何超时回收?评论中已有用户追问,产品页却未见明确机制说明。若线程崩溃导致文件锁永久悬挂,协作效率会比本地微冲突更灾难。

另一层更深的隐患被一条评论精准说出:代理不会像人一样“看到别人在打字就停手”。这意味着,仅靠文件锁和presence indicator解决的是代码层,而非任务层。两个代理可能各自完成一套完整实现,都在Git上落干净,但功能重复——这是合并工具永远吵不出来的错误类型。

诚实的评价是:Murmell的方向是对的,但以当前形态,它相当于把“谁抢到文件谁写”的规则搬上云端,离“多智能体协调调度”还有两个版本的距离。值得肯定的是,它支持多款主流代理(Claude Code、Codex等)并主动输出到Git,降低了试错门槛——但在文件锁、任务声明、失效锁回收这三个机制层面成熟之前,它更适合作为团队尝鲜工具,而非生产环境的协作基座。真正的价值壁垒在于能否从“文件互斥”进化为“意图互斥”,看到那一步,它才配称canvas,而不只是共享桌面。

查看原始信息
Murmell
Murmell is a shared cloud canvas where your team and AI agents work in the same room, on the same repo, with a preview and more coming in the future. Close your laptop and the work keeps going. Agents claim files before they write, so people and agents can move at once without overwriting each other. Run Claude Code, Codex, Kimi, and OpenCode together today, with more agents on the way (OpenClaw, Hermes, and more), and your work lands back in git, so you can always find your projects there.

Hey Product Hunt. I'm Moss'Ab, and I built Murmell.

Last year at a hackathon we had three people, four AI agents, and somehow still one laptop everyone was afraid to close.
Half the night went to "who's on which file" and "wait, my agent died when I shut the lid."

So I built Murmell: a shared cloud canvas in the browser where Claude Code, Codex, and your team work on one repo, on a cloud machine. Close your laptop, they keep going. Same room, a preview in the canvas, and the work lands back in git.

More is coming next, including iOS and Android simulators in the canvas so you can see mobile builds the same way.

I built most of this with Claude Code. Once it was solid enough, I started building Murmell with Murmell.

Launch offer: free for the first week, plus $60 of Claude Code credits.

Curious: when you ship with agents on a team, what breaks first for you, the coordination, the laptop, or the merge mess at the end?

murmell.com

3
回复

Hey👋 What a killer hackathon-inspired product.. congrats on the launch. Quick question how fast does a fresh cloud workspace spin up when importing a massive multi-repo project?

0
回复

@moss_ab_mirande_ney the merge mess, every time. coordination i can shout across the room to fix and a dead laptop is annoying but recoverable, but the conflict where two agents touched the same function differently at 11pm is the one that actually kills a night. is the file claim whole-file, or something finer like a block or function range? asking because a whole-file lock just pushes the same fight downstream to whoever's queued behind it.

0
回复

File level claims solve the loud half. Two agents can hold completely disjoint files and still both rewrite the same contract, one edits the caller and one edits the callee, nothing conflicts and the build breaks somewhere neither of them was looking. The thing I'd want on the page is what happens to a claim when the agent holding it dies. Nobody's at the keyboard on a cloud machine, so a stale lock is silent and it's sitting on exactly the file the next person needs.

1
回复

you asked what breaks first. from the shared inbox side it is coordination, but not the part people expect.

the merge mess is loud. git tells you, someone fixes it, everyone learns from it. the failure that actually costs you is two actors doing the same work without colliding at all. both finish, both succeed, nothing conflicts, and you find out downstream or not at all.

we get that version every day. two people open the same conversation, both answer, the customer gets two different replies and neither of them did anything wrong. in code you would at least get a conflict. when the work leaves the system, you just get two sends.

agents sharpen it, because a person hesitates when they see someone else typing. an agent does not hesitate and does not look.

so does the canvas have a way to claim something, a file, a task, whatever the unit is, or does it show presence and leave the rest to people noticing? presence tells you someone is in the room, not what they have taken.

0
回复
Now can I use this work with my clients agents ?
0
回复

@arun_prasad06 

Hey Arun, good question.

If you mean working with your clients in the same room: yes. You can invite them onto a Murmell canvas, share the repo, and run agents there together (Claude Code, Codex, Kimi, OpenCode today).

If you mean plugging in agents your clients already run outside Murmell, that depends on which ones.

Tell me what they use and I’ll say if it’s already supported or next on the list.

1
回复
@moss_ab_mirande_ney Like query their Claude code to get an audit to share with us, instead of an sdk to connect with their platform, if we could ask their Claude code to execute in their environment
0
回复
@moss_ab_mirande_ney also to query their db from their system cause if I need to know something without complete transfer of sensitive data from client environment
0
回复
#19
gesture.live
Play live electronic music with your hands using your webcam
98
一句话介绍:gesture.live 通过普通摄像头捕捉手势,让音乐爱好者无需实体乐器,即可用双手实时演奏和弦、旋律、鼓点与效果,解决即兴创作与演奏场景中设备门槛高、操作复杂的问题。
Music User Experience Electronic Music
手势音乐 摄像头交互 电子音乐演奏 AI音乐工具 实时音频 Web应用 无乐器演奏 音乐创作 手势识别 现场表演
用户评论摘要:评论关注两点:一是舞台或昏暗灯光下手势追踪的可靠性,质疑其仅适合卧室场景;二是音符量化与延迟问题,担心30fps摄像头带来时序误差,影响演奏的人性化“推拉”感。开发者回应称和弦已量化,旋律为实时,尚未进行现场测试。
AI 锐评

gesture.live 的价值不在于“用摄像头代替MIDI控制器”这个表层创新,而在于它重新定义了电子音乐演奏的入门成本与身体表达边界。它把复杂的和弦系统压缩到单手操作,释放另一只手去控制旋律与节奏,这本质上是将“演奏”从硬件依赖中解放出来,变成一种近乎本能的肢体语言。然而,其真正的天花板恰恰卡在技术物理极限上:30fps的采样率带来的时序抖动,在音乐语境下是致命的——量化虽然保证了“不跑调”,却牺牲了微 Timing 产生的“人味”,这让它更接近“音乐玩具”而非“演奏工具”。评论里那位提问者的质疑一针见血:舞台灯光和复杂背景下的追踪鲁棒性,决定了它能否从卧室走向Livehouse。目前,它的最佳场景可能是音乐教育、儿童启蒙或社交娱乐,而非严肃表演。开发者若想突破,需要在算法端引入预测性追踪或融合手机IMU数据来补偿延迟,否则这款产品只能停留在“惊艳的Demo”层面,难以成为音乐人工作流中的常驻工具。不过,它确实指出了一个未来方向——当算力与视觉模型足够强大时,身体即乐器,舞台即交互界面,gesture.live是这条路上的早期探索者,虽不完美,但方向值得肯定。

查看原始信息
gesture.live
Play live electronic music with your hands over a webcam. Chords, bass, drums and effects, performed through gestures.

Shoutout to indecisiveeric.com/gesture-synth, which went viral a few weeks ago on Instagram. It allows users to use both hands to perform chords.

gesture.live is an exploration on how to take this gesture synth further. I am using the same chord language, but am compressing it to one hand, so the other hand is free to play melodies, add drum/bass patterns and control effects.

1
回复

the demo video looks great in a well lit room at a desk. has anyone actually tried this on a small stage or at a house party yet? I'm curious how the hand tracking holds up under stage lighting or just dimmer, more colored light than a webcam usually gets pointed at, since that seems like the real test of whether this leaves the bedroom-producer use case.

1
回复

@galdayan Thanks for the comment! I haven't tested it with a live audience yet. The initial use case was for the bedroom, but would love to optimize for live performance in the future!

0
回复

I am no musician, so probably I will not ever use this, other than to play with my kids, but this seems amazing!

1
回复

@igor_torrealba Thank you! I hope your kids will enjoy it :)

0
回复

The question that decides this is whether note-ons are quantised. Webcam hand tracking is 30fps on a good day, so there's 30ms of jitter before the audio thread even hears you, and you start feeling timing errors well under that. Snapping to a 16th grid makes it playable but you lose pushing and laying back, which is most of what makes a part sound human. Freeing the second hand by compressing chords into one is the right call either way.

1
回复

@asadmalik901 I am quantizing the chords to the grid since they also influence the bass and the notes available to play the melody. The melody is completely in realtime! I haven't found latency a big issue so far, but its good to to think about!

0
回复
#20
The Garden of Mind
Your subconscious mind as a living 3D garden you water daily
97
一句话介绍:The Garden of Mind 将“潜意识刻意练习”转化为一座随真实日历天数生长的 3D 花园:用户每天用两分钟写下并观想一个意图,它便化为种子生根发芽,用可视化的生长过程替代抽象的坚持,解决“注意力被无意识消耗、想培养习惯却缺乏耐心与反馈”的痛点。
Web App Productivity Growth Hacking
潜意识训练 习惯养成 正念冥想 意图可视化 3D花园 自我成长 专注力管理 无订阅付费 浏览器应用 每日仪式
用户评论摘要:有效反馈集中在三点:一是“中断后植物是否死亡”决定它能否成为低负罪感的练习工具;二是创始人坦承“最不确定用户是否会每日回归”,引发对习惯粘性的真实讨论;三是用户认可“两分钟强制放慢”的仪式感,但质疑其本质是否只是“换皮 affirmation”,并追问是否有长期改变的数据追踪。
AI 锐评

这款产品的聪明之处在于把“潜意识”这个玄学概念,翻译成了“注意力选择”这个现代人普遍焦虑的日常议题。它没有宣称能实现愿望,而是诚实地把“你每天重复什么,你就会成为什么”这句老生常谈,做成了一面镜子——花园里的每株植物都是你过去数周注意力的物理证据,这种“时间可视化”比任何打卡日历都更直指人心。

但它的弱点也恰好在这里:它本质上是一个单机版的心智整理工具,缺乏社交压力和外部约束,完全依赖内在动机。创始人Victor自己也承认,最担心的是“这会不会变成另一个待办事项”。评论中那位用户问得精准——“植物死了还是等着”决定了这个产品是慈悲的还是惩罚性的,好在设计选择了前者,这保留了产品的温度。

真正的价值不在“潜意识”的包装,而在于它提供了一个极其轻量的、可反复回到自我意图的路径。每天两分钟的仪式,本身就是一种对抗信息过载的微小抵抗。但问题也在于此:它过于温和,以至于对有重度焦虑或拖延的用户可能缺乏足够的“刺痛感”。它适合作为冥想初学者的习惯锚点,却很难成为深层心理问题的解决方案。

商业化上,一次性买断€29是相当克制的举措,但能否跑通取决于是否会形成口碑传播。它的天花板在于:到底有多少人愿意为“和自己安静待两分钟”付费?这不仅是产品问题,更是时代问题——在注意力经济里,反向贩卖专注本就是逆流而行的生意。值得关注,但别神化。

查看原始信息
The Garden of Mind
The Garden of Mind is a visualisation of your subconscious mind. Whatever you hold in your attention gets planted in you — so plant one thing on purpose. Write an intention and it becomes a seed in a living 3D garden. Water it two minutes a day: read it, breathe with it, picture it as already true. The plant grows across real calendar days, so what you see is what you kept choosing. Free to start, no account, nothing to install. Founders Pro is €29 once — nothing renews, ever.
Hi Product Hunt 👋 I'm Victor. I built this alone in Brussels, and it started with a book: Joseph Murphy's The Power of Your Subconscious Mind. The Garden of Mind is a visualisation of your subconscious. Here is the concrete version of that. Everything you hold in your attention long enough gets planted in you, whether you chose it or not: the feed you scroll before sleep, the worry you rehearse in the shower, a sentence someone said to you years ago. Your subconscious does not check whether any of it is good for you. It accepts what it is given, repeatedly, with feeling. So the app asks you to plant one thing on purpose. You write what you want to grow, an idea, a wish, the person you want to become, and it becomes a seed. Once a day you water it: you read your own sentence, breathe with it, and picture the moment it is already true, seen through your own eyes. Two minutes. What you plant in your subconscious, you plant in the garden. It is the same act. The 3D garden is that inner ground made visible, the plant grows across real calendar days, so what you are looking at is a picture of how many times you actually returned to your own intention. Nothing in there grew that you did not keep choosing. And that is where it stops being a metaphor. A thought visited once stays a wish. Visited daily, with feeling, it becomes familiar, and familiar thoughts change what you notice, what you believe is available to you, and what you do next. Over weeks, that is how something you only wanted becomes something you are living. Not because the garden grants it, but because you kept showing up for it until it became the thing you think from instead of the thing you think about. A few decisions I would defend: • Three intentions on the free plan. Not a paywall trick: attention is the scarce thing, and a garden with twenty seeds is a to-do list. • Miss a day and nothing breaks. No streak shaming. The plant recovers when you come back, because that is how a practice actually behaves. • Nothing renews, ever. Founders Pro is €29 once (first 200, then €49). There is no subscription hiding anywhere. • No account to start, nothing to install. It runs in your browser and your garden stays exportable. I would genuinely like to know: does the daily ritual feel like something you would return to, or like one more thing to maintain? That is the part I am least sure about, and I will be here all day.
2
回复

@victor_tanaka 

Answering your question honestly: the thing that deserves my attention today is the part of my work that doesn't produce anything visible. I shipped a launch this morning, and the pull is to keep refreshing numbers rather than sit with the one problem I'm actually trying to solve.

The line about your subconscious accepting whatever it's given, repeatedly, with feeling, that's the bit I'll be thinking about. Building solo, most of what I repeat to myself daily isn't chosen.

One thing I'd want to know as a user: what happens if I miss a few days? Whether the plant dies or just waits says a lot about whether the app becomes another thing to feel guilty about.

1
回复
@fasathor 🌟 I always enjoy learning about growing businesses. What's been your biggest win so far this year?
0
回复

@victor_tanaka the ritual is the honest part here regardless of what you believe about the subconscious claim - writing one sentence and sitting with it for two minutes a day is just a small, well-designed habit loop, dressed up as a garden instead of a streak counter. i'd be careful leaning on the murphy framing though, since "plant a thought and it manifests" invites the obvious pushback that this is affirmation practice with extra steps. do you track whether people who stick with it for a few weeks report anything changing, or is that explicitly not a claim you're trying to make?

0
回复

Before the world tells you what matters, what deserves your attention today?

1
回复

honestly the two minute watering thing feels kind of nice, like it actually forces you to slow down instead of just setting a reminder and ignoring it. my little sprout showed up after a couple days which was a small but real moment.

0
回复