Your question is Build a Reusable Mobile Component Library. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You’ve been asked to improve consistency and development speed across the rider and driver mobile apps by creating a reusable component library. The goal is to reduce duplicated UI patterns, make interfaces between feature modules clearer, and give teams a safer way to ship shared changes without breaking app-specific behavior.
How would you design a reusable mobile component library with clear interfaces between modules?