I think anyone with hardware or Android game development experience should be healthily skeptical of the tall promises and minimal explanation coming out of this Kickstarter. I love a good chunk of optimism as much as the next guy who loves games, but the fervor seems to really be distorting reality and setting up an inappropriately adversarial tone to these HN discussions.
But to reply to you--their pitch may be "working" in the sense that they're getting pledges, but the amount of the pledge totals is pretty clearly not going to generate a profit. Without the app store, they're not going to be making money. Without developers, they're not going to be selling anything in their app store, which you need to have populated with games by early 2013. Six to nine months is already not a lot of time to put together a game, so you really, really want to get developers excited for and working on your stuff right effing now.
That's where they're falling over. And it is literally-literally as important as getting the consoles to consumers.
Since the hardware is not released yet they should be showing developers how to emulate as-close-as-possible to this on a regular PC (including which commodity joypad you should be testing with) so they can be confident that their game will only require minor tweaking when the final hardware is released.
OT: It seems to be very easy to get HellBanned from HN which makes it seem pretty cruel. You only need a handful of people not to like your first few posts to effectively kill your chances of contributing to the community and potentially wasting a lot of your time.
Perhaps a system like , you can only downvote comments from users under a certain karma threshold if you also flag them as trolling/spam
I'm sure their wet dream for this is to get an exclusivity deal for a big juicy AAA title.
edit: [1] http://www.appbrain.com/stats/libraries/details/libgdx/libgd...
If I develop a game for this, using LibGDX seems like a no-brainer because even if this is a total flop I can at least pivot it into a PC game.
Well, how deep of an answer were you expecting on twitter?
Instead of trying to infer what the 140 character limitation suggests, maybe email them?
And, sure, most developers won't put time in to customize a game for a specific platform, but I'd personally be ashamed if I didn't make it good on every platform I say I support. If it isn't done well, I'd rather not do it, know what I mean?
I'm not even sold about supporting the Nexus 7 I've got, because I don't know yet whether I can make it awesome enough. Trash-flood games ruined XBLIG and make finding worthwhile games on the iOS App Store and Google Play way harder than it should be. I won't contribute to the pile of crap.
I'm not a games programmer , but I would certainly be interested in building a small simple game for this and having at least a demo ready for the console launch.
It's interesting that you mention LibGDX as something that could work well here. Let's say I want to build a game that is designed around joypad control would my best bet be to build a game with LibGDX using the lwjgl backend (for PC) and plug in an xbox pad to test the gameplay? What about testing performance?
Slightly OT: LibGDX seems to have relatively scant documentation in terms of examples of significant working code so it is difficult for me to think about how to best structure the code for the engine. Are there any books that cover this specific to LibGDX? I can't find any.
The bigger issue right now, as far as libgdx on Ouya would be, is that libgdx doesn't support controllers yet. But badlogic (who also replied to you--he's the main dev behind libgdx) seems to have some ideas on that one. I wanted to start in on writing a gamepad extension to their input system last night, but pulling down a clone with git-svn took most of an hour and I ran out of time. =)
One thing I noticed when comparing libGDX to XNA was that the basic game framework that you can extend from in XNA has 2 "tick" methods in it's main class, update() and render() (or something to that effect). Also the Java library "slick2D" follows this convention. This makes it simple to seperate out rendering code from logic updating code.
LibGDX on the other hand only provides a render() method which confused me a little. Should my render() method be handling logic updates? Should it call another method that does, but check time deltas on each loop to decide whether it should run, or should game logic happen in it's own thread?
it definitely does build, otherwise jenkins would scream at me all the time :)
We have our reasons to use SVN for the time being, externals being one of them (git modules don't work for our setup), tooling support being another one. We are eager to give people commit rights, provided they follow a small set of rules.
This does not necessarily help you with your dev process of having lots of local changes that you throw away. But that's something git-svn should be able to solve.
Ping me via e-mail at contact at badlogicgames dot com.
SVN is functional, simple, and it works.
If you're doing OSS contribution right, you'll spend far more time talking and coding than you'll spend poking at SCM, and you won't be maintaining a large fork or poor hacks that upstream doesn't want to merge.
Discuss early, merge often.
The completely non-standard gamepad with display is a terrifying hint that Ouya is trying to do their own thing, not build a good solid ecosystem device.
The Kickstarter feels very consumer-focused, which is great but they still need to have games to sell to people.
It raises the question of how this kind of project should be handled. Should they have developer docs ready before fundraising? In the end, that's what it would take to answer your questions.
I'm not taking a side on that, it's quite possible that the answer is "Yes, they should have that level of documentation ready."
Just thinking about what's best for this kind of Kickstarter.
Either the funding is "to develop the platform and make it available for developers to write games" or "to get the platform we've developed into production so that games written for it will have a wide audience."
If its the former then there is a much bigger gamble here, they may not be able to make it compelling enough to actually be a competitive game platform. If its the latter then they should have the 'big' pieces in place software wise and the remainder might be just refinement. Reading their collateral and listening to their pitch I think it is more if A than it is B but I would love to hear differently.
I keep trying to remember the DirectX guy who created a company to make 'game develoment for the masses' and then faded away, damn my aging neurons.
If they were pitching this for, say, Q1 2014, this wouldn't be that much of a red flag. That's plenty of time to get a dev SDK out for developers to have enough time to make something.
However, with less than 9 months to launch, they absolutely need an SDK ready, unless they're serious about only getting ports of existing android games. A 6-9 month dev cycle is on the short side for most quality indie game releases, but it's very possible to get good games made in that time.
I would bet that to a large extent this could be called a land-grab platform--"get in early or don't get in"--and that makes them particularly important to have well in advance.
When they have development resources that show me that they're taking developers seriously, I'll revisit it (and doing so is fairly cheap for me; I'm using the always-awesome libgdx, which has Android support already). But my initial experience has been pretty bad, and I'm questioning their competency right now to the point where I can't give them money.