Note that there are some explanatory texts on larger screens.

plurals
  1. POWindows in iOS, best way to build a multiple-activities app from Android?
    primarykey
    data
    text
    <p>i'm currently developing an app for both Android and iOS, thing is... I started with Android and my app has several Activities with different layouts (Screens with different GUI's, if you are not familiar with android), most of them display very different contents; maps, lists with data from databases, images, text fields with buttons and so on (And most of the time the orientation of the screen changes).</p> <p>The problem comes with iOS:</p> <ul> <li><p>How do I create more windows from IBActions? (Is this a correct approach?).</p></li> <li><p>Once I create a Window, how do I create a new Interface? (Do I need another .xib file?)</p></li> <li><p>If once the user finishes with one Windows, does the previous window remains in memory and can be re-opened? (Can I use a navigation tab, even though the first windows was not a using it?) This is a major problem since iPhones do not have a back button and Android relies a lot on those...</p></li> <li><p>Also, if I can't split my program in several windows, wouldn't my app use a lot of memory from destroying and building views?</p></li> </ul> <p>I'm new to Cocoa development and I have already read a book about Objective C programming (which only teaches syntax and so on), another one about simple iPhone apps (all of them were done in one window, changing the views programmatically) and I'm currently reading another one, but i'm unable to find a simple answer to my problem...</p> <p>I mean I get Obj-C and how to build iPhone apps (well kind-of) but maybe the problem is that I come from a more straight forward development in Android. Each time I see an iOS project, I see it like a total mess, and the documentation in developer.apple.com doesn't help much either, I'm unable to find what I want.</p> <p>Hope someone has gone through this already and is willing to point me in the right direction, thank you!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload