Question

I am making an iPhone app with this flow

  1. On initial app launch, user sees screen asking if they want to login to social service
  2. If yes, modal is launched to enter login details
  3. If details submitted, modal is dismissed and a view is presented which provides interaction with the social service

My question is, in step 3, should the View Controller controlling this view be the same VC I use in step 1 or should it be a new View Controller?

I should also note that login details are saved and as long as they are, the user will never see the view in step 1 on subsequent app usage.

What is good practice in this situation?

Was it helpful?

Solution

It's a good thing you're thinking about the view controller flow at this point - you've made a good observation here:

I should also note that login details are saved and as long as they are, the user will never see the view in step 1 on subsequent app usage.

This is a pretty clear indicator that step 1 should be a modal view. What that means is, it is not the root of your app's flow. Step 3, on the other hand, sounds like it is the root view of your app, as it is what users will encounter when they open your app afterwards. If you agree with this, then step 3 should actually be the controller presenting steps 1 and 2. And step 2 might be a push from step 1 instead of a modal view, because the user isn't going to return to step 1.

When you're in the phase of designing app flow, it's important to think about how the user will navigate between screens of your app. But, as the commenters on the question have partially observed, what really matters is how the information flows between screens. It's more important to have a sensible hierarchy of views than to have a sensible series of animations.

Hope this helps!

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top