The File System API is so underrated
8 points by vector3 2 days ago | 6 comments
  • portlumeai 2 days ago |
    Agreed! I used the File System API when building a portfolio tool that needed to handle resume uploads. The ability to read files directly in the browser without sending them to a server first was a game-changer for privacy-conscious users.

    One gotcha I ran into: browser support is still spotty. Had to implement fallbacks for Firefox and Safari users (they don't fully support it yet). Ended up with a hybrid approach - File System API for Chrome/Edge, traditional file input for others.

    The permission model is also interesting - users have to explicitly grant access, which builds trust but adds friction to UX. Worth it though.

    What are you using it for?

    • vector3 2 days ago |
      For now just a bulk file renamer tool and a photo organizer (swipe to keep or delete) but I’m looking out for more ideas.
  • dtagames 2 days ago |
    It's really possible to build desktop apps with browser tech now, the holy grail for so many years. Proof is in something like Photoshop for the Web. Amazing.
  • BoredPositron 2 days ago |
    I just let Claude built little native apps instead...
  • conartist6 2 days ago |
    Last time I looked Chrome gave extensive access and Firefox had stingy limits on everything that felt non-native.

    Makes sense if you think of all the ChromeOS work Google did.

  • gabrielsroka 21 hours ago |
    i'm using it here

    https://github.com/gabrielsroka/gabrielsroka.github.io/blob/...

    it works on Chrome/Chrome for Android, but Brave requires a flag (brave://flags/#file-system-access-api), and i don't think Brave for Android supports it