Ask HN: front-end/back end split in the iOS world

Being relatively new to the iOS world (predominantly web - Node.js, JS, front-end, etc...), I'm finding it has it's ups and downs. ie. I have that useful sense of naivety in approaching iOS challenges (drawing on pre-existing experiences in web tech), but then I'm finding that's also quite a drawback in certain situations.

My question relates specifically to whether people have seen a split in iOS devs, ie. like on the web we have front-end/backend. And more recently, because of the rise in JavaScript MV* frameworks, we now have very front-end people and "client-side engineers".

If we take a social network style app, we have the custom UI to implement, the data layer, caching, data refresh/integrity, auth management, etc...the list goes on. However, those could easily be split into "front-end" and "backend" roles. Does anyone have any experiences from working on a team who does iOS apps or collaborates with iOS devs, whether this split exists?

I'm imagining not so much as web, as iOS dev is primarily done with Xcode (and potentially storyboard), I'm just struggling to see that the split would be so obvious as it is in the web world.

This post has turned into a little bit of a mind-dump, so apologies on that! I'm just more curious as to how it works in the iOS world and what relevant experiences people have had?