Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
In general, do you feel that Combine has developed enough that it can replace Cocoa Bindings?
I want to create a data model that is totally based on Combine #Published properties and attach it to my view controller and view with Combine.
But before I spend all the effort, I wanted to get you all’s thoughts on potential pitfalls or considerations I should be taking into account. Should I just stick with tried and true Cocoa Bindings?
Thanks!
Cocoa Bindings are great but they only work on macOS. Apple has signaled in multiple ways that the future of their frameworks is cross-platform (SwiftUI, Combine, etc). Combine is going to enter its third year soon. I'd say it's still early, but not too early.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 days ago.
Improve this question
I am writing a SwiftUI app and am having a hard time understanding the best architectural pattern to go with. I know MVVM is the go-to in mobile development in general, but have also seen sources that say that swiftUI has MVVM built in, so all that is needed is MV. Here is one such source: https://developer.apple.com/forums/thread/699003. This and many other articles say that using swiftUI with MVVM is redundant.
I've also seen other sources that say MVVM is just fine for swiftUI.
Is it just a matter of personal preference? Or, is explicitly defining viewmodels redundant in swiftUI?
Should you factor out the logic that adapts your data model for use by your views? Sometimes.
Do you need a four-letter initialism, a rigid process, or a slew of wannabe-influencers and pundits telling you how to do it? Rarely.
Keep in mind that MVVM was designed specifically for Windows Presentation Framework. If you're looking for an app architecture designed for SwiftUI, try the Composable Architecture.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I understand that in order to use Selectors in Swift, one must mark the Swift function #objc and have at least internal visibility because the function must be exposed to the Objective-C runtime.
So from my understanding, when running those #objc marked Swift functions as selectors, Objective-C's core is majorly involved. So I'm wondering will Apple eventually make Swift completely independent from Objective-C as Swift is primarily written in C++?
Thats a complicated question, and only Apple truly knows. I would say no because of how many apps still use Objective C and the fact the some people still use it in new apps. It would be hard for apple to just completely ignore those developers and potentially take massive amounts of revenue away from themselves and other developers, on top of most of their OS still uses some Objective C. I hope that makes sense and sorry if people get upset that you asked this on SO.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I wa never coding myself before, but I'd like to give it a try and start from Swift. Do you its possible without previous coding expirience or do I need to star from something else?
"Swift can open doors to the world of coding. In fact, it was designed to be anyone’s first programming language, whether you’re still in school or exploring new career paths. For educators, Apple created a free curriculum to teach Swift both in and out of the classroom. First-time coders can download Swift Playgrounds—an app for iPad that makes getting started with Swift code interactive and fun."
Quoted from https://developer.apple.com/swift/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I maintain an app for my business and am pretty much self-taught on code. I understand all of the structural code, and everything is perfectly usable. My problems is with the overall boringness of the looks. Everything is stock iOS from buttons to backgrounds to pinstripes on the list view. Does anyone have any guides or tutorials they used to take a stock iOS app's look to something like the Piictu app? (I'm not looking for something that impressive but in between that and stock iOS; and I'm open to a full app re-start.)
Almost all of controls can be customized with the view properties. and also there are lots of fully customized controls published with its source code.
With iOS5 there is a lot more scope now for customisation of UIKit elements. However, where this is not custom enough for your design then you would need to write your own controls rather than only using Apple'. There are a few good ADC videos on this.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Is it considered kosher by Apple to create an app consisting of nothing but a WebView and the appropriate html/js/css files to support it?
I have an app that could be written entirely within a webview and it would be much easier to get from start to finish that way instead of learning the parts of the iOS SDK necessary to do it.
Yes, it is acceptable, but I would recommend looking at PhoneGap, which is based on a similar concept, but provides JavaScript access to native functionality.