iOS emulator

[iliyas Abdul Kader]

Hi friends, I am new to Flutter development. I am in Windows 10 environment. Is there any way to use iOS emulator for Android Studio without VMWare?

Thanks in advance.

[Michael Thomsen]

Sorry, no. The iOS Simulator is provided by Apple as part of the Xcode IDE, and they only make that available for macs running macOS.

But there are a number of Cloud-based services where you can rent a mac on hourly/daily/monthly basis.

On Thu, May 24, 2018 at 7:05 AM iliyas Abdul Kader <iliya...@gmail.com> wrote:

Hi friends, I am new to Flutter development. I am in Windows 10 environment. Is there any way to use iOS emulator for Android Studio without VMWare?

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "Flutter Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[samsafay]

FYI - I haven't done this but I think, since Flutter's philosophy is "write once and use everywhere", you can continue developing your app on Windows and see it on an Android Emulator until its completely done!

Once its done, rent a mac from Macincloud and then clone your repository to your Mac machine. Then use Xcode to generate your ipa file and then upload it to the Appstore via "Application Loader".

If you decide to go with their "Managed Server" you have to ask them to install the latest Android Studio for Flutter. I have used their Managed Server for React-native project, it almost have everything you ask for.

I haven't tried a Flutter app in Macincloud but If you are interested, I can let you know in couple of days if it works or not?

Disclaimer, I am a React-Native developer whose trying Flutter for the first time.

[Fabio de Matos Quaresma Gonçalves]

I'm sorry for the nitpicking, but "write once use everywhere" is java's motto. React native is "learn once write everywhere" https://reactjs.org/blog/2015/03/26/introducing-react-native.html, which I still think is not exactly right. I have had countless conversations with countless people over the years about why you can't solve some problems the same way in Android and iOS apps, either for UX reasons, not being accepted on the store, or the phones not having such-such feature. Many times hybrid developers, designers and managers assume that Android and iOS phones are exactly the same, although it's quite obvious at 1st contact they're not.