The To-Do List

This seems like a pretty big project to me. So big, in fact, that I’m ready to bring in outside help: I’ve already contacted an illustrator and asked if she would be willing to do the illustrations, should I send her a proof-of-concept that she finds convincing. The answer was a “yes,” but a tentative one.

So, outside of the ‘simple’ act of coding, I see several things for me to be working on:

  • Defining what a ‘success’ will be in this project. It has to be more than just a working app, as I don’t think I can afford to pay an illustrator just to prove that I can make the app. And I certainly can’t expect her to work without some sort of reward. What are we working towards?
  • Deciding if this thing is going to cost money? That’s obviously a subset of whether or not I want it to make me money, or if I’m doing all this just to prove that I’m cooler than the next guy. (Still a worthwhile goal, but is it enough?)
  • Researching how to get my app in front of a few eyeballs. I get that it can get lost in the Play Store, but how do I get the people who would be interested in it to see it?

I genuinely love the idea of seeing an idea that I had realized. Sure, it’s not something physical in the traditional sense, that I can frame and put up on the wall. But, nonetheless, it would be something I could point to and say “See that? I had that idea and I made it happen.”

On the other hand, I sense that success is going to require more than just a finished project. And the idea of marketing my idea, of being forced to try and convince people to look at what I made, well, that’s the part of this project that I’m looking forward to the least. Forget the tedium of trying to figure out why my code isn’t doing what I think it should be doing, this will be the hardest part of the project for me.

And that means it’s the part that I need to work the hardest on.

Advertisements

The Vision

The vision, I think, is simple: an app that tells children an entertaining story, but in an entertaining way. There are a lot of story-telling apps in the Play Store, but few of them are what I would give my kid. They’re basically videos that ask the kid to press the button for the next page.

I don’t know how you read to your children, but that’s not how I read to my children. If they won’t sit still for me, why should they sit still for a device?

What I’d like to build is an app that tells kids a story the way I would, or very nearly. I would love to be able to have the app read the story wrong and respond to kids correcting it (“No! He’s not a horse! He’s a boy!”) But I don’t think that is within my reach as an amateur programmer.

Telling children a story and then becoming increasingly — and comically — frustrated as they keep touching the things in the pictures, now that is something I could do. (I think.)

Imagine for a moment that you’re basically passively consuming a story and you touch the funny picture of a cat. The narration stops for a moment and says “Yeah, that’s a pretty strange picture of a cat. I bet that cat is having a bad day.” And then the narration picks back up again. I don’t know what you would do, but I would touch other things, what does the narrator say?

If I touch the cat again, will the narrator do it again? This time he says, “We talked about the cat already, come on, let’s do this story.” I try it again, of course. In a voice that is so comically frustrated it sounds more like the Cookie Monster than anything else, the narrator complains: “Enough with the cat! I am trying to tell a story here!”

I think my kids would eat that up. And, of course, I’m banking this project on the idea that other kids would eat it up, too.