6 pointsby familytreeeasy10 hours ago3 comments
  • javadhu6 hours ago
    I always wanted to make such a tool for myself but never sat to actually build it. User experience was a breeze.

    I see that there is no import button. Adding Import will help many of us to keep editing the same tree instead of building it from scratch everytime. You can add a JSON export of the tree and then users can import this JSON to make edits. I can also share this JSON with other family members.

    • familytreeeasy5 hours ago
      Thanks for the feedback! I’m glad the UX felt seamless—that was definitely the hardest part of the project.

      Implementing JSON import/export is at the top of my roadmap for persistence: letting users "save" their progress locally without needing a cloud backend.

      I’m working on the data schema for this right now. Stay tuned!

  • HiiDee10 hours ago
    Love the simplicity. Most family tree tools are so bloated that it feels like a chore just to add a cousin. One quick question: Since it runs entirely in the browser, are the family names and data stored locally, or do you have a backend keeping track of the trees? Privacy is always a big concern for people when it's about family history.
    • familytreeeasy10 hours ago
      Thanks! I’m glad the simplicity resonates with you—fighting against genealogy bloatware was exactly what I wanted to avoid.

      As for privacy, everything stays in your browser. There’s no backend database tracking your family history.

      The data is stored locally (via LocalStorage), so if you refresh the page or come back later, it’ll still be there—but I never see it.

  • testbyhuman_tor40 minutes ago
    [dead]