Both Android and iOS Frameworks have a lifecycle. But in iOS, there are 2 important functions that don’t exist.
onSaveInstanceState/onRestoreInstanceState -> doesn’t exist
onActivityResult -> doesn’t exist. You have to use Navigation Controller with delegates (listeners).
Also, note that it’s tough to compare lifecycles from Android and iOS. I think that more detailed comparison deserves a separate article.
Very good article sir
Great and very useful article, thanks!
I’d just like to point out that the equivalent to Android’s “multi-line scrollable EditText” would really be UITextView, not EditText.
Thanks Jonathan, right, it should be TextView. I just updated it
Great article, minor correction on Libraries you mistyped Gradle instead of Glide.
Thanks Lucas. I think that I fixed it yesterday. Maybe it wasn’t updated properly. I will recheck it.
Have to point out, creating layouts can be done programatically (constrains / anchors / stacks), which is much more advance than any interface builder by achieving reusability and scalability. (Plus real developer/engineer don’t program by mouse.)
Thanks, Eisen. Right, I thought that it was covered by ‘and Swift’ but I should probably add a clarifying note.
Hi there! Would you mind if I share your blog with my myspace group? There’s a lot of folks that I think would really enjoy your content. Please let me know. Many thanks|
Appreciate this post. Will try it out.|
Hi there, I enjoy reading all of your article post. I wanted to write a little comment to support you.|