Curiosity Atlas v1.0.0 — App Review Summary

Loaded Source URL

LOADED_SRC: https://producingtechnology.com/65-apps/wuirene_184763_15200472_json.html

App Overview

Curiosity Atlas v1.0.0 is a personal knowledge-mapping app that visualizes a network of ideas as a connected graph. The aesthetic is moody and editorial: a deep black canvas, a thin neon-green hairline at the top, and gold serif accents on the title and toggle buttons. Each item in the graph belongs to one of five typed categories — concept, book, thinker, question, and field — each with its own color and icon. A header strip surfaces three running totals: 142 Explored, 89 Connections, and 17 Open Qs. A daily prompt sits at the bottom of the page: Pick one open question and write three sentences you couldn't have written last week.

Behavior Summary

The interface is split into a left rail (search + node list) and a main canvas that toggles between two views:

Things That Didn't Work As Expected

Suggested Improvement Prompt

Improve the Curiosity Atlas single-file web app so the graph feels alive and the knowledge tool actually supports the daily-practice ritual it advertises. Specifically:

  1. Make the graph interactive: Add a force-directed layout (e.g., d3-force or cytoscape) with drag, zoom, and pan. Cluster nodes by type or by tag, and animate transitions when filters or selections change.
  2. Improve edge legibility: Replace the low-contrast dashed lines with solid strokes that adopt the source node's color at lower opacity, and label the edge type ("references," "inspired by," "contradicts") on hover, not just on selection.
  3. Wire up the type filters: Clicking a type pill should filter both the graph and the list view to matching nodes, with a clear active state, a count badge, and a multi-select mode (shift-click) so users can combine filters.
  4. Make stats reflect loaded data: Compute Explored / Connections / Open Qs from the current JSON. If the larger numbers are intentional lifetime totals, label them ("Lifetime") and add a smaller "in view" pair beside them.
  5. Build a real Add flow: Open a modal that takes title, type, tags, mastery, description, and an optional list of connections (multi-select from existing nodes), and animate the new node into the graph with edges drawn.
  6. Live search with highlighting: Filter both the rail list and the graph as the user types; dim non-matching nodes in the canvas, show a "no results" empty state, and support fuzzy matching across title, tags, and description.
  7. Expand the node detail panel: Add a free-form notes field, a journal log with timestamped entries, an "update mastery" control, and an inline "Add connection" picker. Show the date last revisited and a small spark line of journaling activity.
  8. Mastery legend & progression: Add a small legend (curious → exploring → familiar → fluent) with hover tooltips, and let users update mastery from any card or the detail panel — logging the change to the node's history.
  9. Make the daily prompt actionable: Tapping the footer prompt should pick a random open question, open its detail panel, scroll the journal field into view, and timestamp the entry on save. Keep a rotating archive of past prompts.
  10. Import / export JSON: Add explicit "Load JSON" / "Download JSON" controls so users can bring their own atlas, share snapshots, and back up their data — true to the app's JSON-driven framing.
  11. Polish the icon set: Use slightly larger, higher-contrast SVG icons inside each node circle, with consistent stroke weight, so concept/book/thinker/question/field are instantly distinguishable on the graph.
  12. Optional light theme: Offer a light variant for daytime reading; the gold serif title should adapt rather than disappear against a pale background.