Sagan One

Full article here

Wouldn't it be a privilege to get your app found on iOS App Store? The store puts your creativity at display in front of over 1 billion iOS users worldwide. So the moment you are there, your business prospects get multiplied manifolds. However, it takes real hard-time to create app that can outpace the competition of 2.2 million apps. Indeed, you have to be at your best while pursuing iOS app development. Here is a guide for aspirants as how to get started with.

Create Your Apple ID (If you don’t have any)

Open “iTunes.” Make sure that you have the latest version.

Navigate to the top of the iTunes window, choose “Account > Sign In”. Then click “Create New Apple ID”.

Read and accept the “Terms and Conditions” and “Apple Privacy Policy.”

Complete the form to create your new Apple ID. The email address that you use becomes your new Apple ID. To make account recovery easier in future, it asks about security questions and optional rescue email ID.

Fill the form, click “Continue.”

Enter your credit card and billing information, then click “Continue.” The entered information can be removed or updated later.

Check verification email received, and click on the link therein.

Your Apple ID is ready.

B. Set up Xcode

Read the entire article here

I've worked 3 years within the Sustained Engineering Team at Fiserv, a mobile banking company based in New Zealand. Even with 4 years of experience under my belt, I was amazed about the things I actually didn't know and over the time I realized there were a lot of small things I was doing totally wrong.

What I'm about to write is not the holy truth and I might not cover everything but I hope by sharing my amusing own experience, you'll avoid my mistakes.

Getting comfortable

I worked on a Stat tracking app on iPad, called StatEdge. The whole idea of the app was to track numbers, save it locally and being able to synchronize with a distant database. Because in the past I wasn't used to work with CoreData but a sqlite3 database, I decided to stick to it ; needless to say it was a pure nightmare. The client needs changed every day and so was the database structure. At that time, Parse was still recent, and I never heard of Couchbase and other NoSql solutions yet.

Helpful post to get a better understanding of Asynchronous programming.

Full article is here

've worked and trained with many developers over the years, and I found that many people struggle to get their head around asynchronous programming. Asynchronous structures like Futures, Promises and Blocks are literally everywhere now. Yet, they're still difficult to understand, so I thought I can help you wrap your head around it with some help from Starbucks. That said, grab your Pumpkin Spice Latte and get ready for a Caffeine-fueled adventure through the world of Async programming ☺

Pre-Starbucks - The Synchronous Model

Let's take a moment to picture yourself in line at your favorite coffee store, where they can process only one transaction at the time. You get to the counter, what happens next?

You put in an order for a quadruple espresso (it's going to be a long day ahead)

You pay the extortionate price (when did coffee get so expensive?!)

You stand still...

While you stand your server goes and crushes some beans;

You stand still...

The barista turns some handle's, bangs a big metal thing loudly, steams, froth;

You stand still...

Everyone behind you stands still...

The barista holds the little paper cup under the coffee machine as it pours your drink in;

Everyone behind you waits, checking their phones/watches, wondering who the awkward person ordering a quadruple espresso is;

Finally, the barista gives you your coffee;

You grab your drink; add any additions of your choice and leave;

Now the Server moves on to the next person, who orders a single bottle of water they've been holding the entire time, they pay and leave immediately!

Welcome to the world of synchronous programming! You ask a function to do something and you wait until they've done it. And if someone else wants to do something that could be much quicker, they have to wait!

See this link for more

Just some examples:

BestBuy

Amazon

Bing

Box

BrainTree

Business.gov

Eventful

Facebook

Flickr

Foursquare

Google App Engine

IBM Watson

Last.fm

Netflix

Product Hunt

Stripe

Twillio

Link here

SwifterSwift is a collection of over 500 native Swift extensions, with handy methods, syntactic sugar, and performance improvements for wide range of primitive data types, UIKit and Cocoa classes –over 500 in 1– for iOS, macOS, tvOS, watchOS and Linux.

List of All Extensions

SwiftStdlib Extensions

Foundation Extensions

UIKit Extensions

AppKit Extensions

CoreGraphics Extensions

CoreLocation Extensions

MapKit Extensions

SpriteKit Extensions

Misc. Extensions

How cool is this?

SwifterSwift is a library of over 500 properties and methods, designed to extend Swift’s functionality and productivity, staying faithful to the original Swift API design guidelines.

Read the entire article

Another week, another assortment of atrocious design worthy of MOMA. In the interest of variety, I have added a few newcomers to this issue. One is a piece of architectural design and the other is a brand I have never featured before. Of course, I have also included the requisite examples from big brands like Facebook and Apple, because those companies are bad design factories. All in all, it’s a good haul this week.

If you’re wondering what gravity has to do with all of this, you’re just going to have to keep reading.

Important lessons

Know your user and the circumstances in which they will be using your product.

Sometimes simpler really is better.

Read the entire post here

A few years ago I conducted one of the most interesting interviews to this day. And, it came with a big twist in the end. We were looking for a junior AngularJS developer. Writing basic directives, simple two-way data bindings, clean code - yes. Deep understanding of the digest loop, interceptors, XSRF protection, fancy design patterns - no, not necessarily. Then out of the blue, THE MOST gorgeous candidate applied. Strong background with not just Angular but plenty of backend frameworks as well, he had even coded mobile apps in his spare time. Had that slightly arrogant half-smile going on, as if to say "Don't know why you even bother, dude, I'm your man." Here comes the twist, though. For 20 minutes of intro talk, we barely spoke about Angular. Such was his urgency to showcase all the various assets of his skill set that what I really wanted to hear was a sentence and a half about some dull directive he wrote one time. Then came the technical part. In the next 30 minutes, I could actually see his confidence evaporating from the room, although I was trying to be as friendly as possible. Turned out his Angular knowledge was shallow, the tip of the iceberg, "I saw that in a tutorial once" type. Although he was presenting himself as a senior developer, he was a mere junior level for this position. Expectedly, he didn't get the job. We hired a quite younger girl with less overall experience but much more focused on what we needed. See, not that he wasn't smart - he was. I'm sure he would have caught up eventually. His problem was different - he didn't have a niche. He hadn't picked a thing. He was ok for everything but good for nothing.  

This is your #1 Junior Developer Mistake - not picking your niche early.

Read full article here

Looking for interview questions & answers? Need to find iOS chart or animation library? Or maybe you are just curious to check new open-source apps, free courses, coming conferences or people to follow on Twitter. Whatever you’re looking or need, you will find that on GitHub :)

There are really a lot of iOS gems done by the community! We made our research and collected the most useful repositories for you. For sure, you will find there a bunch of practical resources and a lot of inspiring ideas.  Check it out!