Repository navigation
Support Swift in ios template project #7312
Description
As Swift is the future of development with any Apple product, I'd like to know if the ios template that is generated from flutter create could be a swift template rather than an obj-c template.
The code readability of swift in substantially higher that obj-c and seeing as how one of flutters goals is to make development across platforms simple, readability is an easy way to help with simplicity.
Activity
sethladd commentedon Dec 27, 2016
I like this idea. I personally find myself able to read and understand Swift, but not ObjC.
mit-mit commentedon Dec 29, 2016
I like it too; Swift is a lot easier to read.
But for plugins / native interop purposes we likely will need to support both. AFAIK that should be possible, as iOS supports projects with both using "mix and match":
https://developer.apple.com/library/content/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html
sethladd commentedon Jan 3, 2017
@mit-mit if we change the output of
flutter createto use Swift, how would that impact plugins?(agreed that our plugins should support user code written in both objc and swift)
mit-mit commentedon Jan 4, 2017
We think it will be fine, but we need to do more work to confirm it.
1 remaining item
mit-mit commentedon Mar 27, 2017
Changing this to supporting Swift as an option, in addition to OjbC. This could be something like
flutter create -swift myapp[-]Request: convert ios template project from obj-c to swift[/-][+]Support Swift in ios template project[/+]rxlabz commentedon Apr 18, 2017
I suppose it's planned, but an option for swift plugin template like
flutter create --plugin -swift mypluginwould also be handy.eseidelGoogle commentedon May 16, 2017
@rxlabz wrote one btw: https://github.com/rxlabz/FlutterSwiftPlugin-template
mravn-google commentedon May 24, 2017
Closed per #10259
Roll engine to f0a1d6f
Roll engine to f0a1d6f (#25849)
Roll engine to f0a1d6f (flutter#25849)
github-actions commentedon Sep 4, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.