When designing an API for a system like Twitter, it's crucial to maintain consistency. Opting for a RESTful, resource-oriented approach (e.g., /tweets, /users, /followers ) generally leads to a more intuitive and unified API compared to an RPC style. This consistency simplifies client integration and makes the API easier to understand and maintain.