title: Architectural approach in iOS Interface Builder
body: <p>Would you code this design mockup below as tableview with sectioned groups that are padded on the sides with custom cell types or would you put the groups in a scroll view and make each section a built up UIView. </p>
  
  <p>This isn't an opinion based question or "to general" this is an iOS development design problem. </p>
  
  <p>In Interface-Builder I have seven screens that look like the image below. If I use a tableview for the scrolling and used grouped sections those sections should not be able to scroll they need to be static for lack of a better word. Is that even possible? </p>
  
  <p>The sections headers will stick at the top until you scroll past them which isn't what I want. </p>
  
  <p>I can't put a static un-scrollable table in a scrollview either since that is just backwards and wrong. Also with this approach I have different sized headers for each section and different cell types for each section. Seems rather tacky/hacky to do this. </p>
  
  <p>If I use the UIView build up approach thats a lot of building since there are 7 screens that have this look. </p>
  
  <p>What is the better decision based on a native iOS development approach? Better to use a lot of custom TableViews for each screen or a bunch of UIViews with subviews? Both approaches have major trade-offs to me which is unusual in my experience. Do you see a better approach then what I'm going after? </p>
  
  <p><a href="https://i.stack.imgur.com/xZqub.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xZqub.png" alt="enter image description here"></a></p>