How open is open?

Good afternoon all!

I've got a general question regarding the Ouya that I hope the community will be able to answer for me.

Essentially, here at Spearhead Interactive we develop online 3D visualisations for B2B sectors, distributed via web or mobile devices. Everything from component visualisation as a sales / R&D / Training tool, through to full architectural models for regeneration planning/BIM etc...

For some of our more security-conscious clients, I'd like to propose that we could provide a stand-alone, secure solution for them to view the end-product in-house, and this is where I hope Ouya could come in.

What I would like to be able to do is install the final APK file onto our own branded front end loader on a specific client by client basis. No connection to Ouya Marketplaces or any other Ouya Service, merely connect a Ouya box to our PC, load in a custom Spearhead Interactive front end and install the APK files as required. The Ouya console would then be handed over to the client to use as required in a 100% offline capacity.

Is this something which would be possible, or does this contravene the terms of use for the console? I'd be more than happy to have an Ouya screen present whilst loading the custom front-end if this is necessary.

Thanks all. Looking forward to your responses - appreciate any assistance you can provide.

Regards,
Dan Riley, 
Director, Spearhead Interactive.

Comments

  • jayderyujayderyu Posts: 110Member
    I could be wrong, but as I understood the talks. You are allowed to take take the open source OS and modify it. You are allowed to put on a new version of the OS. You are allowed to hack the hardware.

    You are not allowed to bypass the market place security aspect of the Ouya, or any parts of the OS that Ouya uses to secure the financial and user accounts. Also the Ouya OS uses API's that are closed source that can't be circumvented. 
    Question the paradigm you believe in
Sign In or Register to comment.