Question

I am thinking of creating UIView classes and adding all views to single horizontal UIScrollView so that when we are done with one view and click next button, it slides to next view instead of creating multiple UIViewControllers and use UINavigationController to navigate to next page. .
Is it a good idea or causes performance issue? Can you please tell me which way is better and why?

Answer 1

You’re probably better off going with the navigation controller in terms of memory management. At least doing so will make that part of the process easier, but there’s no reason why you can’t do this with a scroll view, you just have to keep track of what elements are on and off screen so you can alloc/dealloc different objects at the right time.

However, if you do decide to go the scroll view route you can simple make buttons on your scroll view that adjust the scroll view’s content offset.x property to jump around between pages, and you can use this to set up the scroll view:

Simply add the number of pages you want as entries in the array below, and the scroll view will be dynamically adjusted to accommodate new views for every page.

[myScrollView setPagingEnabled:YES];

NSArray *arrayOfViews = [[NSArray alloc] initWithObjects:@"First View",@"Second  View",@"Third View",@"Fourth View",@"Fifth View", nil];//number of views you want in your scroll view

[arrayOfViews enumerateObjectsUsingBlock:^(id obj, NSUInteger idx,BOOL *stop) {
    UIView *subView = [[UIView alloc] initWithFrame:CGRectMake(320 * idx, 0, 320, 480)];
    float randNum = arc4random() % 255;
    [subView setBackgroundColor:[UIColor colorWithRed:randNum/255 green:randNum/255 blue:randNum/255 alpha:1.0]];
    [myScrollView addSubview:subView];
    [myScrollView setContentSize:CGSizeMake(320 * (idx + 1), 480)];
}];