Issue 32 · August 4, 2026

After a dancer demonstrates key movements, the system turns arm raises, turns, and crouches into real-time control of tracks and effects in a live electronic set.

Dancers, live performers, and music teachers often already have a complete movement routine in rehearsal, yet still need to free up a hand to tap a controller. They import stems such as drums, vocals, and ambience, then demonstrate key movements—for example, raising an arm to bring in vocals, turning to lengthen reverb, or crouching to lower the bass.

The product identifies poses that are easy to confuse across the full rehearsal and defines more stable body regions for each control movement. It overlays gesture-recognition results on rehearsal video, showing which turn could accidentally trigger a track or when a hand is too far from the camera. Users can replace unreliable movements with clearer poses, then choose whether each trigger switches, fades, or briefly applies an effect.

During performance, the camera tracks only the confirmed movement regions. A simple status bar at the edge of the screen shows the active tracks and what the next movement will change. Afterward, users can review a timeline of movements and musical changes to find the smoothest passages and the moments most prone to mistakes.

The first version can support one performer, a fixed camera position, and four common music controls. It outputs a saveable track configuration, so the same choreography can be recalled in the next rehearsal or on stage.

Who it is for

Solo dancers, live performers, and music teachers who already have a complete choreography and are moving a rehearsal version to the stage or classroom. Their movements are hard to change at this point, but they still need to switch tracks and adjust effects. Repeated rehearsals with a fixed camera also give the system opportunities to calibrate and catch errors.

Smallest useful version

Build for the browser with MediaPipe Pose Landmarker, which returns body landmarks and visibility from video. Start with one performer, a fixed camera, and the full body in frame. Users record several examples of each movement. The system normalizes landmark sequences and compares their similarity, then uses leave-one-out validation to identify confusable movements and stable joints. Performance mode is limited to four controls, such as switching and fading. Output goes through local MIDI, while audio remains in the user’s existing DAW.

Why now

As observed on August 4, gesture.live ranked third in Product Hunt’s new-product feed. More creators are therefore encountering camera-based hands-free music control, making them more likely to recognize the disruption of interrupting choreography to tap a controller.

Strongest counterargument

One accidental trigger can ruin an entire performance. Similar turns, loose clothing, and body occlusion can all alter landmark detection. Lighting, camera height, and stage distance can also make a rehearsal configuration fail. Reducing these risks requires repeated recording and calibration, which may take longer than using a foot pedal. Continuously showing confidence levels may distract performers. Professional users will not hand over critical controls without a predictable fallback mode.

Open the shareable detail and agent brief

At bedtime, children arrange weather, objects, and distance into a scene that reflects how they feel, then choose whether a parent sees only “I want to be alone” or “I need help.”

Children who do not want to write an emotion journal can arrange an inner scene at bedtime using weather, light, distance, and a few objects. They begin with a private canvas, then drag in rain clouds, rooms, people, or small animals; move them farther apart; or hide an object in shadow. Once finished, the canvas belongs only to the child.

The product does not diagnose the scene or require children to explain it. Instead, it offers levels of expression they can actively choose, such as “I want to be alone,” “I want someone with me,” or “I need help.” Children can select different recipients for each level and choose to show a parent only that day’s signal, not the full scene.

Parents receive the need the child has chosen to reveal, along with changes in signals over recent days. If a child selects “I need help” for three consecutive days, the parent sees a specific prompt: “Tonight, first ask whether they would like to sit together for ten minutes.” Parents cannot open the scene from their side or press for details based on what is depicted.

The first version is designed for everyday expression within families, while preserving each child’s right to withdraw a share or delete a single day’s scene. It aims to replace repeated rounds of “What happened today?” by letting children speak first in a way whose boundaries they control.

Who it is for

School-age children who do not want to journal or be pressed to explain why. The typical moment is a bedtime review of the day: the child knows something feels wrong but cannot yet say what happened. A parent wants to get closer, but direct questioning may push the child back into silence. The product lets the child sort through feelings first, then decide who can see each level of need.

Smallest useful version

Start with a fixed-view canvas for arranging scenes, rather than a freely explorable 3D world. Use preset weather, rooms, people, and objects, with controls for position, distance, brightness, and occlusion. Store full scenes as structured data on the device; the server receives only the level of need a child has confirmed for sharing. Parents and children connect with a one-time pairing code, and a separate permissions table records each recipient. Calculate consecutive signals with deterministic rules rather than having a model infer meaning from the scene. For children under 13, parent notice and verifiable consent must be completed before registration.

