South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Safer... don't make me laugh.
What exactly is driving your need to build iOS apps? ... because if this part of a career objective then it's an investment you probably need to prioritise.
Agreed brilliant little machines; such a pity Apple still hasn't released a new model.
Xcode has gotten quite a bit better with Xcode 10; certainly much faster compile times and a lot more stable. Can't talk for storyboards and xibs, because I've always actively avoided that; far better and more flexible to learn how to construct interfaces in code.
Yes you can, but you need to connect your Windows Xamarin to what is basically a Mac based "build host", but this is buggy and slow. Multiple clients can theoretically use the same build host. I eventually gave up before insanity set in and just bought a Mac.
If its just for dabbling, and/or to get familiar with Swift, then I'd even go so far to suggest Silver from RemObjects, which is in strict terms more of a variant of Swift that allows you build apps using the .NET, Java, and Android framework APIs.
Interesting, noted, thanks!
I wasn't really promoting cross platform, but rather suggesting an option for someone who wants to play around with a Swift like language variant in Windows.
For most use cases, designing a native app isn't worth the time/resources though.
I disagree, plus I'd counter argue that any app that isn't worth designing a native app for simply shouldn't exist. Majority of the garbage apps are all written in these pseudo cross platform solutions.
Disagree on that, don't think we can both agree on this. Just because a lot of garbage apps are written using cross-platform, doesn't mean cross-platform is bad. That's like saying the Android/iOS store is garbage because there are so many useless apps in it.
So UI wise: UI will be the same on Android and iOS, with both having notifications integration, etc. (EDIT: You can edit how it's displayed etc. to customize your app)
You're far above the average dev in skill. Remember, a majority of devs will be the cheapest people that can fulfill the task well enough for the business. Most businesses will not pay that extra bit of money so you can optimize the app a little bit more as it doesn't have enough of a return for them, this not taking into consideration if the dev can actually do so.
You do know that Flutter compiles into platfrom specific code, unlike React which uses a JS bridge? Admittedly Flutter uses its own widgets instead of OEM but I'd take that as a plus.
You're making this too easy for me... Yes both of those stores are filled with garbage, and their idiotic app models have destroyed the notion of any profit for the lone developer in the mobile app space. Historic issue if you missed it; if the priority is boasting about how many apps are in store; then even garbage matters.
Weird correlation: all these cross platform have the worst UIs -- wonder why?
In most cases the decision making people that buy into these cross platform fairytales have very little actual experience as a developer. Buying into fairytales is the problem, not somebody's acumen.
I know you're not asking me that question. Ps. plugins.... mmmhhh wonder if its so "perfect" then why ever do they need that...? ...and why explain how a widget is not a UIView... Fairytales...
The problem is that equation is never assessed; somebody buys into the marketing fairytale and a proper assessment is never done. While you at it remind me again which costs more: development, maintenance or dare I say it providing a good customer experience.
You're making this too easy for me... Yes both of those stores are filled with garbage, and their idiotic app models have destroyed the notion of any profit for the lone developer in the mobile app space. Historic issue if you missed it; if the priority is boasting about how many apps are in store; then even garbage matters.
Ps. I certainly have never considered mixing my good stuff with garbage.
They do? Haven't noticed that. Most cross-platform use a nice Material Design that works perfectly well on both platforms. Again, I only have iPad equivalent apps and not iOS ones.
I answered you in the PM, hope I made myself clearer in it? Not saying there aren't trade-offs, just that sometimes those trade-offs are worth it.
Lol, the biggest gripe with performance on React is the JS bridge. Flutter removes that bridge, so it's faster in-app. Fairy tale thing again, native implementation compiled aot would be better of course, but trade-off for faster product launch/easily cross-platform consistency.
Small projects, not large ones like you work on where the majority of the code base is non-GUI.
And I agree with you, poor planning is a key reason why projects fail. Writing a cross-platform app or native app depends on your use-case, and if you can't properly analyze your use-case and buy into marketing/buzzwords instead of actual implementation, then you've failed as a project manager. Again, sometimes it's not that easy either, sometimes the client forces you to go the cross-platform route (heck, even had clients that force WP usage when they clearly only need a static site, so loading all that additional garbage when not needed, you could argue that it's bad that you didn't convince your client, but your client will just go to the person who does it and you lose out, so it's easier just to use it if the draw-back isn't too large).
It doesn't take much Google effort to see that a lot of users don't share your point of view. Material design is awful idea; same design everywhere is never a good approach with UI/UX.
Agreed, too much garbage on them, what I mean is that there are good apps on it.
They do? Haven't noticed that. Most cross-platform use a nice Material Design that works perfectly well on both platforms. Again, I only have iPad equivalent apps and not iOS ones.
So how exactly is that a positive thing?
Huh... mobile apps where the code base is non-GUI? Example?
Did you read this article? Certainly plays into my conclusions i.e. crappy UX is non native.
... quote, the conclusion is that we should go with non-native if:
... sounds like the recipe for a crappy UI / UX -- which is quite typical for a garbage app -- clearly I'm missing the point you're making?
![[)roi(]](/forum/data/avatars/m/8/8711.jpg?1563828683){kind=avatar}
