I do not know anything about game development.
I am trying to develop and android game but my problem is the graphic/display part.
I have the code for running the game already but my UI is just awful. Im just using textviews and buttons
I need a dice (3D if possible). but 2D is also ok..
Where should I begin???
Can anyone give me a really really simple code for making 2D games?
or any link out there that is very simple to follow?
Thanks
take a look at the lunar lander example or snake demo on google's developer website
For 2d take a look at andengine and its examples, it is an opensource 2d open gl es framework, its very usefull, coder friendly and it will work 10 times smoother than canvas on java...
I hadnt really found an app that allowed really good touch control with the pen.
One of my favourite drawing & animation apps is now in Beta (free) for android tablets.
Its Called TVPaint.
You can get the beta here:
http://www.tvpaint.com/v2/content/article/downloads/openbeta.php
Worth a look in my humble opinion.
Regards
A|C
Hello to everyone, i'm new of this forum ,
I wanted to ask you for a game engine and when it becomes necessary.
I was wondering if the games that have a simple logic and a 2D graphics is developed with a framwork types similar unity, etc..
For example, Pou (you can find that on the play store of google), you think it was done completely by hand or has been used a Game Engine?
Also, you know one GE that is completely free for android / ios / wp where i can, according to the license of that, market my product?
Thanks
AndEngine is great but it's not necessary to use an engine: http://www.raywenderlich.com/12065
I suppose if you're project is a little bit bigger than TicTacToe or similar and you want to use scaling, rotation and so on you shouldd really use an engine!!
I don't like AndEngine, I use LibGDX and this one is really great!!
Regards
If you are interested in native Android game development, you may take a look at this:
https://sitoberger.de/wiki/doku.php?id=getting_started
I wrote a little game for android and as I had a lot of problems with the gradle build system, the OpenGl and jni stuff I decided to share my work and experiences with you.
This little 2D game engine is designed to be very easy to use. You do not have to deal with any OpenGl or android specific stuff.
It supports all the basic functions a game needs (displaying graphics, motion, sound, the google play games services...)
Of course your can also take a look at the build system set up and so on to use it for other projects. I managed to get Android Studio to interpret native code but still using the Android.mk and Application.mk file with all of it's possibilities.
Feel fee to use this project for any kind of non profit projects. It is absolutely free!
If you have questions or any other comments/suggestions, feel free to ask them.
I am very excited what you will build up on my work
nice.
why not upload it on github for better visibility ?
Caution: Android P Developer Preview 1 is for app developers only and not intended for daily or consumer use. See the release notes before installing it on your device. Enrolling in updates using the Android Beta Program is not supported in Developer Preview 1.
Support should be in Dev preview 2. It's for app devs now and not intended for public use yet.
Can't wait to get it through android beta program..
Thanks for reading
John
Support? What do you mean support is included in dev preview 2?
I ran it for a while and it's completely fine to daily.
Its for app devs it's not really to be used by people yet.. it's no daily driver if it was you'd still be using it.
Android preview 2
This first one is easy. Every year Google releases a new developer preview of Android at I/O, and Google's own schedule says we'll get a new developer preview in "May," the same month as Google I/O. A new preview of Android P is pretty much a lock. The real question is "What do we expect in the second Android P Preview?"
More Material Design 2
The first Android P preview arrived in March with a big UI overhaul. There's an all-new notification panel and quick settings, a new main settings screen, and lots of redesigned system UI components like the volume interface, text selection, animations, and dialog boxes. In the past few months we've also seen a whirlwind of UI changes from Google in other products, with a new design style appearing in Gmail.com, Chrome in its Desktop, mobile, and OS varieties, the Google account interface, Google Pay, the Android Developers site, and the new Google Tasks app.
All of these redesigns could loosely fit under the same overarching design style, which feels like an evolution of Google's current "Material Design" guidelines. The new design doesn't have an official name, but internally at Google it has been called "Material Design 2" and "Material Design Refresh." Whatever Material Design 2 ends up being called, at I/O we expect Google to formalize the new design style, publish design documents, and have several developer sessions covering all the new changes.
Google likes to keep the I/O schedule vague before the keynote, but there are a few sessions that suggest Google will talk a lot about Material Design 2. One session is titled "How to incorporate what's new with Material Design in your code base." Another session will cover "how UX researchers helped test, refine, and evolve the latest Material Design guidance." I'm going to interpret mentions of "what's new" and "evolution" as hints of Material Design 2 news.
In Android P Preview 1, there was a pretty clear clash between newly redesigned screens and old interfaces that haven't been touched yet. In Preview 2, hopefully we'll see more parts of Android redesigned so we have something approaching a cohesive OS.
Gesture navigation
Android borrows a lot from iOS in this round of updates. In addition to iPhone X-style notch support, Android is apparently getting gesture support. This feature was seemingly leaked by Google itself, which accidentally posted a picture to the official Android Developer blog showing a navigation bar we haven't seen before. The home button was a pill shape instead of a circle, the back button used an older design, and the recent apps button was missing. This was Android's in-development gesture UI.
There's a ton we don't know about gesture navigation, and it's clearly still in development from the screenshot. While it seems inevitable it will come to Android, we can't guarantee it will be ready in time for Android P Preview 2. It certainly seems like a major change for Google, and it's something the company may want to release in beta so people can wrap their heads around it and offer feedback.
Google Assistant "Slices"
The first Android P Developer Preview contained a new "Slices" API, and we're still not sure exactly what it will do. The Android P developer docs say a slice is "a piece of app content and actions that can be surfaced outside of the app," but that's pretty vague.
Sebastiano Poggi from the app development house Novoda has been diving into the Slices API since release, and he thinks the most obvious use for slices is for apps to display their own content inside the Google Assistant search results. The UI with Slice renders currently looks very unfinished, but the layout is similar to a Google Assistant reply. Poggi has built a whole Slices demo app showing how a Google Assistant interface might work. One app would be a primary "Slice Host" (a Slices-aware version of the Google Assistant) and many other apps would be "Slice Providers" and offer up information to display inside the host app. So imagine asking the Google Assistant (the Slice host app) for Infinity War movie times, and instead of displaying search result info, users with the Fandango app installed (a Slice provider) could provide custom UI for the Google Assistant that would let users quickly buy a movie ticket.
Since Google will need app developers to build a Slice capability into their apps for this to work, the company needs to come clean about what the Slices API is and how developers should use it. Google's largest developer show seems like a good place to do just that. Again, the I/O schedule is very vague before the keynote, but the talk "Integrate your Android apps with the Google Assistant" might have something to do with Slices.
I went back to O for compatibility for one app. It's completely stable enough to be used as a daily and no amount of regurgitated release notes will dispute that.
Why don't you flash it for yourself and find out? It's not exactly rocket science on a pixel.
APIs will be final in the third release.
Android gingerbread walks into a bar.. drunk iPhone 6 throws a punch but misses.. Android gingerbread laughs and says you have no idea where my touch area is... But would you like to know...
Abort thread
Worst thread, evar!
What about Thread West?
Technodude2504 said:
Caution: Android P Developer Preview 1 is for app developers only and not intended for daily or consumer use. See the release notes before installing it on your device. Enrolling in updates using the Android Beta Program is not supported in Developer Preview 1.
Support should be in Dev preview 2. It's for app devs now and not intended for public use yet.
Can't wait to get it through android beta program..
Thanks for reading
John
Click to expand...
Click to collapse
I've also used the preview on my Pixel pretty much like ChongoDroid and it worked pretty flawlessly till yesterday, when I came back to Oreo after having a bootloop because of a Magisk mod.
Heck, the Android Beta Program pop-up on the actual preview says it's also for Android enthusiasts.