Origins I started JellyChip after playing some Pocket Rice with a couple of people from RMIT. I realised that an app that simple yet life-changing had a lot of potential to turn into a really global phenomenon, and kept coming up with things I wanted to change and stuff I wanted to add.
I had recently quit my job as a consultant to be able to focus more on app development during my free time, and I was looking for a new app to develop. I had a few ideas floating around, but most required really long development times.
These two factors led to JellyChip.
Development and philosophy Waterfall is dead, long live agile!
I've got a few plans and visions, but my only true design decision is to keep it fun and accessible. There's no design doc, but there are two lists; one for bugs, and one for features I want to add but think I might forget.
I want to make sure to play JellyChip a lot, and I've made my share of charity donations to school rides, and neutered several dogs. If something ever doesn't feel fun, I'll remove it. I believe that I can combine enough fun, accessibility and charity for this app to be a huge opportunity to save lives and change the planet.
I strongly believe that all good apps have an impact, and that all good apps make an impact regardless of if it's pre-determined or emergent. A messaging app is fine and dandy, but for many people it will ultimately become boring once you've got it figured out. It's like repeating the same thing over and over, or talking to the same person over and over... a lack of impact kills the fun.
For a charity app, I'd rather give the experience a more social angle. That also means I'm going to have to include some way for people to connect (or some other climax) so that they can make an impact together.
But if it's not fun, I'll redesign.
The future I plan on developing JellyChip until it's a finished complete app, with a large number of social features (with many charity gifts), gaming features and possibly custom charity gifts.
For as long as people enjoy and purchase the app, I will develop updates after the app is done.
Once the user population starts growing and a minimum time has passed, I will increase the team size to make features faster. I'm not very happy with large team sizes because productivity decreases as teams grow bigger, so I might just possibly sell it all to a social media giant.