Project ideas from Hacker News discussions.

Launch HN: Nori Robotics (YC S26) – A low-cost humanoid robot for development

📝 Discussion Summary (Click to expand)

1. Skepticism about the robot’s real‑world capabilities
Many commenters doubt that the demo videos show genuine, usable performance, arguing the motions are jerky, staged, or only work in very constrained scenarios.

  • “Can you be up front about its real capabilities. Are these videos of it eg tidying up real or just staged / cherry picked?” – jonplackett
  • “That video of it folding clothes would seem to hint at that. It's only able to awkwardly throw it into a pile… It's clearly a very cool project, but it suggests the claimed capabilities are more show than substance.” – jdiff
  • “I can only imagine this thing literally fucking everything up. Like, knocking shit off my table, setting my kitchen on fire…” – dvt
  • “You do know that false advertising is a crime, right? … you had to say it folds clothes, lol. You’re now going to be a scam in the mind of me and surely many others, forever.” – Mawr

2. Price, business model, and target market
The low $1,688 hardware price sparks debate about sustainability, VC‑driven hype, and who the product is really for (hackers/hobbyists vs. mainstream consumers).

  • “Love the design and freedom of this! Curious what the business model of this is to make the company sustainable.” – TristanX
  • “If we're dependent on SF tech‑bros to build useful robots we're already screwed. The Chinese robots can literally run circles around anything I've seen come out of the US.” – doodlebugging
  • “We make money by selling the hardware for $1,688, with optional paid software on top.” – IAmBroom (quoted in the thread)
  • “I'm confused, is this a research device, hobby/tinker item, or consumer product? … making a sustainable business on a hardware race to the bottom sounds challenging.” – mNovak
  • “Why would you price your hardware so low? if this is as good as a customer would imagine, pricing should start around $20,000.” – calvinmorrison

3. Practical concerns: usability, privacy, repairability, and software openness
Commenters raise worries about sensor quality, compute power, telemetry, repairability, and whether the robot can be truly controlled without reliance on cloud services or smartphones.

  • “Does this require internet connectivity? If Nori goes out of business, can we keep using these?” – anonym29
  • “RPi5 seems a bit underpowered for all the sensors & control… A Jetson Orin Nano would seem to be a better choice…” – slug
  • “My preference would be ifixit level guides where you can easily replace parts yourself. Then it would be perfect if the same servo is used everywhere…” – whazor
  • “Is every function available through the app possible to perform or recreate with the open SDK? … Is the software that ships on it totally open source?” – anonym29
  • “Privacy would be a huge concern, I can't have this in my garage lab with all my stuff being sent back to your servers for computer vision tasks etc.” – IAmBroom (quoted earlier)

These three threads—capability skepticism, price/business‑model debate, and practical/privacy/repairability concerns—dominate the conversation.


🚀 Project Ideas

ServoFlow: Open-Source Trajectory & Compliance Library for Hobby Servos

Summary

  • Provides smooth motion planning, inverse kinematics, and compliance layers that turn cheap RC servos into precise actuators for home robots.
  • Core value proposition: Enables reliable, repeatable task execution (e.g., folding clothes, picking up objects) without expensive hardware upgrades.

Details

Key Value
Target Audience Hobbyist robot builders, educators, and small‑scale robot startups using low‑cost servo‑based platforms
Core Feature Real‑time trajectory generator with jerk limits, IK solver, and optional torque‑feedback compliance using current sensing
Tech Stack C++ (core), Python bindings, ROS 2 nodes, optional CUDA for acceleration; builds on Eigen, Pinocchio
Difficulty Medium
Monetization Hobby

Notes

  • HN commenters complained about jerky motions and lack of precision (e.g., “The arm motion will be like a 90 year old with mild Parkinsons”) – ServoFlow directly solves that by smoothing trajectories and adding compliance.
  • Enables discussion: users can share tuned parameters for specific servo models, fostering a community‑driven improvement loop akin to the K‑scale labs desire for open, collaborative robotics.

RobotTaskVerify: Crowdsourced Benchmark Suite for Home Robot Capabilities

Summary

  • A platform where users upload videos of their robot attempting standardized household tasks (folding a shirt, loading a dishwasher, stirring soup) and receive objective success metrics (completion rate, time, error bounds).
  • Core value proposition: Turns vague marketing demos into transparent, reproducible performance data, combating cherry‑picked claims.

Details

Key Value
Target Audience Robot developers, reviewers, early adopters, and skeptical consumers who want proof of real‑world capability
Core Feature Standardized task protocols, automated video analysis (pose estimation, object detection), leaderboard, and reproducibility scoring
Tech Stack Web frontend (React/TypeScript), backend (Node.js/FastAPI), video processing (OpenCV, MediaPipe), storage (PostgreSQL + object store), optional WebAssembly for client‑side analysis
Difficulty Medium-High
Monetization Revenue-ready: Subscription (free tier for public benchmarks, paid plans for private tasks, detailed analytics, and certification badges)

Notes

  • Commenters like PxldLtd and jonplackett asked “Are these videos … just staged / cherry picked?” – RobotTaskVerify gives an open way to validate claims, directly addressing that frustration.
  • Sparks discussion: a public leaderboard encourages honest competition and provides practical utility for buyers deciding whether a robot can truly handle chores like folding clothes or closing a fridge door.

OpenRobot SDK: Privacy‑First, Offline‑Capable Robot Control Framework

Summary

  • An open‑source SDK that lets developers build robot applications without requiring internet, Google Play Services, or proprietary cloud telemetry; includes on‑device inference hooks and local data storage.
  • Core value proposition: Gives users full control over privacy and ensures the robot remains usable even if the parent company disappears, answering concerns about vendor lock‑in and data harvesting.

Details

Key Value
Target Audience Privacy‑conscious makers, developers targeting de‑googled devices, and institutions needing air‑gapped operation
Core Feature Modular architecture (hardware abstraction, skill library, optional on‑device AI plug‑ins) with zero‑mandatory telemetry; works on Linux, Android AOSP, and bare‑metal MCUs
Tech Stack Rust (core safety-critical components), C/C++ HAL, protobuf for messaging, optional TensorFlow Lite for on‑device ML; build system via Cargo/Cmake
Difficulty High
Monetization Revenue-ready: Support contracts & premium skill‑module marketplace

Notes

  • HN users (anonym29, Tepix) stressed the need for offline use, no GMS reliance, and clear privacy policies – OpenRobot SDK delivers exactly that, making it attractive to the “hacker” crowd that values user freedoms.
  • Potential for discussion: a truly open SDK invites contributions for new skills (e.g., suction‑card handling, board‑game play) and can become the foundation for community‑driven robot ecosystems, reminiscent of the desire for riffable, moddable platforms expressed by mrnotcrazy.

Read Later