Updated: May 25
This entry was imported from Group's former blog on Blogger written in 2020
1 child and 3 years later I finally have managed to submit the first version of Groups to both Apple's and Android stores. Groups first began as a D3 experimental project. At the time I was struggling to remember everyone's names and faces on my team, which included people from different countries who kept coming and going. My company's corporate site did a poor job at showing this so I thought that there was a need for it. I started framing the app with CodenameOne, which was a great framework for cross-platform mobile development at the time (2017). I still love CodenameOne, it's functional and it produces really tiny packages (app is 3MB on Android and 7MB on iOS at the moment). It does lack some features, but they do a good job at keeping up with changes so ideally these will be there soon. Besides, it also allows you to embed native code where the framework can't reach, which can't be said for every mobile cross-platform development framework out there.
In August of 2018 my grandfather passed away and all the family got together for the funeral. My grandfather had 8 siblings so I found myself in front of loads of people whom I perhaps was supposed to know but didn't. Somewhere in my subconscious I put 2 + 2 and thought that this might be a good use for Groups too. In a way, I feel that I've needed all this time to come up with the final idea. The app is now a subversion and visualizer of both organigrams and family trees. Users can join and create "groups" that are stored on the cloud, view, submit, and get changes. Groups can be reverted to a former state. Trees can be seen in relational and hierarchical views. Users can email themselves full chart captures to perhaps be shared in quick presentations. I find it very useful for myself, since I now can quickly glance at my organigram before I join any meeting and feel confident I'm not making any mistake in regards to people's names and roles