Back in November 2014 I wrote about my attempts to create a Mobile App in Mobile App Part I.
Since then a lot of water has passed under the bridge – basically all of 2015. In short I stopped the mobile app development. I could just say “It was too wet to plow” and let it go at that. However I did develop the State Conference Web Page instead. We developed the State Conference Web Page as a responsive web page. That is, it would morph depending on the device footprint used to view the web page. In theory with responsive design Mobile Apps are not needed. And the jury is still out on that theory.
Of course, my 2015 contained many other events and experiences. But, they are a tale for another day.
Now that the web page is completed I’ve decided to give the Mobile App another try.
In my year’s hiatus Apple introduced Swift to eventually replace Objective-C. Since my two main problems last time besides TIME were Objective-C and the Storyboard I decided to eliminate one of my problems and try Swift. Wow, Swift is a modern language much more understandable, at least to me. I’ve been much more productive since I switched. I’ve developed a working, on my iPhone, Calculator App based on the Stanford University Swift Online Course.
My plan is:
- Complete the Stanford University Swift Online Course
- Develop the State Conference Mobile App in parallel
with a goal of finishing by March 31. (good luck).
My observations from the first blog have not changed significantly. Changes are:
- Use Swift and forget Objective-C. I have not found anything I can’t do with Swift yet and it much more intuitive, at least for me.
- The Storyboard learning curve is steep but easy to use after you’ve reached a certain point on the learning curve.