dbldbl - My First App

I decided to put the source code for my first app onto GitHub.

Back in the heady days of 2012 and 2013, I decided that after 8 years of doing front-end development that I wanted to become an iOS developer.

dbldbl (Double Double) was the first app that I ever released onto The App Store. It was a pretty simple little app that used the Core Image frameworks to simply set some filters on two images.

Considering that I came from an ActionScript 3 and Javascript background, getting dumped head-first into a C based language with memory retain and release cycles was one heck of a metaphorical hill to climb.

I ended up having to teach myself Objective-C, C (for Core Image manipulation), Cocoa, Blocks, GCD, Storyboards, Mobile Design, Code Signing and the list goes on and on and on.

There's a lot of rough edges on the app, it's pretty clear that this is someone's first public release.

The application did pay off though, I managed to make enough money off of it that it paid for a few years of iOS development access and it gave me enough confidence with iOS/Cocoa to ultimately get a job doing iOS development full time.

Plus I created some really great images:

Words by brett ohland

Hot/Cold - Oh Look: A Repo.

I decided this morning that there's really nothing wrong in posting the source of the app up on GitHub for the time being. Really, it's in the middle of heavy development and I've never really developed anything in the open before. What's the point of keeping a dev blog if I can't reference chunks of code?

The repo has been created

Another thing that might be interesting is that I think I'll be linking directly to specific commits in order to give a bit of historical context to certain posts. Not sure if I'll keep doing this but it seems like an interesting idea.

It's that awkward first set of check-ins

Mattt over at NSHipster had a great post on Multi-peer connectivity that really make me interested in making this application communicate both ways. The 'seeker' would only get "HOT" or "COLD" verbal commands but the Hider could get a distance measurement.

Taking it the next step you could even have multiple Seekers looking for one Hider and all of their distance measurements could be displayed (Or just show the motion tracker from the movie Alien to really freak them out).

Words by brett ohland

App #1: 'Hot/Cold' App Outline

The first and simplest app idea that's been rolling around my brain uses iBeacons. I attended a couple of sessions at WWDC 2014 about them and have been really interested in playing around with them ever since.

So here's the app idea (it's kind of a joke): You have two iOS devices. One is the 'hide' and one is the 'seek'. The 'seek' device does nothing but yell HOT! HOT! HOT! COLD! COLD! as you get closer or further… I didn't say it was a good idea, just that it was an idea.

(IAP idea: Novelty voices?)

Getting the 'seek' app up and running should be pretty trivial, Apple has their Air Locate app that shows just how simple it is to listen for iBeacon signals. The neat thing is that with one UUID there could be multiple people/apps looking for one 'hide' app instance.

On the 'seek' side of things it gets a bit more interesting. The idea for the app would be for two kids to be using them to have a kind of nerdy hide and go seek game. I was thinking that the hide app could say some funny things or give updated information on how far the seek app(s) are away from you. Since iBeacons are supposed to be a one way communication path (broadcast only) that would mean that I would need to look into being both a iBeacon broadcaster as well as an iBeacon receiver. Is that possible? I guess we'll see.

Step one's going to be just getting the application scaffolding up and running and starting with a basic 'one is hide and one is seek' prototype.

Words by brett ohland

Where Our Hero Declares Himself

Plans. Let's make some so that we can all look back and laugh at them.

My goal is to keep a bit of a running dev journal for three iOS applications that I'm hoping to build in the near future. Let's see if I actually keep up with it, shall we?