I just wanted to add something to my above comment.
When I have built my app, I used an iPhone 4s to test on a real device, my mum gave me it That was really good because since the device doesn’t had that much memory, when I was building my massive wizard, I really had to take care to save memory and to optimize my code.
But when I tried later to finish my app and include push notifications, it was difficult because I had trouble to make it running because XCode and iPhone 4s and supporting version weren’t that compatible anymore to do so. So I spend 1, 2 maybe 3 weeks on the problem and finally bought an iPhone 6 2nd hand and I solved the issue and finished the push implementation in one day
Long story short: older phone are also good because it force you to think about memory and speed but sometimes, some features you would like to build need a newer phone to be developped.
Therefore right now, February 2018, I think iPhone 6 is a good solution
Of course, just, if you try the wizard and don’t really have a room to let or looking for a roommate, plz don’t press the last button “publish”
But if you have a room to let, go for it, press “publish”
When you do an account, you gonna first be asked “are you looking or offering a room?”. Answer “I’m offering a room” and you gonna land in the wizard build with a slider, containing around 10 steps (it’s dynamic and that’s the thing, I couldn’t load 10 steps on an iPhone 4, even when the first version of WkWebview)
I stopped using the ionic slide component, but regrading memory usage I suggest wrapping each slide content in an *ngif condition so it only impacts on the dom if it is the activeindex.
@JAR19 yes exactly, it’s what I did and one of the reason why it works like a charm always only three slides active, the previous, current and next one
But it’s what I meant. On an iPhone 8 or local machine, there is enough memory, so you won’t notice such problems. Having an older phone allows you to discover such problems before your users does
I’m also an Android/ PC user. I’m using macincloud Managed server (https://portal.macincloud.com/select/#/plans). It is an awesome service where just for $20 per month. I have fixed all the issues which my client has on his iPhoneX 11.2+ using above service. And also I use chrome 64+ iOS simulators too. That too awesome. It has a built-in iPhoneX simulator too. I don’t have any iOS device. My client has the iPhoneX device and he does the testing using it and log issues. After that, I’ll fix it using above service. So far I have fixed all of those issues. No issues to me even though I don’t have any IOS device. If you need any information about macincloud please let me know. I have huge experience with that service. Cheers!
Usually I use ionic serve most of the time for development. Before deploying a new feature, I test them on a device. I rarely use the emulators, because I encountered many visual and functional differences in comparison with real devices. This applies to ios and android emulators. Sometimes they are helpful if you have to test different screen sizes and don’t own devices for these. But if you can choose between a real device and an emulator I recommend the device.
Device farms are nice, because you get screenshots and videos from real devices. If you have to fulfill strict requirements it is a good way to check if your app behaves correctly on many devices.
Hi, I have an iPhone 7 and I want to deploy it on it. Can I emulate this my iPhone connected to my Windows USB using Macincloud? Or can I just emulate the native Mac emulators?
That was really good because since the device doesn’t had that much memory, when I was building my massive wizard, I really had to take care to save memory and to optimize my code.
