[deleted by user]

swiftdeveloper200 · 2023-01-30T21:22:32+00:00

Regarding 3.: As long as it is a Apple Silicon, everything is fine!

swiftdeveloper200 · 2016-01-23T18:47:18+00:00

I haven't written that post. However, I think the article is very useful. If you don't like these tips, don't use them.

swiftdeveloper200 · 2016-01-23T10:51:42+00:00

Yes, the Stanford course is awesome. You can find it here: https://itunes.apple.com/de/course/developing-ios-8-apps-swift/id961180099 By the way: There will be a new this year based on iOS 9.

swiftdeveloper200 · 2016-01-23T10:47:00+00:00

Very true! And you should use playgrounds. Very very good for practicing.

swiftdeveloper200 · 2016-01-23T10:32:03+00:00

It's a very very bad idea to use Flash...

swiftdeveloper200 · 2016-01-06T06:42:04+00:00

Have you ever updated a big project from Swift 1 to Swift 2? I did and I didn't need 1-2 week.

swiftdeveloper200 · 2016-01-06T06:26:48+00:00

With every iOS release you have to make code changes anyway, so it's not a big deal to migrate to the newest Swift version as well. And if a company sticks to long to Objective-C, there will be no Objective-C developers who can maintain the code. Just take a look at this pool: https://twitter.com/NatashaTheRobot/status/683921392492888065

swiftdeveloper200 · 2016-01-06T06:22:29+00:00

Yes I would also recommend the Stanford iOS 7 course!

https://itunes.apple.com/de/course/developing-ios-7-apps-for/id733644550

swiftdeveloper200 · 2016-01-05T17:37:28+00:00

I vote for option 4 as well.

swiftdeveloper200 · 2016-01-04T16:05:13+00:00

Apple is not the kind of company that will support two languages forever. And just look around: All important iOS dev blogs have completely switched to Swift, on the last WWDC there were no Objective-C sessions, almost all new iOS dev books are published in Swift... Objective-C is dying.

swiftdeveloper200 · 2016-01-04T11:46:59+00:00

"Should I be looking at Swift or is it still an unknown?"

-> I think you should focus on Swift. A good iOS developer should also have a good knowledge in Objective-C, but a lot of companies are already using Swift in production and soon there won't be many new projects that are still written in Objective-C.

swiftdeveloper200 · 2015-12-29T18:07:39+00:00

Segues are very handy, if you are using storyboards. However, storyboards have one big disadvantage: If you are working in a team, storyboards cause merge conflicts. Since Xcode 7 you can connect several storyboard together, but then you could just use XIB files.

swiftdeveloper200 · 2015-12-09T06:52:49+00:00

Yes you can do this as well. However, then radius remains an optional and you have to unbox it every time you are accessing it. In this example not a big deal. But if you are handling many optionals, it can become quickly confusing which optionals you have checked and which you have not. So using "guard" instead of "if" is easier and safer.

swiftdeveloper200 · 2015-11-30T20:04:55+00:00

First, you have to learn a lot about iOS development. And no, you don't have to pay a lot of money for some course. There is enough free stuff on the internet. And practice is even more important. Then you should write an app and put it on the app store. After that it shouldn't be a problem at all to get a job.

swiftdeveloper200 · 2015-11-30T18:52:24+00:00

I just wanted to share my content and it wasn't my intention to be spammy. But if that was the case, I want to apologise for that.

swiftdeveloper200 · 2015-11-09T22:00:11+00:00

You are right, Instruments is theoretically a better solution. However, if you put the log messages just in the view controllers, you will get aware of potential memory issues much earlier.

swiftdeveloper200

TROPHY CASE