Start with Why
But as it happens one starter repo and few hello-worlds later I wasn’t so sure about my reasoning anymore. Don’t get me wrong the Electron itself sounded and looked great, but the fact that it’s used to write GUI apps for Windows, Mac and Linux just did not stir up any enthusiasm in me. Not a very good sign when it comes to passion projects. So I started thinking what would work for me the best. Enters: React Native.
Few year back I had a idea about a simple quiz app. I even sketched out some visualisation and gave it a try codewise. But it never took off properly. I decided that the end of the year I would focus my off work coding to learning React Native. Udemy happened to have their once every other week megasales on so I bought Maximilian Schwarzmüllers course React Native - The Practical Guide as a learning material.
The next day when I was commuting to work on a buss watching the newly purchased course I wondered when I would have the time to see this project through. I also have the once again started blog and tons of stuff to code at work. How could I make it more appealing for myself to commit to a yet another thing. And then it it came to me. I’ll make a series of blog post documenting the project and about the progress.
What happens next
Well that’s a good question. I think I want to make a proper plan that can then be executed. I have the idea and some visuals already existing so I get them documented and then see what the minimum viable product would be. After that it should be fairly easy. Just code. The documentation will be at least first stored with the code repository. And yeah, this is a learning project that I’m going to use as a reference on what I have done so of course all the source code should be accessable via internet. There for it’s only logical (all hail Spock) that the repository will be located at my Github-profile. I’m still sticking with my original publishing schedule of at least one post per week so maybe many of the post in the coming weeks wil have React Native as a topic.
The end of the year is a bit hectic at work so I can not honestly say if I have the time or the energy to get stuff done by then. But as a driving force I want to set myself some sort of goals and one of them should be that the documentation and a blog post about it should be ready at the end of this month. Maybe for learning and execution I will allocate 3 months so that there should be something ready at the end of the January. But this can change depending on various things. After the following few weeks I will be wiser and can have a propper estimate about the schedule.