The logo changed since fossuser posted this comment. The older version of the logo had the "I" and the "M" joined near the top so it looked like "Fukme" instead of "Fukime".
It has the same vowel and consonant positions as heroku, too. I wonder how long it will take them to get to the top of a google search for "fukime". Right now it's a deviantART profile. :)
Parse is definitely more versatile and targeted to power-users that don't have time to implement server side ORM, user management, pushes & such. Very high-tech.
Fukime might be more like candy machine for prototyping and developers who want to make things happen quickly and just focus on client development.
Fukime f = new Fukime("your_app_id","your_app_secret");
// Count stuff across all your apps.
f.teller.global.increase("farms");
f.teller.global.count("farms"); // get global farm counter
How secure is this? Wouldn't the "secret" be stored as plain text in the binary?
Even then you could just put a breakpoint in the Fukime constructor and read the raw string?
Heck, even if the authentication step was 100% secure, what's stopping a malicious user from calling increase("farms") on a previously authenticated Fukime object? The Fukime instance is shown to have direct access to "global" variables, so the user wouldn't be limited to screwing with their own data.
This kind of logic belongs server-side (and this obviously isn't a server-side API, because the examples provided are for Android and iOS.)
To what end? I guess they could troll your "mobile app installation counter" if they really want to, but so what?
If someone wants to misrepresent how many times they've installed your app, there's nothing you can do about it. (They could just uninstall then reinstall over and over.)
Though... obviously they should only be able to mess with their own statistics, not the global statistics.
True that there's nothing terrible they can do when it's just statistics. The obvious solution would be to remove the global variables altogether, so that each user only has their own (from which the global versions are calculated).
That way, if the user was to do stupid things to their own variables, they could just be removed when calculating the global ones.
oauth would have request replay prevention or there could be some other ways of stopping the count fraud, but app_secret is probably always available in some kind of readable form. This is just an aspect of mobile security we have to live with. Facebook 3 party sign-on helps a little here because one could check requests server-side against valid temporary FB keys. But Fukime cow counter could easily do without those :)
I like these new hosted services for mobile apps, and believe this niche has huge potential for growth and monetization.
First these services need to convince users to be able to trust them -- to be in for the long run, and to do their job well. For me this assurance is missing on fukime.com -- who are they, why can I trust them and the quality of their product? Which is where I feel parse.com is one big step ahead -- being in the YC batch and having raised more than $1M makes me believe they are all in for it, and that they actually what they are doing!
Sidenote: I find it annoying to be asked to social share in order to get three others to sign up, as a prerequesite for getting into the beta (after entering my email).
It means "fuck me" (repeatedly) in Slovenian :) But I guess if Ford* can't be bothered to check it's car names that a small startup will be even less likely to do it.
If it's supposed to be Japanese, it would be pronounced key, not kai. I'm not sure if it even means anything, though. GIS makes it appear that フキメ may have something to do with fishing lures, but it's not in my dictionary.
This is the third mobile cloud platform I've heard about in the last several hours (Parse, Kinvey, Fukime) and it is something that I could definitely use. I am wondering, anyone know which one is the best to use? It may be early since they are all still in beta.
I'm sure some folks are getting lots of yucks from the name. Can you imagine being in a corporate IT job and trying to justify to management that the next project should be built on their platform?
