Captain Danko’s JavaScript Lab — Code Smarter with Tutorials, Frameworks & Dev Insights

September last year(2015 I released my iOS app, My Day To-Do  and the following December I released the Lite(free) version , which is missing a few features from the paid version. At this point, both versions have a different code base i.e. seperate repositories and when I add a new feature to the either of them, I basically copy and paste the code from one place to the other. I know this method is horribly prone to errors, right? well, I wanted to release the Lite version just before Christmas and since I started working on it a week or two before the holidays, I could not afford to invest time into finding out best way to go about it. However now that I plan to release another paid but limited and cheaper version of My Day To-Do, I am thinking of doing it right this time.  Introduction Since 2013 my version control of choice has been Git  and I have used it on all my projects ever since including My Day To-Do family of apps. I always knew about branches in Git but...

This is one of those achievements that had me yell a big "YAYYYYY" when I had it working, even though it is not complete at this stage. After coming across some hurdles, I finally managed to deploy a web demo for my iOS app  My Day To-Do  that anyone with a mobile or PC can try. In this short post, I will talk about my motivation for it as well as shed some light on my overall solution and I will conclude this post with my thoughts on this approach and what I think about it, in current day and age.  Motivation  My Day To-Dos has both a free and a paid version and the distinguishing features between the two are (at this stage) weather summary selecting the language the app talks in The above features are only available in the paid version and I wanted to give any prospective users a feel for what these features are like. Solution I have already written about the unique way in which I built my native iOS app i.e. Html5 for UI and native...