There's a bug that happens around New Years in a few apps (including Apple's). It's simple to avoid, but you need to submit a fix soon to beat the App Store holiday.
You’ve done the Stanford iOS course and all of the Wenderlich Auto Layout tutorials, but your app is still dumping
Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want
to the console.
On Tuesday, Apple announced the iPhone X, described as “an iPhone that is entirely screen.” On closer inspection, though, the screen does appear to missing a little something.
Sometimes you really care that your app is in the App Store on a specific date. You might think that submitting a week before is enough time, but it’s not if you get rejected. You can’t prepare for every eventuality, but there is one thing you can do that might help
Storyboards get a bad rap. Sure, they are impossible to test and code review, and merges are a real pain. But it takes a second to look at a Storyboard and visualize what the UI is going to look like (or even if you are in the right file). If only there was a way to preserve the visualization but dump the XML.
If you are just starting your career and started with iOS and never learned anything about the web, it doesn’t hurt to know something about other platforms.
These are the top three web technologies you should have some familiarity with, even if you are in Xcode 100% of the time making a native app.
Ok, so you have a view controller that brings up another view controller. Let’s call the first one
FirstVC and the second one
FirstVC either presents
SecondVC or there is some segue that it uses to bring it up.
There’s this myth in the iOS community that “professional” iOS developers never use Interface Builder. It’s meant to imply that coding your interfaces is always better, and if you don’t do it, you are somehow less of a programmer. The myth perpetuates the idea that IB is a crutch, a toy, something that only newbies use.
I call BS.