Back to AppliAid

Changelog

One line per change you can see, newest first. AppliAid is a beta with one builder, and this is how you can tell it is being worked on.

  • Fourteen days after a fit run, the posting's page asks whether you applied and whether you heard back, with fixed answers. Once per run, skippable, and Settings can turn it off for every run.
  • This page, linked from the footer.
  • A table of contents beside the privacy policy, the terms and the scoring page on a desktop screen, and anchors on those pages land below the header instead of under it.
  • Sign-in links now work in whichever browser opens them, for their whole lifetime. Before, a link opened more than five minutes after it was requested failed, and so did one opened on a different device from the one that asked.
  • Both sign-in emails carry a numeric code as well as the link, and the code can be entered on every screen that sends one, including the screen shown when a link has failed.
  • Settings has a switch that stops AppliAid counting how you use it and deletes the counts already stored.
  • The privacy policy says how long usage counts and server logs are kept, with the figures.
  • A cover letter and an interview brief now say what your part in a publication was, when you have told the graph.
  • The fit judge reads how proficient you said you are in a skill, for how many years, and when you last used it.

  • Delete your account from Settings. It is a real deletion, at once.
  • Skill claims are listed on the graph page and can be edited or deleted there.
  • Each verdict on a fit report links to the record it rests on.
  • The privacy policy names all five processors, including Stripe, and says the usage count carries the domain of your sign-in address.
  • The position editor on the graph page opens again.

  • A page on how scoring works: what the engine reads out of a posting, how each requirement is judged, how the judgements become a score, what the bands mean, and what it will not do. Linked from the footer and from the pricing FAQ.
  • The privacy policy names Deepgram as the processor for spoken answers and says how long a recording lives.

  • The landing page holds together on a 360px phone, the app navigation no longer hides half of itself, and loading states stop dragging the page sideways.

  • A new look across the site and the app: one type scale, one set of controls, and the same chrome on both sides of sign-in.
  • The pricing page is rebuilt in the order a visitor decides, and stops ending on the refund clause.
  • The emailed sign-in code accepts codes of six to ten digits. It only accepted six, and the project sends eight.
  • Signing in with the code keeps the posting you pasted before signing in.
  • A resume no longer calls a publication peer-reviewed unless the record says so.

  • Paste a posting on the landing page without a CV. It is held, unread, for 24 hours or until you sign in.

  • Attach a CV on the landing page before you have an account. It is held, unread, for 24 hours or until you sign in, and the notice under the box says so.
  • The posting comes first: paste it, then import your CV, and the first fit runs only when you ask.
  • The sign-in flow has real states: sent, expired, already used, wrong browser, each with one sentence and one action.
  • The privacy policy says how long everything lives and names the second cookie.
  • The FAQ, the hero paragraph, and a follow-up conversation that is bounded and can be dismissed.