compose-samples VS filament

Source: JetNews sample app

Your concept of Android development looks to be stuck in the 4.4 days. Jetpack Compose and its declarative UI is how modern Android apps are developed.

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

>Hopefully Flutter will fix that because the difference in usability is night and day. It's just a shame the Dart ecosystem is so dead.

I don't see how the difference is night and day when they both use declarative UI's. Whether you use Jetpack Compose/Kotlin or Flutter/Dart is really up to your objectives. As for your claim that the Dart ecosystem is dead - I really don't get that, since Flutter/Dart is the #1 cross-platform development environment.

Voyager is a multiplatform navigation library built for, and seamlessly integrated with, Jetpack Compose.

This repository contains Jetpack Compose components for the Maps SDK for Android.

The official documentation provides a comprehensive guide on the basics of Jetpack Compose, components, layouts, theming, and more advanced topics.

Apparently Jetpack Compose is an Android copy of SwiftUI?

https://developer.android.com/jetpack/compose

Only two HN threads with comments: https://hn.algolia.com/?q=jetpack+compose

If you want to take a look at code, we have the Jetnews sample app that support different screen sizes. And Jetcaster also implements features such as table top mode.

check this out : https://github.com/android/compose-samples/tree/main/Crane

So I would say that instead if learning everything from Android SDK, you should just set a goal to create some app. Learn about Activities, their lifecycle, layouts (or Compose if you want to be more up to date). Try to implement your app based on this. Then improve your app using Fragments and their lifecycle. If you truly want to understand Views, which are essentially the building blocks of Android UI then I would recommend implementing your own custom View, which will have completely custom look - it is cool thing to try and you will learn how it all works inside.

Filament - A modern, efficient graphics engine suitable for real-time rendering, link: http://google.github.io/filament.

I'd like to share Thermion, an open source 3D rendering toolkit I made for Flutter and/or Dart.

This came about when I needed a 3D renderer for a Flutter app I was building (https://polyvox.app). At the time, the only off-the-shelf option was to embed Unity, which wasn't ideal for a few reasons - unstable build process, compositing and transparency issues, and licensing uncertainty, just to name a few. In any event, frankensteining Unity (C#) together with Flutter (Dart) didn't seem like a great solution.

After browsing for alternative renderers, I discovered Filament (https://github.com/google/filament), an open-source, cross-platform Physically Based Rendering engine from Google. I initially only wrote some simple bindings to embed Filament inside a Flutter Android/iOS app, but have since added more functionality, and have expanded this to cover Windows, MacOS and Web (there was Linux support at one point, too, but I haven't been keeping up with it I'm afraid).

Last week I published the first Thermion release to pub.dev (https://pub.dev/packages/thermion_dart), and with that milestone it seemed a good time to share with HN. This is also a call for contributors to anyone who is interested in helping! The repository is hosted at https://github.com/nmfisher/thermion).

Some examples:

- A live DartPad playground so you can try the Dart-only (i.e. non-Flutter version) of Thermion in browser (Chrome only for now).

Also: Filament is a real-time physically-based renderer written in C++. It is mobile-first, but also multi-platform.

https://google.github.io/filament/

Also beginner here, I think you can learn other's codes to get a better understanding of the API by learning how others can abstract these concept into higher level. They're many great projects out there like Google's pbr renderer filament https://github.com/google/filament, AMD's gltf sample https://github.com/GPUOpen-LibrariesAndSDKs/glTFSample and also as many suggested, the Sascha Willems's repos https://github.com/SaschaWillems and the official sample https://github.com/KhronosGroup/Vulkan-Samples

In the Flame discussions page, there is a request for 3D, and Flame developers write that they will be happy to start working on support once when Impeller is stable on most major platforms. So what can the community do? 1) Create discussion topics, just like these posts. Or in other discussion forums. 2) Learn about Impeller, Filament, Flame, and Flutter and be willing to contribute to their development. 3) Join Flame now and try to do something or contribute. 4) Study the implementation of Flutter 3D, and try to do something together with ARCore or ARKit plugins.

Anyone know much about how this compares to Filament by Google?

https://github.com/google/filament

Have you tried Filament? https://google.github.io/filament/

I was looking through the Google Filament repo and I noticed that the classes in include/filament use a trick I haven't seen before that hide implementation details similar to PIMPL.

There are a handful of other examples out there of high-level shading languages - Cg (long deprecated), whatever Filament Material system uses (example), and various GLSL preprocessors (example).