Ben Dodson

Freelance iOS, Apple Watch, and Apple TV Developer

The Divide #6 - The 'JJ Abrams' of game lists

This week we’re back on schedule and episode 6 of The Divide is now available. Chris, John, and myself discuss over 40 games that are being released this year and pick out a few of our favourites including Crackdown 3, Final Fantasy XV, Zelda, Mass Effect, Street Fighter V, and Yooka-Laylee. We also spend some time discussing the Oculus Rift pre-order and I have a bit of a rant about the rumoured removal of the audio headphone jack from the next iPhone1. Finally, Chris is still upset with JJ Abrams…

You can get The Divide from these fine outlets:

Don’t forget to leave a review on iTunes and follow us on Twitter via @PodcastDivide

  1. Short version: I’m cool with it being removed. ↩︎

Fixing emoji footnote arrow bug in Jekyll

I’ve been using Jekyll as my static blog generator for a few years now but noticed a minor annoyance a few days ago; whenever I use footnotes1, the return arrow (↩︎) is converted into an emoji (↩️) on iOS and in some RSS readers. Obviously this isn’t desirable and so after a bit of digging I was able to find a fix.

Firstly, this isn’t an issue with Jekyll but with kramdown which does the Markdown conversion. Thankfully, there is a config option in kramdown 1.8.0 and above2 that lets you specify the text you want to use for the footnote return link and you can set it as unicode to stop it being converted to emoji. Just add the following to your _config.yml file:

kramdown:
  	  footnote_backlink: "↩︎"

Regenerate your site and you should find that the emoji arrow is now back to a ↩︎.

  1. like this one! ↩︎

  2. You may need to run gem update kramdown if you installed Jekyll a while ago. ↩︎

Dodo Apps

After selling WallaBee last year, I changed my company name to Dodo Apps Ltd. Now that I’m publishing my own apps again (in addition to my freelance work), it seemed time for me to make a few changes to my website.

Today I’ve updated bendodson.com so that my client work and my self-published apps are now in separate sections1. I have also created a new site at dodoapps.io to advertise my own apps that are currently available in the App Store2.

I am currently available for freelance work from February 2016. For more details, please contact me.

  1. My more recent apps also have some nice photos or screenshots to show them off a bit better. ↩︎

  2. Including a sneak peek of my upcoming “Music Tracker” app… ↩︎

Swift extension to make CALayer borderColor and shadowColor work with Interface Builder

I’ve been using Interface Builder in more projects over the past few months due to the benefits of AutoLayout. This has led to me shifting more standard UI code (i.e. colors, borders, shadows, etc) into Interface Builder via the User Defined Runtime Attributes1. However, this doesn’t work for the CALayer properties shadowColor and borderColor as they expect a CGColor rather than a UIColor.

To fix this in a recent project, I created a very basic CALayer extension (in Swift) that adds UIColor accessors so you can set them via the User Defined Runtime Attributes as so:

You can get the extension on GitHub.

  1. You basically just set layer.cornerRadius as the key path and use an NSNumber within the User Defined Runtime attributes and then Interface Builder will handle the rest - no more filling your code with button.layer.cornerRadius = 8, etc. ↩︎

The Divide #5 - 'Jar Jar Abrams', a Star Wars special!

After a slight delay in recording, Episode 5 of The Divide is now available. As a New Year treat, this show is a 2 hour special all about Star Wars. We discuss the original trilogy, the prequel trilogy, some of our favourite Star Wars video games and comics, and then dive into Episode VII, ‘The Force Awakens’ (there are numerous spoilers but we confined them all to the last half hour or so and there is a big warning before we start). We also discuss one of my favourite oddities in the re-release versions, the addition of CGI rocks to Episode IV:

You can get The Divide from these fine outlets:

Don’t forget to leave a review on iTunes and follow us on Twitter via @PodcastDivide

iOS developers don't work for free

Over the years, I’ve received a lot of emails offering me the chance to work on an exciting new project for free in return for some equity. This is an excerpt from one I got yesterday:

We are currently developing a [redacted] site with some developers who are dragging their heels and would like to to jump ship. They are more web developers and not used to app coding. They have been working for free in returning for an equity share in the company.1

We have pitched to a few venture capitalist who like the idea but need to see a minimum viable product out in the market place.

Is this something you would entertain… work for free now but get a percentage of the company?

I write back to (nearly) every email I receive so I used my standard “sorry, I don’t ever work on an equity basis as per my website” reply. However, it’s starting to irritate me just how many of these emails I get per day, the fact they don’t read the clear disclaimer on my contact page, and the mindset that they must have to think that someone is going to work for free for a potential kickback later. Hopefully this post will clear up why I, and most other iPhone developers, will not work for free on your project2.

Short version: We have mouths to feed the same as anyone else.

