Keep one primary task
A focused sign-in area makes the intended next action clear instead of competing with a dashboard of unrelated services.
THE TRADE-OFF
Brand presentation must not push the form out of view when the mobile keyboard opens.
ENTERPRISE ACCESS EXPERIENCEDesign exploration
Symphony Summit
Make access predictable, including when something goes wrong.
Make access predictable, including when something goes wrong.
Sign-in is a gateway to a task, not the task itself. People need to recognize the service, understand the required inputs, and recover from mistakes without uncertainty.
DESIGNED FOR
Employees signing in to an enterprise IT service platform
A UX reading of the supplied artifacts. The sequence below explains the design logic, not a verified chronology of research. Intended benefits and proposed tests are not measured outcomes.
The user's path
- Recognize the service
- Choose language if needed
- Enter credentials
- Check input
- Submit or recover
PROCESS & ARTIFACTS
How the problem becomes an interface.
Define the access boundary
The shared file focuses on a login experience, with desktop, tablet, mobile, and form-state explorations. It should be evaluated as an entry point, not as evidence of a complete authentication system.
Build a focused form hierarchy
The desktop frame places credential inputs in a distinct sign-in composition, with language and password-visibility affordances supporting the task.
Specify more than the default state
Form component states and the companion design system provide a basis for consistent input, status, and interaction styling. The next implementation step is to connect those visual states to accessible behavior.
Validate recovery and access
Test invalid input, password visibility, keyboard navigation, browser autofill, and small-screen zoom. These checks should happen alongside security review, not be inferred from the visual design.
THE ORIGINAL SCREEN
Symphony Summit · summit-login-desktop
1440 × 900 · Exact source frame, not a recreated mockup.
A downloadable screenshot is not available in this portfolio yet. Open the original frame, or load its Figma preview below. Figma may require sign-in or block embedding.
View the original screenLoad original Figma frame
WHY IT IS DESIGNED THIS WAYEvery choice has a reason.
Every choice has a reason.
And a trade-off.
Allow input inspection
A password-visibility control gives users a way to check what they entered instead of repeatedly deleting and retyping it.
THE TRADE-OFF
Revealing a password has privacy implications. It needs a clear toggle label, keyboard support, and a predictable state.
Make status a shared pattern
The design-system page distinguishes text, border, interactive, and status tokens, supporting consistent feedback across form states.
THE TRADE-OFF
Colored feedback is not sufficient. Errors need readable text, programmatic association, and a recovery instruction without leaking account details.
BEHIND THE FINISHED SCREENS
Design presentations2 pages
Explore project presentations in Figma, without opening the working design file.
ENTERPRISE EXPERIENCE
Symphony Summit
Responsive sign-in explorations and a shared language for form interactions.
Read the UX process & rationaleWhy this page exists
- Purpose
- Explore sign-in at different sizes and interaction states.
- UX rationale
- Access needs to remain predictable on a phone and when a form is not in its default state.
- Next check
- Validate keyboard order, autofill, password visibility, and error recovery in an actual implementation.
Why this page exists
- Purpose
- Give Summit forms a consistent visual language.
- UX rationale
- Separating background, text, border, interactive, and status tokens helps the same feedback mean the same thing in different places.
- Next check
- Document accessible field states and verify contrast rather than assuming the token names guarantee accessibility.
GOOD THINGS START WITH A CONVERSATIONKerala, India · Working everywhere