Show HN highlights open‑source resume builder and installable web‑app

A recent “Show HN” thread introduced an open‑source resume builder that runs entirely in the browser, storing data locally and offering real‑time editing and ATS‑friendly formatting [1]. In a separate discussion, a developer showcased a curated app store for installable web applications, prompting debate over the role of PWAs versus native mobile apps [2].

Key takeaways

• The resume builder updates the UI in real time and requires no sign‑up, keeping user data in the browser [1].
• It includes a parser that evaluates how well existing resumes will pass applicant‑tracking systems [1].
• The web‑app store filters for installable PWAs, but the default view may include non‑installable sites [2].
• Commenters note usability issues such as broken deep‑link back buttons and limited trackpad scrolling on the store’s carousel UI [2].
• The discussion reflects broader tension between native app ecosystems and the growing capabilities of PWAs [2].

Open‑source resume builder emphasizes privacy and ATS compliance

The creator of the resume builder explained that the tool was inspired by mentoring students who repeatedly made the same résumé mistakes [1]. Its core features include live UI updates as users type, compatibility with major applicant‑tracking systems such as Greenhouse and Lever, and a privacy‑first design that avoids any server‑side storage. Users can also import an existing PDF résumé, and a separate parser lets them test the ATS readability of their current documents. The project’s code and live demo are hosted on GitHub and a dedicated website, with additional exposure on Product Hunt [1].

Installable web‑app store raises questions about web versus native experiences

Another Show HN post presented “Store.App,” a marketplace that lists only installable web applications, i.e., PWAs that can run offline and integrate with OS features [2]. The thread quickly turned to criticism of the store’s user experience: deep‑link URLs break the back button, the privacy and terms links open in new tabs, and the carousel navigation lacks trackpad scrolling, mirroring issues seen on commercial sites like Apple’s store [2]. Participants debated whether PWAs can truly replace native apps, citing examples such as messaging, email, and music streaming that benefit from window‑level controls, while others argued that many popular services (Twitter, Reddit, Instagram) still rely on native experiences for performance and user expectations [2].

Why it matters

Both posts illustrate the Hacker News community’s focus on open‑source tools that prioritize user control—whether through local data storage in a résumé builder or through the promise of installable, offline‑capable web apps. The resume builder’s privacy‑centric approach addresses growing concerns about data handling in job‑search platforms, while the app store discussion highlights ongoing friction between web standards and native app ecosystems. As PWAs gain broader OS support, the feedback from these Show HN threads may influence future design choices for developers seeking to balance accessibility, functionality, and user trust.