Long version: There is a huge amount of paid work available to freelance developers and it pays incredibly well3. Some might say that developers are risk averse and so of course they’d choose paid work over the risky equity venture but that isn’t really true — being a freelancer is already incredibly risky with the fact you have to find work and hope that the client does pay on time and as agreed. That said though, choosing equity over money is one step too far on the risk ladder; the chance of it succeeding is very small and you’ll end up working on it for much longer than you anticipated.

For example, lets say you’re a developer charging around £500 a day for your services. To get a project to MVP status, you’re likely going to need to work for 1-2 months so you’re looking at around £10-20k of lost revenue. At this point, you need to make back at least that sizeable amount of money in order to break even. However, as the MVP continues, there will be bugs and new features to be added and you’ll be expected to add them for free; after all, you’ve been doing it for so long by now and if the project needs to switch developers then it’ll most likely die and you’ll end up with nothing. You will keep working for free until the project does eventually fail; you might get some small amount back but the real likelihood is that you’ll end up with nothing but a portfolio piece and the realisation that you should have filled the last 6 months with paid work.

This isn’t hypothetical; whilst I don’t ever work for equity, I’ve worked on a freelance basis on projects who did have other developers working for equity. They were hardly ever available after the project launched (as they needed to work on other projects to put food on the table) and when they were available they did a poor job as they were doing it in their spare time and they’d lost any passion they had for the business. The project folded after 9 months and they got around £1500 for their troubles.

Even if a project does succeed and you do own a portion of the company, it is still going to be a very long time until you see any monetary reward for that. A company only pays it’s shareholders when it is profitable and most startups aggressively use any money they make to grow further; it will likely be years until you get anything. Of course, they might sell to another company and you’ll get a big windfall payment4 but that is highly unlikely.

The biggest issue I have with ‘CEOs’ saying “work for free now but get a percentage of the company” is the hypocrisy of it. They are putting all of the risk of the business on the developers shoulders and bearing very little of it themselves. Most of these people with nothing but an idea are working in a full-time job and continue to do so during the life of the project as they don’t need to do much during development; if it fails, they don’t really lose much whereas a developer loses everything.

My one piece of advice for other freelancers and for people looking to hire them is “if the project owner isn’t willing to use savings or a loan to pay for a developer, then they are showing that they think the project is too risky”. When I built WallaBee, I insisted that all contractors were paid at market rate5 and did so with loans and money from my own freelancing6. If you are trying to get an app built and you don’t do the same, you will not succeed.

This is why I do not work for equity. It isn’t just the fact that I’ll lose money, it’s that I don’t want to work for a business that treats professionals in this way7.

  1. By this point I’ve already dismissed the project out of hand even if they are paying; I don’t work on projects started by other developers and I don’t work for people who treat developers who work for free like crap. I can’t ever imagining being this dismissive of people who have given their time for free and are presumably leaving with nothing. ↩︎

  2. This should really be considered part 1 of a series entitled ‘So you want an iOS developer?’. Later articles in the series will be ‘Why iOS developers won’t sign an NDA’ and ‘Why you should pay your invoice when you receive it, not 60 days later’↩︎

  3. I charge near the higher end as my portfolio and experience allows but even at the lower end you’re still talking £300-350 per day! ↩︎

  4. As we discussed on this weeks episode of The Divide ↩︎

  5. One of my freelancers wanted to have equity and I said no. In my opinion, only founders should have equity tied up in a startup as then they are the ones that succeed or fail; contractors should always be paid. ↩︎

  6. I haven’t made back the money I invested in that business yet but I do have equity in the company that bought it; that is a scenario where equity can be appropriate. ↩︎

  7. I have form in this belief. Many, many years ago, I was offered the chance to work on a project by a guy who was happy boasting about the millions he made from a previous project. We agreed my freelance rate and when we’d start. He changed the start date and I found other work. He then wanted to move the start date back and was very annoyed when he found out I’d taken other work; he then went on to try and negotiate my day rate down. I walked away at that point as I don’t work for boastful millionaires who look to save £20 a day on an already low freelance rate. That company was Hailo and became wildly successful. I don’t ever regret not working for them (though I probably should regret not asking them for equity). ↩︎

Pocket Rocket, read your Pocket articles quickly in Safari on iOS

Ever since I sold WallaBee, I’ve been splitting my time between client work1, my Xbox One, and doing small apps that help improve my life in little ways. Today, Apple finally approved2 my first self-published app in a long time, Pocket Rocket:

I save most articles that I want to read at a later date with Pocket but I hate their mobile apps. Tapping an article will load their own reader view3 and it’s an extra step to jump to Safari. In addition, their apps aren’t updated for split screen support or new device sizes and so the experience is pretty poor. With Pocket Rocket, I wanted to do one thing; have my Pocket queue load up and then when you tap on an article it should load in Safari. I prefer using Safari as then you get to see the article as intended and with content blockers most pages load quickly. I got the basic version working within in an hour and it worked well enough for my needs; then, when I got the iPad Pro, I realised this could be a useful app for other people as it dramatically improves the reading experience especially when used in split screen mode.

