Add a 3rd party library to a Swift playground
Swift playgrounds are great for quickly trying out new ideas, it can often be a lot easier to try out concepts within a playground than a whole application. Sooner or later you are going to want to add a 3rd party library to a playground, it is not immediately obvious how to accomplish this.
Implement your own application onboarding flow using a UIScrollView
Many popular applications, Google Translate, Pinterest, Fitbit, SwiftKey, to name but a few, have a series of screens to introduce the applications features/concepts to new users. Commonly, these screens consist of an image, small amount of text and a UIPageControl, allowing navigation between pages.
There are many reasons you may want to inspect mobile app traffic using Charles Proxy. You may want to change the responses which come from your server during testing. You may want to see how your favourite app works. In this tutorial I am going to show you how you can use Charles Proxy to inspect mobile traffic.
Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).
I’ve written before on the subject of Behaviour-Driven Development, here and here. I have found it invaluable in answering the question “what should I test?” Focussing on behaviours rather than tests, helped me a great deal. A focus on validating behaviours soon becomes second nature and I found it a lot easier than Test-Driven Development.
So back in Part 1 we set-up a simple Quiz App, we added Specta and Calabash to the project and most importantly we managed to code to of the steps from the first feature using an outside-in approach. In Part 2 we are going tocontinue where we left off and finish off the rest of the features. By the end of this post we will have a fully passing suite of automated acceptance tests. To finish off I will run through some of the pitfalls as the complexity of a project grows.
So if you are anything like me, you may have noticed whenever you create a new Xcode project you get an associated Test folder with it’s own scheme. You may have even opened up a few of the test files and seen something like this.
Automating iOS Builds in Jenkins should be easy. When you say it fast it sounds like it could be easy. 2 weeks of my life later, the automation of iOS builds has some complexities which I hadn’t expected. The main problem I had was with precompiled headers. It wasn’t long before I got the error “has been modified since the precompiled header”.
For simplicity I am going to write about how to overcome this problem in simple shell commands. For this post at least I am going to shy away from translating this into re-usable build scripts which can be called from Jenkins. The topic sounds like a good future blog post topic through so rest assured I will write about how to create a Jenkins build for iOS builds in the future.
Dependency Injection, why do you need it? You start your new app with good intentions. You strive to keep the code clean but quickly things go wrong. You hook your app to a set of services, add analytics, add some logging. Quickly you find there are dependencies all over your app. It is almost impossible to run automated tests against your app. Difficult to reproduce strange behaviour users are reporting out in the wild. It might be time for Dependency Injection.
Depend on abstractions. Do not depend on concrete classes
In this series of blog posts we aim to show you how to build a Simple Login Form in Swift. Back in Part 1 we left off with a Login Screen which opens when you run the app. In this part we are going to add a LoginService which will manage user authentication. If the user is already authenticated they will be directed to a Welcome Screen. Users who are not authenticated yet will see a Login Screen.
There comes a time when login within an app is necessary to access a secure resource. This post walks through the implementation of a simple login view in Swift. There a number of things new Mobile App developers can find confusing and difficult:
This post will help you with these important topics. Future posts will deal with other things which are important such as validating the username and password before sending a request to the server, displaying validation messages to users, dealing with failed login attempts and what to do when the OAuth Token becomes invalid.