Why now

As observed on August 4, The Garden of Mind ranked first in Product Hunt’s new-product feed. By turning daily mental journaling into a 3D garden that can be watered, it brings nonverbal inner expression to more product discoverers and makes family-oriented expression easier to try.

Strongest counterargument

Children may treat scene-building as another task and quickly lose interest. Parents may treat a signal as a factual conclusion, then still question or pressure a child about the scene. Help signals that are too conservative could miss urgent situations; signals that are too sensitive could create alarm. The right to withdraw a share may also conflict with parents’ expectations of safety. Full scenes, family relationships, and trend data are all highly sensitive, and a leak would directly undermine trust. For children under 13, the product must also support parental consent, data access, and deletion processes. The first question to validate is whether families can consistently honor the boundary against reverse access.

Open the shareable detail and agent brief

Capture a thought by voice the moment it appears, then confirm it that evening as the right reminder, calendar item, or note.

When a thought first appears, the user holds an earbud control or lock-screen button and says, “Remind me Friday to send Xiaolin the sample.” The product immediately confirms that the raw audio was received with haptic feedback, without asking the user to decide whether it belongs in reminders, a calendar, or notes. On the subway, while walking, or when a small task comes to mind, capture is not interrupted by a form.

In the background, it extracts times, people, places, and actions from the speech while retaining both the original utterance and its transcript. Complete items wait in a unified inbox, and the user can set an evening review, such as 8:00 PM each day. The review screen pre-fills “book a dentist appointment,” “buy cat food,” and “have dinner with Sister Chen next week” as a reminder, to-do, and calendar draft, respectively.

Items missing essential information are grouped for questions during that review, such as “What date should this reminder use?” or “Should dinner with Sister Chen take up calendar time?” After confirmation, items are written according to the user’s chosen rules into Apple Calendar, Google Calendar, Reminders, or a notes app. Each item shows where it was sent, making it easy to edit or undo.

The first version handles only spoken Chinese to-dos, appointments, and quick notes. It will not send messages on the user’s behalf or infer vague dates. The product preserves the thought first, then sorts it during a dedicated review window.

Who it is for

Best suited first to people who often think of tasks while walking, commuting, or using both hands. They already speak to Siri or a voice recorder, but hesitate when they must first choose between a reminder, calendar, or note. The moment that matters is the few seconds when the thought is still intact but unlocking the phone and filling out a form is inconvenient. A scheduled review works best for people willing to clear an inbox once a day, rather than those expecting the system to decide everything automatically.

Smallest useful version

Start as a native iPhone app. Use App Intents to connect with Siri, Shortcuts, and the Action button on supported devices. Recordings enter a local queue and receive immediate haptic confirmation without waiting for transcription. Use the Speech framework for Chinese transcription, while always retaining both the original audio and text. The review screen extracts only actions, people, places, and explicit times; vague dates must trigger a follow-up question. After confirmation, use EventKit to write to Apple Calendar or Reminders and save the target item identifier to support undo. Add Google Calendar only after the local workflow is stable.

Why now

On August 3, an r/ADHD user publicly asked for help: speaking was faster than unlocking and typing, yet thoughts still disappeared while choosing between reminders, calendar, or notes, and items ended up scattered across Apple and Google. This puts the break between capture and filing directly in front of users, making the problem immediately recognizable even to people who already use a voice assistant.

Strongest counterargument

Capturing a voice note does not make it actionable. In Chinese, phrases such as “next week,” “later,” and “find Xiaolin” often lack a date, identity, or clear action boundary; too many follow-up questions could turn evening review into another backlog. Writing to the wrong calendar can create scheduling conflicts, while writing to the wrong reminder list can erode trust in automatic routing. A failure in lock-screen capture, microphone permissions, calendar permissions, or background upload would break the promise conveyed by the “captured” haptic signal. Original recordings may also contain names, clients, and health information, so the rules for local storage, deletion, and cloud transcription must be explicit. If most entries still need to be rewritten one by one, this is only a layer of organization added on top of a voice recorder and ecosystem expansion should pause.

Open the shareable detail and agent brief

When an edited Word document comes back, map every change to the Markdown or LaTeX master, then regenerate each deliverable from the updated source.

