hyung

- Adding a metronome, even at very slow tempos, adds good subtle variation.

- Starting from different points in the piece also provides a good subtle variation.

- Playing the piece at different octaves.

Looks nice! Have you thought about adding screenshots on the landing page (maybe one each for "Log Expenses", "Tag Expenses" and "Analyse Expenses")?

I think a lot of people would like to see what the app might look like before giving away their email address.

This question might be too broad, but how would you compare the infrastructure, English level, technical talent, etc. of Rwanda with other African nations?

I really like how you send a link to the game via SMS. May I ask which service you're using to do that?

This is what I do. Please feel free to contact me (details in my profile).

I think it also depends on the type of operations you're looking to hire. I've found that people with stronger skill sets (for example, engineers), are very difficult to hire for swing or overnight shifts, even if salaries are double or triple the daytime shift.

(I run 24/7 operations in Vietnam, I'd love to talk shop.)

A cross-platform game engine sounds awesome. But I wonder what kind of game can truly be write-once, run-everywhere, and considered "fun" on all platforms.

A few major challenges:

- Designing a game that is fun and intuitive to play with a wide variety of input controllers (touch, mouse, keyboard, joystick).

- Handling the entire spectrum of screen resolutions, from older iPhones to high-end desktop computers. The game would also probably need to work in both portrait and landscape modes.

- The QA effort alone could be huge. Testing on quirky desktop browsers or buggy Android devices alone could be a dealbreaker.

- I'd argue that the time spent trying to figure out a game design or technical workaround for a particular platform would be better spent focusing on one platform and making the game more fun. In my experience, trying to make a fun game involves a lot of trial and error and iteration, and I personally don't think I could do it if I also had to keep in mind multiple distinct target platforms.

I can envision a couple one-button games like Angry Birds or Tiny Wings possibly having a chance, but even in those cases, I'd argue it'd be better to nail one platform first and then incrementally add other platforms instead of spreading oneself too thin.

The pressure to censor content often comes from advertisers. A lot of advertisers don't want their ads showing up next to photos with even minimally offensive content.

(This doesn't explain everything for Google, but I'm sure it was a factor.)

At its core, our networking layer uses long-polling, but we added several modifications to attempt to keep the requests alive. We also drastically changed the timeout values based on testing directly on the mobile devices.

We found that vanilla long-polling works sometimes on iPhone and some Android phones. But it often introduces huge latencies, and it often just fails for no apparent reason on some Android devices.

I'd like to add that, in practice, socket.io doesn't work well for mobile HTML5 multiplayer games. We found that long-polling requests tend to get dropped without informing the mobile client.

Our solution so far has been to roll our own mobile networking layer, with redundancies and timeouts especially tuned for mobile.

Congrats Anand!

I've been working in the crowdsourcing field for several years now (our workers are from Vietnam), and can understand that the profit margins can be very thin for some of the more basic tasks.

Drop me a line if you're interested in branching out to Vietnam.