Your question is Reusable Mobile UI Component Strategy. 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're starting a mobile engineering initiative to make UI development faster and more consistent across the app. Different screens have evolved independently, and teams now want a more reusable component model with cleaner boundaries between feature modules.
How would you design reusable UI components and define clear APIs between modules?