Connecting the details behind a better mobile experience.
Payments, rewards, station discovery, and account management are different tasks. Thoughtful interaction design makes them feel like one experience.
- My contribution
- Interaction design, workflows, and interface specifications
- Context
- Frog design engagement
- Focus
- Mobile payments, rewards, station finding, account tasks
- Evidence
- Flow and system-rules documentation
One product. Many moments of interaction.
A consumer mobile app can look like a collection of screens. People, however, experience a continuous journey: finding a station, paying, reviewing rewards, and keeping their account information current.
My interaction-design contribution focused on connecting those moments through predictable pathways, understandable transitions, and consistent behavior.
Design beyond the happy path.
The account flow documents more than a straightforward settings page. It maps changing a password, updating payment methods, examining receipts, contacting support, and returning to other parts of the application.
I value this level of detail because people change their minds, encounter exceptions, and need a way back. A strong experience anticipates those realities.
Orient
Make it clear where people are and what is possible.
Act
Support the next task with understandable steps.
Recover
Plan for errors, interruptions, and alternate decisions.
Continue
Return people to their journey without losing context.
Make interactions consistent by design.
The original system-rules documentation distinguishes navigation, field errors, alerts, modals, takeovers, and half sheets. These patterns are not interchangeable; each communicates a different relationship between the user and the task.
By defining when to use each one, design becomes more predictable for customers and clearer to implement across a team.
Back behavior
Help people move deeper into content and return with context.
Errors & alerts
Explain what went wrong and how to resolve it.
Modals & half sheets
Introduce contextual choices without disorienting the user.
Takeovers
Require a decision only when it is genuinely necessary.
Payments
Support account and payment-method maintenance.
Rewards
Keep offers and rewards understandable within the broader flow.
Decisions that can be built, not just admired.
The project files include iterations, annotated states, and detailed mobile layouts. For me, this is where interaction design becomes a bridge between product intent, visual craft, and engineering decisions.
I enjoy that collaboration: articulating the logic behind a choice, refining the smallest details, and making the experience coherent as a whole.
Clarity is built into the details.
This project represents the systems side of my practice: architecture, screen-level decisions, and the shared language that allows a team to build consistent experiences.
The flows and interaction guidelines helped establish a shared foundation for reviewing decisions and maintaining consistency across the experience.
The ExxonMobil consumer app launched on the App Store. The screens and interaction documentation shown here reflect the period of this design engagement; the production app has continued to evolve.
I love the moment when a complex system starts to feel simple—because every small decision works with the next.