This is probably the smartest move. When I am dealing with someone who doesn't seem to understand what I am saying due to language barrier, I start dealing with physical communication instead however possible. It can look odd, and be sort of funny to witness; but it works a charm more often than not. There are just some things we all generally understand once the body becomes involved.
Would like to see a wrapper generator around C# libraries so they could be easily be loaded into node.js
That would make all sort of integrations between legacy systems with existing C# support libraries and newer lighter node.js projects work without jumping through crazy marshaling hoops.
Seems like a very interesting direction, embedding managed languages into JS.
From my quick run with the app, what I find lacking isn't in the events, but in actions: currently, it mostly notifies you (or others) about events.
It'd be more useful if it could also interact with the phone settings (for example, silence the phone at certain locations, &c).
Currently, this could be worked around by having an event launch SL4A that would run another script doing it; but this forces you to maintain a separate script for the desired action, instead of doing it at the same place.
The main difference is that you can write a JavaScript snippet that is pushed to your phone and executes.
The JavaScript can register on device triggers and you can control the logic to do whatever you like. You can code it to be very specific in contrast to other rule based platform which have to be broad to cover main scenarios.
You still have pre-coded recipes which you can choose and quickly configure and install, and one of the coolest things is that you can actual see the recipe's code and hack it to your own profit :)
Are you familiar with the Android Account Manager? [1] You can let users log in to your app with pretty much one click of an existing account. Since virtually every android user already have a google account signed in on their phones. It seems that using a google account would be the most obvious route for ideal user experience (no need to type in a new account you haven't before).
That's funny, I'm the opposite. I'm generally unlikely to sign up for any site or service that makes me create and record yet another username/password combo.
It seems there's a discussion on your forum now. [1]
Unfortunately, to chime in on the discussion one needs to log in with Facebook, which might keep a good chunk of those 'Please support something else' voices out. I know you wrote (both here and in that entry) that you plan to support other authentication methods. The reason why I post this is just to point out the flaw of asking the subset that willingly gives out their FB details in the first place.
