The use of batching client GraphQL queries can be a useful solution to reduce network requests and improve performance in modern apps. However, it may also introduce issues such as slow loading times, increased complexity, and reduced debugging capabilities. Batching is not always necessary and should only be considered if performance issues persist after implementing other optimization techniques. Manual batching can be done by combining smaller queries into one larger query, but this approach also has its drawbacks, including reduced whole-query caching capabilities. Automatic batching can sometimes be fixed by debatching expensive operations using a tool like Apollo Engine. Ultimately, the decision to use batching depends on the specific needs and constraints of the application.