5 ms·
I don't understand the notion that as a mobile developer you have to do the front end and the backend... I just wrote the back-end for an iOS app, I had nothin
by halis 10y ago
I don't understand the notion that as a mobile developer you have to do the front end and the backend...
I just wrote the back-end for an iOS app, I had nothing to do with the front-end and the sole front-end developer had nothing to do with the back-end.
We used a simple Rest API. Where is the problem?
- jasey 10y agoI think the author was meaning it more in terms of MVC in the iOS project - Web dev - Backend dev scope: Model, Controler Front end dev scope: views - Mobile dev - Where as with an mobile dev, their scope is model, view and controller code (full stack) Your thinking of it in terms of the whole mobile app being the front end and the rest API being the backend. But the app its self has both "front end" and "backend" code segregation its self
- rayvinly 10y agoThanks jasey. That's exactly what I meant. But you laid it out for me.
- robmcm 10y agoIt is a grey area, all web applications I work on have syncing, caching, local storage and offline support. I can also think of many mobile apps that do not. To assume otherwise is a bit of a generalization.
- megablast 10y agoThere is more than one backend. The backend might be the server, or it might be the database/models on the device.