Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK’s documentation. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the “upstream” source code available from the Android Open Source Project. Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations.įor this reason, the Android Open Source Project is both the reference and preferred implementation of Android. To be considered compatible with Android 8.0, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference. A “device implementation” or “implementation is the hardware/software solution so developed. The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in RFC2119.Īs used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 8.0. It has behaviors like construct2 but even better defined, the templates gets your hands on water while developing is faster thanks to event system.This document enumerates the requirements that must be met in order for devices to be compatible with Android 8.0. Then I found that this was just made by only one person, and the huge community behind him, and G DevApp! all open source, MIT License, Exporters to HTML5 and PC. It was just perfect, I made good and complete prototypes just like with construct but without actually paying!Īnd surprise! you can make games for pc with high performance.
However since I was finding a drag and drop engine ( Thanks to the facility of C2 ) and the “export-what-you-want-without-fees” one, I asked to Mr.Google to leave things clear.Īnd here, ladies and gentlemen, is how I found the Great Editor Ever, G Develop. They just made a really ugly interface, but it seemed like is really getting support and the modules they have look like you can trust them. I can´t talk to much about this software because I didn´t test it enough but, the more I investigated the more I feel uncomfortable. Construct2 was good enough to make me to choose it, but they want you to pay for something that they even support. Just amazing, but then… Licenses… oh licenses and the poor support of exporters ( they actually tell you that they don´t support third party exporters, however, there are solutions tutorials there to do that). The simple engine event took me the first day to learn it how things work. I tried the free version and it was the first time that I actually make a demo game. So here´s where I run to Construct 2, an easy, robust and complete drag and drop (Nothing like GMS) game engine with its own visual editor. Just weeks later they closed the site to upload your games, eliminating that way thousands of games. I though it was just my fault but found that error windows on the most GM projects. At first, it was like: finally! an engine with drag and drop capabilities and easy language to learn, but then errors appear like it was waiting for a single action to hit your project in the proud. A year later, I wanted to make big projects like those whose names you know. I´ve made my first prototype in two weeks. When I was 12 years old I first begun with Game Maker 8.1, Yoyogames forum was a nice place to share your creations. First of all: English is not my native language so feel free to correct me