Pocket Rocket is completely free with no ads or tracking4. It runs on any device capable of running iOS 9 and is a fully adaptive so it looks great no matter what screen-size you have. Due to this adaptability, it works in all split-screen modes on applicable iPads and that is the way I tend to use it. You can swipe on an article to archive or delete it upon reading. There is also a settings panel so you can choose whether links open in Safari or via an in-app browser (with the option to enable a reader view5 on launch if you want).

You can get Pocket Rocket for free on the App Store.

  1. Of which I’ve done a lot; recently launched apps include Brapp, Chipp’d, and Natural Cycles with two more apps awaiting approval from Apple… ↩︎

  2. I won’t go into details as Apple specifically request people don’t, but it has been one of the longest and most painful App Store review processes to date. I don’t know if they’ve been having a bad month but a number of my projects have had a rough ride through the review process for no good reason lately. ↩︎

  3. I hate their reader view as it often misses text or puts pull quotes in the wrong places. In addition, the scrolling was completely broken on the iPhone 6S for a few weeks. ↩︎

  4. Literally nothing leaves your device apart from when you log in with Pocket (and that is a secure connection with Pocket’s servers via OAuth so I see nothing); I don’t want to know anything about you and respect your privacy. This also isn’t a money-making exercise so the whole thing is free with no In-App Purchases. ↩︎

  5. The reader view is only available in the in-app browser, powered by SFSafariViewController, as there is no URL scheme for opening Safari with reader view enabled. I’ve submitted a Radar (rdar://23684808↩︎

Natural Cycles Apple Watch app

I’m very proud to announce that my first Apple Watch app for a client has gone live in the App Store; Natural Cycles.

Natural Cycles is a popular iPhone and Android app that allows you to track your fertility or plan a pregnancy. It can tell you when you are fertile, when you are ovulating, when your next period is due, when you are pregnant, and the progress of your pregnancy. I was hired as a freelance Swift developer to build an Apple Watch app that would be bundled in with their big v2.0 update and would allow viewing and logging of this critical information. The app allows you to see your current fertility level, body temperature, and progress of your period as well as viewing messages from Natural Cycles. In addition, you can quickly update your current body temperature and menstrual flow within the app:

As well as the core Apple Watch app, I also added support for Notifications and Glances making for an even quicker way to view your information:

My favourite feature, however, is the addition of full text Complications so you can see your current body temperature and fertility status on your watch face:1

The project was quite difficult (but rewarding!) for a few reasons. Firstly, the design was very ambitious when watchOS severely limits the amount of customisation that can be performed. Secondly, the iOS app was a Cordova app2 rather than a native app which meant I had to write a JavaScript plugin and set up some build scripts in order for the native Swift watchOS code to be able to speak with the iPhone. There was also a requirement to make the app as easy as possible to update (i.e. updating the iOS app shouldn’t break the watchOS app) and so I built everything such that the phone takes care of all logic and a lot of the UI so the watch app can be altered without going through the App Store review process.

This was a really exciting project to work on and I’m very happy with the end results. You can download Natural Cycles from the App Store or learn more on their website.

  1. This did lead to an awkward situation when I’d left the complication enabled on my Mickey Mouse face that I use at weekends; the weekend after testing was complete, I switched to my Mickey Mouse face to be greeted with the words “Not Fertile” underneath his tapping foot! ↩︎

  2. I don’t usually work on non-native apps but I was willing to make an exception as the bulk of code I’d write would be fully native (as there is no way to write non-native apps on the Apple Watch due to the lack of a UIWebView) ↩︎

The Divide #4 - Getting into code

Episode 4 of The Divide, a podcast I co-host, has just gone live. This week, we discuss the routes we all took to becoming software developers. We take a look at how the programmer market is evolving while sharing our experiences of how we learned to code and we close with some musings and tips on where new coders might start to learn how to join the digital gold rush. Chris also shares a harrowing tale of how Captain Janeway wouldn’t look at him…

You can get The Divide from these fine outlets:

Don’t forget to leave a review on iTunes and follow us on Twitter via @PodcastDivide

Steve Jobs introduces the iPad at Death Star briefing

I’ve been re-watching Star Wars1 this weekend in preparation for The Force Awakens and a special episode of The Divide we are recording after Christmas. When it got to the Death Star briefing sequence towards the end of A New Hope, I was reminded of an excellent video that came out after the original iPad announcement with a mashup of that sequence and Steve Jobs voiceover. I had a quick look for it and couldn’t find it as for some reason it had been removed from YouTube2. After much searching, I eventually found a copy online but I’ve extracted it and saved it here to avoid it disappearing again in the future:

I absolutely love this video and wish I knew who created it.

  1. In Machete Order, obviously (although I’m tempted to re-watch The Phantom Menace after this theory that Jar-Jar is a Sith master…) ↩︎

  2. It doesn’t look like a takedown notice so maybe the account was deleted for some other video and this disappeared along with it. ↩︎

« Older Entries Newer Entries »