Interface work at Vita is part of the product, not a separate deck that gets reinterpreted later. We prototype the workflow, then build the screens. When the application is Ruby on Rails, the interface lands in that stack. When the product needs its own frontend, the design is made for that too.
Teams who need a clearer product before build, and Rails apps whose admin or customer UI has become hard to use.
Watch the current task, or describe it step by step
Prototype the shorter path
Test it with the people who will use it
Implement it in the application rather than handing off a static file
Screens people can finish a task in, implemented where the data already lives.
Prototypes are a step. The engagement is complete when the interface is in the product.
Yes. We usually redesign the busiest workflow first, not every screen at once.
Customer flows are designed responsive. Native apps are a separate decision from a mobile-ready Rails interface.