Back to journal

Show success only when the action is confirmed

From October 17 to 21, I worked through several employer flows on locdemunca.ro that needed a clearer answer to the same question: did the requested action actually succeed? A form closing, a success notice appearing or a status refreshing can all imply completion. Those signals become misleading when the application has not received a response that confirms what the person asked it to do.

The sequence began with collection loading on October 17. Jobs and templates gained explicit failure feedback and retry instead of treating an unsuccessful read as an empty collection. Applicant navigation also retained its view and sort choices. This established the read-side distinction before the later save corrections: an empty list and an unavailable answer should not mean the same thing.

The onboarding and interview paths were corrected to require explicit confirmation before showing completion or updating the visible result. Failed requests kept their context, with localized feedback and a way to try again. Interview controls also stayed unavailable while the request was pending, reducing ambiguity about which version of the form was being submitted. The work preserved the existing scheduling and access rules; it changed how the interface interpreted and explained the response.

Settings and media forms followed the same principle. They retained failed drafts, announced errors and reported success only after the expected confirmation. Editing again cleared an earlier success notice, so a message about the previous save would not appear to apply to new changes. This is a small distinction on the screen, but it matters when someone is deciding whether it is safe to leave the page or whether their latest work still needs to be saved.

By October 21, the work also covered the read side of the posting flow. Malformed initial data was rejected before entering the wizard, with the existing retry path preserving edit or template context. The dated records describe focused checks and Romanian/English desktop and phone workflows using controlled responses. These were local implementation results. They did not establish real profile persistence, media delivery or calendar behavior, and some release checks still awaited separate completion.

Reflection

Success feedback is part of the application's contract with the person using it. For locdemunca.ro, the improvement was to make that feedback depend on a confirmed result while keeping recovery practical. An honest error with preserved work gives someone a useful next step; an unsupported success notice does not.