
Schedulin — Social Media Scheduler for TikTok, Instagram, LinkedIn & More
在 TikTok、Instagram、LinkedIn 等平台安排社交媒体,$5/月起。
@troyaunderwood · X
完整作品展
技术栈
16 projects

在 TikTok、Instagram、LinkedIn 等平台安排社交媒体,$5/月起。
@troyaunderwood · X

按收入风险评分收件箱、自动起草回复的 AI 邮件管理工具。
@dailytaskproai · X

在一个仪表板中安排和发布内容到多个社交平台。
@DonatasJab · X
Not long ago finished my first SaaS product - social media scheduling tool. Tomorrow will launch on Product Hunt. I hope it goes well.

将Basecamp项目日历合并为统一的iCal日历源,支持谷歌日历、Outlook和Apple日历。
bhagyeshsp · HN
First things first: On the landing page, click on the "demo" link below the Hero section to try it without jumping any hoops ** I'm a long-time Basecamp user and satisfied with its overall functionality. Of course, there are many things that can be improved but that is not the point of this post. *Background* Basecamp lets users create "Projects". These projects are isolated workspaces that contain: members, todos, chat, files, message board, and calendar, etc. My issue was with the scattered calendars. Because I (and every other Basecamp user) creates a dedicated project for different scope of work, even if it is for the same client. For example, at any given time, I may have 4 projects for client-X and 3 projects for client-Y. *My pain point* I have experienced that most clients (especially the decision-makers) do not use Basecamp as often as we--the agency folks use it. They just use it when some reviews or comments are required or some file access. The clients organize their

从实时目录自动生成符合您日程的播客会话
@Akisin1 · X
Listen Like You Live

在一个仪表板上安排发布到11+平台的社交媒体内容。
@AmeerHaio · X
your content everywhere!

私人日记应用,为家人保存记忆并传承数字遗产。
@Rustam280592 · X
Day Etch is your second memory. Day Etch - your experience as intellectual capital for future generations. We are creating not just a diary, but a repository of life.

English Daily是免费AI英语学习平台,包含听、说、读、写练习。
English Daily — AI 每日英语学习平台

为日历事件添加状态、标签和评级,获取周度和月度时间报告。
mjkl7896 · HN
Velprium - Time Workspace


Servicebay — 为服务型企业管理工作、客户、日程、发票和支付的一体化平台。
@seb_klopfer · X

管理学术会议:提交和审阅论文、处理日程安排和注册。
@harryjwang · X
I've used many of the major conference systems. Plenty still have docs as an unsearchable static site — or worse, as PDFs that stopped tracking the product three versions ago. Somehow, still true in 2026. We took an AI-first path with instead. Our docs are generated from the codebase itself. A custom Claude Code skill writes each page and retakes the screenshots whenever a feature changes — so the docs don't drift from the product. Every page still gets reviewed by a human before it ships. Now you can talk to them, too. We just shipped "Ask AI" over our docs: This feature also turned out to be a nice teaching case for agentic RAG vs. classic RAG: • Classic RAG: chunk → embed → vector DB → retrieve once, by fixed rules • Agentic RAG: hand the model a search tool and let it drive — write a query, read the results, rewrite, retry At more than 100 pages, still no vector database needed. And every answer cites the exact page it came from. #Age