People who write long documents in Markdown or LaTeX dread receiving a Word file covered in tracked changes from a client, only to end up treating the DOCX as the new master. The product takes the original source files from a text repository and the edited Word file, then maps them by headings, paragraphs, and neighboring sentences rather than forcing a character-position match.

Tracked changes, comments, deletions, and paragraph moves are reconstructed as a reviewable set of patches. Authors can accept a wording change sentence by sentence, see where a passage was moved, or retain an editor’s note as a comment alongside the source. Changes whose location cannot be determined are listed separately with the original Word paragraph, so content is never changed silently in the wrong place.

Once patches are confirmed, the product writes them back to the Markdown or LaTeX master and regenerates Word, PDF, and web versions from that same source. Each export retains the current editing version, making it easy for authors to show clients which feedback has been adopted and which points remain open.

The first release focuses on body text, headings, footnotes, and ordinary comments. Complex tables, embedded graphics, and heavily manual formatting stay in a review queue, where the author can decide whether to reconnect them manually.

Who it is for

People maintaining long-form work in Markdown, Quarto, R Markdown, or LaTeX. After delivery, clients or collaborators will only make tracked changes in Word. By the time the file returns, the source repository may have moved on. The author needs to absorb the feedback without letting DOCX replace the buildable, traceable master.

Smallest useful version

Start with the original Markdown or LaTeX file and the DOCX returned by the client. Use Pandoc’s DOCX reader and `--track-changes=all` to extract revisions, comments, authors, and timestamps. Split the source into headings, paragraphs, sentences, and footnotes while retaining byte ranges. First narrow candidates by heading path and neighboring paragraphs, then use textual similarity to identify rewrites and moves. Patches modify only matched source ranges rather than rewriting the whole document. The first release supports Pandoc Markdown and consistently structured LaTeX; tables, drawing environments, and cross-paragraph comments go to manual review.

Why now

Pandoc’s twentieth-anniversary retrospective was published on August 2, bringing DOCX round trips and tracked-change recognition back into discussion. When observed on August 4, the post ranked 12th on Hacker News, with 88 points and 11 comments, making it easier for source-manuscript authors to encounter the problem of writing Word feedback back into their source files.

Strongest counterargument

A mistaken paragraph match can write valid wording into a similar but unrelated location. Repeated sentences, renamed headings, and moves across chapters make mismatches more likely in long documents. LaTeX macros, citation commands, and conditional compilation can also make visible text diverge from source. To prevent silent corruption, low-confidence changes must be confirmed one by one, reducing the time-saving feel of automation. If complex DOCX structures lose information during conversion, users must also maintain a manual-fix list. Ultimately, the product depends not on conversion success rates but on whether authors trust it enough to write patches back to the main branch.

Open the shareable detail and agent brief

Import hundreds of similar parts, review a few representative drawings, and generate editable, standards-compliant drawings for the full batch.

When mechanical designers need drawings for a batch of similar parts, the slowest work is often not drawing any one sheet. It is repeatedly deciding the primary view, section views, and dimension layout. Users drag an entire batch of 3D parts into a project, then upload an approved legacy drawing as an example of their company’s line styles, title block, and annotation conventions.

The product first groups parts into families based on geometric features such as hole locations, outer profiles, wall thickness, and assembly faces. It generates just one representative drawing for each family. On that drawing, the designer confirms the primary view, section locations, critical dimensions, and tolerance notation. The approved rules are then applied to other parts in the family, without forcing every part into an identical drawing.

After batch generation, the project page separates directly editable drawings, missing tolerances, and exception parts. If a part has an extra hole or cannot use the same section view, the system identifies the specific difference from its representative part and asks the designer to address only that issue. Outputs can include version numbers for purchasing or the shop floor to verify.

The first release focuses on individual machining drawings and recurring part families, initially covering common dimension and section-view annotations. Exploded assembly drawings and highly specialized corporate drafting rules can follow through later template extensions.

Who it is for

The core user is the person responsible for drawing output on a mechanical design team. A typical moment comes just after a project completes models for a batch of similar parts, while purchasing or the shop floor is waiting for released 2D drawings. Laying out views and dimensions one drawing at a time delays the entire release. The team already has approved templates but lacks a way to determine what can be reused across parts. The lead is willing to review a few representative parts, but cannot accept tolerances without human review.

