A modern programming language that makes developers happier.

kotlinlang

I'm stuck in analysis paralysis with a small conceptual problem. This isn't strictly kotlin specific but I'm wondering if anyone can help me break my analysis cycle..

with my application following MVP, I'm implementing a new signup flow, and I have something like SignUpActivity, which has FragmentA, FragmentB, FragmentC.  now my SignUpActivity has its own View/Presenter, and this presenter handles the calls to my API classes.. but should FragmentA have its own View/Presenter, FragmentB have its own View/Presenter etc?  or is that over-engineered?  it feels over-engineered and wrong somehow.  I'm sure many people have done this but I'm going in circles trying to decide what's the "proper" way