compose-samples VS filament

Oh, I’m sorry. I didn’t realize you already looked at those. Those should go into a Window Size file. You can call it whatever, I called mine WindowSize and WindowUtil. These files should be written once and used on all your apps. So design them with that in mind. You can call them in your main Activity file or anywhere else you need it. Here is a good example of using the code in the documentation inside a news info App. This is their main activity file [theirs is written in kotlin, but can be translated into Java] https://github.com/android/compose-samples/blob/main/JetNews/app/src/main/java/com/example/jetnews/ui/MainActivity.kt And here is their window size class files -- https://github.com/android/compose-samples/blob/main/JetNews/app/src/main/java/com/example/jetnews/utils/WindowSize.kt https://github.com/android/compose-samples/blob/main/Jetcaster/app/src/main/java/com/example/jetcaster/util/WindowInfoUtil.kt You should also go into your manifest file and put - android:resizeableActivity="true" or false [depends on what you want resized] In the application or activity section depending on isolation of activity or not.. And here is a YT video with good points - always code for device unknown. That way it wouldn’t matter the screen size, resolution, hardware config. Ext. -- It doesn't give much on syntax usage, but good insight info. Build apps for foldable, multi-display, and large-screen devices (Google I/O'19) https://youtu.be/8uQEzv3upy8 Considering you are just starting out and getting the hang of things. I would look at all their files in the App source code above and see how the classes and functions are being used. Download the source files and tear it apart. The best way of learning any coding language is looking at code and playing with it then going back to the documentation to further understand it. I hope this helps. Good luck.

There is also a similar framework for Android called Jetpack Compose which I will look into next. I have high hopes that these will be the future of native development.

Java still works for 99% of things, but Google officially declared Android development as "Kotlin-first" back in 2019 and it's definitely where the new/latest stuff happens. For example: Compose is Android's new declarative UI framework (similar to React) and it's Kotlin-only.

The "new" way: Compose does everything in code via composable functions. You mentioned your background is in web development; Compose is very much like React for Android UI. It only recently reached version 1.0 so resources can be sparse, but it is very much the "future" of UI on Android.

One thing I noticed is that running on real device the UI is somewhat less laggy. I found JetNews Android Sample App which contained the use case similar to mine. I will try to make changes as per it specially moving the selection and deletion logic to suspend function as done in the example and let's see whether there will be any performance improvements.

Check out some demo apps with Jetpack Compose https://github.com/android/compose-samples. You could work on building them and launching them. You could also work on editing the code and adding/changing features. You should probably pair this with some intro to kotlin tutorials.

Jetpack Compose ftw

Jetpack compose is built by the Android team and is probably what you want to go with. There's also a compatible library by JetBrains if you want to target other platforms with the same kind of patterns/development approach, but it's still early in its life cycle.

Google Filament is a C++ engine with Kotlin bindings for Android. Very high quality code on both sides https://github.com/google/filament

You can make a game engine in Java/Kotlin. But, that doesn't mean you should. For professional work, your choices are pretty much C, C++ and Rust. https://stride3d.net/ is a good counter-example to my claim. But, the far more common method is a high-level language interface over a C++ implementation. https://github.com/google/filament is an awesome example of a Kotlin interface over a C++ implementation. Unity is C# over C++.

You can use Filament (https://github.com/google/filament). It has a comprehensive PBR material system, see the docs here https://google.github.io/filament/Materials.html (visual summary of the main properties: https://google.github.io/filament/Material%20Properties.pdf).

What about filament ? https://github.com/google/filament

Does filament support Embedded gltf files? · Discussion #4240 · google/filament (github.com)

What about using Filament? It seems to have been designed for this purpose.

The filament rendering library from Google has a full PBR pipeline implementation that you can hack on and see where theory becomes practice. It also provides an excellent in-depth discussion of the library implementation as well as why particular choices were made in the library.

Just getting back into Android dev myself. Rapid workflow stack: Jetpack Compose / Kotlin, Material Design UI kits and Stripe / Firebase Cloud Functions. The emphasis on being able to go from idea to release in the shortest time frame. Target being Fast Mobile Commerce

https://github.com/android/compose-samples

https://material.io/resources

https://firebase.google.com/docs/use-cases/payments

Other than that I'm excited about next-gen low latency audio library Oboe and real-time physically based renderer Filament

https://github.com/google/oboe/tree/master/samples

https://github.com/google/filament/tree/main/samples

Best of Luck ;)

Filament is being actively worked on every day, your best starting point would be the gltf-viewer sample app (in Kotlin): https://github.com/google/filament/tree/main/android/samples/sample-gltf-viewer