babydots VS ipfs-lite

I write Android apps for my baby-now-toddler.

At a few months old I created BabyDots [0] as she loved this YouTube video of dancing dots [1] which really settled her when she was upset as a young baby.

At over a year old I added BabyPhone [2] to let her talk to family and have them “talk back” to her even when they were not available. I missed the timing on this and she didn’t enjoy it at all until literally this week when she started talking back to the little baby on the other end of the phone.

At 18 months old I made a book-building app [3] that takes titles of pages on Simple English Wikipedia, and creates pages for a book that can then be exported as a PDF and printed (or viewed on the phone). It also has a website [4] on a free heroku dyno which definitely won’t take much traffic. This was because when she gets interested in, e.g. planets, I don’t want to have to order a book on planets, I want to print one out 5 minutes later to keep her interested.

One of my proudest moments was at my new job where a team member said during our first standup “I have your baby dots app installed and although we don’t do screen time, the music really sooths our kid during nap time!”.

[0] - https://github.com/babydots/babydots

Baby Dots v. 1.5.1: Soothe and calm young babies

The README.md seems to explain quite well:

IPFS Lite v. 2.5.1: IPFS Lite node with modern UI to support standard use cases of IPFS

Basically, the whole point of this exercise was to avoid needing to rewrite an IPFS implementation for Android. Last night, I found an Android IPFS implementation that someone else wrote. (Believe you me, I've been looking for days! I finally backtraced a project from the Play Store to find the damn thing. My searches for things like "Android IPFS Client", etc never turned up this gem. Everything else is built atop of the assumption that you'll be running the go-lang ipfs node)