So NativeScript now requires a Mac to develop for iOS

Thread is closed for posting
6 posts, 0 answers
  1. Sergei
    Sergei avatar
    44 posts
    Member since:
    Aug 2012

    Posted 06 Mar 2015 Link to this post

    Cross platform compatibility has always been a great benefit of using Telerik. This changes with NativeScript because iOS emulator doesn't run on anything but Mac (thank you Apple). So, it seems there are only two options: 

    1. Acquire a Mac (Mini?) and use it to run a simulator. 

    Can I access the simulator over a local network or do I need to actually be logging into Mac?

    2. Use AppBuilder and deploy development builds to physical devices. 

    The obvious problem is that you've got to have a collection of devices if you want to test well. Will it have the "three finger" refresh built into it? 


    Am I missing some other option?
  2. Todd
    Todd avatar
    7 posts
    Member since:
    Jun 2012

    Posted 06 Mar 2015 in reply to Sergei Link to this post

    Hey Sergei-

    The options for building/deploying apps with NativeScript are generally the same as Apache Cordova/PhoneGap.

    If you're using AppBuilder, you don't need a Mac. We'll do all the building in the cloud for you (just like with hybrid apps). From there, you can either:

    A) Deploy to your local device (and take advantage of LiveSync updates as you make changes), OR
    B) Use the NativeScript companion app to scan the build QR code instantly load the app on your device

    The cool thing about NativeScript (compared to Cordova) is that you generally don't have to worry about plugins in the companion app because NativeScript takes care of all interaction with the native APIs. That means the companion app should be useable for testing more of your app code (before you do a full install of your own app package).

    If you do want to use the iOS Simulator, then yes, today you'll need a Mac. We're working on that, but as you noted, there are some "hurdles."  If you have a Mac and AppBuilder, you should be able to launch and run the iOS simulator directly from your non-Mac machine:

    http://docs.telerik.com/platform/appbuilder/testing-your-app/running-in-emulators/ios-emulator#run-app-in-the-native-ios-simulator-from-the-appbuilder-windows-client 

    Hope this helps.

  3. Sergei
    Sergei avatar
    44 posts
    Member since:
    Aug 2012

    Posted 06 Mar 2015 in reply to Todd Link to this post

    Thank you Todd.

    We do all development on Linux Ubuntu, so the Windows way you mentioned wouldn't work. 
    I know that the CLI client runs just fine, and, obviously Android simulator does as well (we love Google for its commitment to cross-platform compatibility), and it is essentially Apple's issue, but, if you find ways around it, please post it here.
  4. Steve
    Steve avatar
    1851 posts
    Member since:
    Dec 2008

    Posted 10 Mar 2015 in reply to Todd Link to this post

    Hey Todd, can you elaborate on 
    "Deploy to your local device (and take advantage of LiveSync updates as you make changes)"?

    If I Build and Deploy my app to my ipad changing the code doesn't update anything?  Do you mean load up the companion app, and do the 3 finger refresh on changes?
  5. Mihail
    Admin
    Mihail avatar
    75 posts

    Posted 13 Mar 2015 Link to this post

    Hello Steve,

    Yes, you can use NativeScript companion app and its LiveSync feature. Build and Deploy (app package) option does not support LiveSync at the moment. However, we are actively discussing whether and how to bring LiveSync feature to Build and Deploy scenario. Stay tuned.


    Regards,
    Mihail
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  6. Sergei
    Sergei avatar
    44 posts
    Member since:
    Aug 2012

    Posted 13 Mar 2015 Link to this post

    Mihail, Todd,

    I appreciate you responses, and using the companion app works for the basic situations, but once the project needs a 3rd party library, it is not suitable for the companion app anymore. I am not at that point yet, but I see it as a serious limitation we'd be facing soon. 
    I hope this feedback allows you to fine-tune your new technology to make it an even bigger hit. 

    Thank you.     
Back to Top