easyweb

Why

Sign-up and posting screens with many fields are a wall for seniors. This Electron app shows the real site as-is and fills it in from one large-type form on the left. It is a personal aid used with my own accounts, not something to distribute.

Rules kept in the design

• A human presses the final submit. Irreversible buttons like “complete sign-up” or “publish” are a handoff step; the app only marks them in orange. Undoing a wrong post is much harder.
• CAPTCHAs, identity verification and terms consent are never automated. All of it goes back to the person.
• Passwords are never stored in plain text. They are encrypted with safeStorage (DPAPI on Windows), and if encryption is unavailable, saving is refused. Progress logs are masked too.
• Recipes live outside the code. When a site changes, only the JSON changes.
• On failure, capture the screen right then. “Stopped at step X” plus a view-screen button.

Structure

A 460px control panel (large-type form) on the left and the real site (WebContentsView) on the right. main/automation.js is the recipe engine; recipes are read from recipes/*.json or the user folder.

Status

One working recipe: sign-up on a community site built on a Korean bulletin-board engine. Across its two steps (terms → form), terms, CAPTCHA and the final submit are handed to the person.