Products shaped around real devices, interaction states and release constraints.
MICHAELANGELOCORRAL
Designing the interface, building the product, and refining both until they feel connected.
One connected practice
My work sits between visual direction and implementation. I care about how something looks, but just as much about what happens when it reaches a real phone, browser, client, and release.
Proof in the work
02 / The body of workTwo surfaces.
One connected practice.
BUILT ACROSS
REAL PRODUCTS.
Client work, product sites, concepts and visual web explorations.
Native Android + modern web, connected by one product-thinking process.
How the work moves
03 / A repeatable loopFROM FIRST QUESTION
TO THE REAL THING.
The process changes with the project, but the principle stays the same: make the direction clear, build it faithfully, then refine what reality exposes.
Direction before decoration
Interface, hierarchy and motion
Native and web implementation
Responsive QA and release polish
I like work where the visual idea survives contact with production.
That means considering real content, device behavior, loading, accessibility, motion, performance, and the next action—not just the screenshot.
The strongest result is usually quieter than the first idea: fewer competing elements, clearer hierarchy, and motion that reinforces the structure instead of distracting from it.
Working principles
THE RULES BEHIND
THE VISUAL WORK.
Clarity before decoration
The useful path should be obvious before motion or visual effects are added.
Design for the real screen
Width and height both matter. Media, type, and spacing are judged in the viewport people actually use.
Design and build stay connected
The implementation should preserve the decisions that made the design work in the first place.
Polish is cumulative
Typography, states, loading, motion, responsiveness, and performance all contribute to the final feeling.
Currently available