I tend to deal with the UI parts of a large product we are building where I work, today I had a disagreement with my boss about how to handle some potentially long operations on the android app which is intended for tablets and now I'm unsure what's the right approach. I'd like to know what the general consensus is on how to handle the following type of operation so I'm better equipped next time I need to do similar.
The problem involves making network calls, two or three calls consecutively, each should complete in a second or two but with a busy network you could potentially wait up to a minute and a half for all 3, highly unlikely, but possible.
When we start the call we display a spinner with some loading text. When the first call returned I chose to update the text (in my head, that is to show there has been some progress and that the app hasn't hung). The text didn't explain what the app was doing, just changed from 'Loading' to 'Still working'.
My boss insists that this is bad for the following reasons (a) having our code need to provide a ui callback adds more maintainability issues (b) it exposes how the app is doing what it is doing (c) it could overwhelm the user because most of the time the message wil lswitch after just 1 second
My question is, what do professional UX consider a good experience when doing an operation like this?