alance

Hey that's so nice to get a bit of support. Thank you.

Yeah, I feel like whatever it ends up looking like, it's going to have to be kept super simple/accessible.

Wondering about the traction problem too - but I guess, there's no real hurry...

Why not just make it non-gender specific? The female pronouns and imagery really distracts.

Clickable:

http://alouy.com

http://alouy.com/blog/introduction.html

http://baby.alouy.net (u/p: ned)

Just released a spin-off of an open source project that I've contributed to for a few years. Still scratching my head trying to get some traffic. Create and manage issues/tickets via email, web, CLI or API. Very mature web interface. Very customizable. Any questions, fire away.

Intro to the features:

http://alouy.com/blog/introduction.html

Demo, user/pass: ned

http://baby.alouy.net

Well it would seem that the logical next step is going to be giving it a way to provide permanence to the data. That generally means online storage, but there might be other ways that are more in keeping with your offline approach... or maybe you could give the user an easy to remember token that they can use to fetch their todo list from another computer. I like the shopping list aspect of it. I would focus my energy completely on the usability side. Keep optimizing for convenience.

I've just launched a todo list sort of an app too, but it borrows heavily from open source components, much hairier, different audience to yours I suspect (alouy.com).

It's might also be worth checking out allocPSA.com, also open source, and has a similar ticketing email gateway thingo... and a little tiny bit more functionality. (I'm very biased though :-)

Huh. I guess that does clang a bit. I suppose the more frequently used approach is to sell sell sell, raise expectations, and then drop the curtain and reveal the pricing.

Thanks for the tip, will think about how I can re-work it.

OK. I'm not accustomed to that level of optimism :-) But I see what you're saying.

One API coming up.

I'm happy to answer any technical questions about the app. It's pretty boring though, LAMP stack, jQuery.

The other thing I would kill for is any ideas on how to market this. How to market it, and to whom. I can run around to all the local creches and nurseries with flyers etc, but in terms of online marketing... I don't have a lot of ideas.

Thanks Yunus. The design is definitely pretty bare ... TODO.

I'm not so sure about giving it APIs, I think the target market will be mainly non-technical. But I suppose given an API, the application could perhaps be leveraged in ways that I cannot anticipate right now. Interesting idea, thank you.