Maybe it's just me, but I find it much easier to understand exactly how a proposed solution works when it uses inline CSS. If the HTML and CSS appear separately, I have to look back and forth a lot to make sense of the whole.
Of course, when I actually implement it in my design, I prefer to separate my CSS from my HTML.
I wish the solution was presented in both flavors, side by side.
People have really short attention span these days. If I can't figure out what OpenLoopz does in 10 sec, I'm probably never going to use/sign up for it.
I'm in a slightly similar situation. Just that I'm in my final semester sitting for placements. But I don't really want to join a company or work for someone else's startup right away.
I'm actively looking for good ideas and people to start up with. While I'm not very experienced developer, I'm indeed capable of working on an MVP for testing out an idea, and taking things from there, if it all works out fine.
I would love to hear from you and see if we can make something out of this. You can support me a bit while MVP development, and if it looks promising, you can quit your job and we can completely concentrate on this thing.
Hm, so far I've only tested it in Chrome, I'll have to look into that.
I'm using the Google Translate TTS Api[1] - had to do some manual parsing + replacements to make some words sound right, but overall it's been stellar, especially compared to most other solutions. It also didn't cost a dime, which is nice.