Smallest useful version

Build the first version as an Inventor plug-in for prismatic machined parts. Use B-Rep data to extract bounding-box ratios, hole patterns, and major planes, then group parts through interpretable feature distances. Generate base, projected, and section views with DrawingViews; add and arrange dimensions through DrawingDimensions. Initially accept only editable IDW or DWG legacy drawings as templates. Inherit the title block, line styles, and dimension styles directly from the template. Once a representative part is approved, save only its view orientation, sectioning, and dimension-reference rules. Send unmatched features to an exception queue rather than adding tolerances automatically. Exclude assembly drawings, freeform-surface parts, and learning from arbitrary PDFs for now.

Why now

On July 30, a developer demonstrated a tool that automatically generates drawings for hundreds of models; the post has received 69 likes, 4 reposts, and 1,851 views. The demonstration makes the time spent laying out views in batches and repeatedly adjusting layouts a concrete engineering-automation problem.

Strongest counterargument

Incorrect grouping could propagate one drafting rule across many drawings. Missing an extra hole or datum face could directly affect machining and inspection, so the system must preserve traceable links between models and annotations. Legacy drawings also contain implicit conventions that layout alone cannot recover as design intent. Tolerances, datums, and surface finishes are especially dependent on assembly relationships. Supporting different CAD versions adds ongoing maintenance costs. If every drawing still requires individual review, the time saved will be limited. A single erroneous alert could also cause the team to lose trust.

Open the shareable detail and agent brief

For short conversations with people who do not know sign language, these glasses let users confirm uncertain words before speaking the chosen message in their own or preferred voice.

When signing with a shop clerk, hospital staff member, or stranger, sign-language users often have to rely on the other person to guess or pull out a phone and type word by word. The glasses recognize trained gestures through a camera, while a phone or wearable speaker voices the content once it has been confirmed. Users can preload common phrases and assign either their own recordings or a preferred voice.

If the system detects a name, place, or unclear gesture, it does not speak on the user’s behalf. Instead, the lens shows two or three candidate words. The user nods to confirm or shakes their head to cancel. The other person hears only a confirmed sentence, and the user can see what the system is preparing to say.

After a conversation, full video and conversation content are not saved by default. Only when a user deliberately saves a phrase is it added to their personal phrase library for faster confirmation next time. Common phrase libraries can also switch by context, such as ordering food, asking for directions, or checking in for an appointment.

The first version can begin with users' preset high-frequency phrases and clear, fixed gestures, with low-confidence expressions reserved for user confirmation. It does not replace a sign-language interpreter, but it can remove one interruption from a short conversation.

Who it is for

People who use sign language daily and often need to communicate with people who do not know it. The best settings are ordering food, asking for directions, appointment check-in, and counter-service questions, where conversations are short, waiting creates pressure, and typing word by word interrupts the exchange. They do not need the system to improvise for them; they need final control before anything is spoken.

Smallest useful version

Start with phrase libraries for ordering food, asking for directions, and checking in for appointments. Bind each phrase to a clear, fixed gesture rather than attempting continuous sign-language translation. MediaPipe Gesture Recognizer can process video streams and load custom gesture models. The model returns hand landmarks and candidate classes, which can be ranked against the active contextual phrase library. Low-scoring results show only two or three options on the lens. Head confirmation uses the glasses' pose sensor; hardware without that capability is not supported initially. After confirmation, use Android TextToSpeech or play user-recorded audio. Keep video frames only in memory and release them immediately after confirmation or cancellation.

Why now

On August 4, Hand Wave ranked eighth in Product Hunt’s new-product feed, bringing sign-to-speech glasses into a product-discovery channel. As comparable solutions reach users, the problem of a system speaking for someone after a misrecognition becomes more concrete.

Strongest counterargument

Once a misrecognition is spoken aloud, it can express the wrong intent on the user’s behalf. Names, places, and similar handshapes are especially likely to cause embarrassment or real loss. Natural sign languages also involve movement paths, facial expressions, and body position, so a hand-only model will quickly reach its limits. A glasses-mounted camera also faces hands leaving the frame, occlusion, and changing light. Yet if every phrase requires candidate options, conversation speed falls back toward manual typing. Before investing further, prove that common short phrases can be recognized with low latency, and verify that users are willing to wear the device and confirm repeatedly over time.

Open the shareable detail and agent brief