android-maps-compose
composePPT
android-maps-compose | composePPT | |
---|---|---|
5 | 3 | |
1,065 | 300 | |
1.0% | - | |
8.3 | 1.8 | |
7 days ago | about 1 year ago | |
Kotlin | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
android-maps-compose
-
Jetpack Compose for Maps
Google Maps for Compose Repo: The repo containing the source code for the library. Contains code samples on how to use the library and also where you can submit your bug reports and contributions
-
Google maps for compose development stalled since March
Does anybody know what happened to the team developing the google maps for compose library?
-
30k lines of SwiftUI in production later
Jetpack Compose (Google's alternative on Android, that also works pretty much anywhere you can run a JVM and others like the web [1], terminals[2], powerpoints[3], as well as pretty much anywhere you have an imperative API that you want to transform into a functional model[4]) is infinitely more polished and has better tools than anything Apple has put out in all of SwiftUI's existence. Apple is bringing this upon themselves with their "major updates" concept for SwiftUI coming every other year, where components aren't even available on old versions of iOS. A UI toolkit is a library like any other, version it like a library and match patch releases.
[1] https://compose-web.ui.pages.jetbrains.team/
[2] https://github.com/JakeWharton/mosaic
[3] https://github.com/fgiris/composePPT
[4] https://github.com/googlemaps/android-maps-compose
-
Simple Google Map App - Jetpack Compose
This simple Google Map app is based on the simplified version of sample app from this Google Map compose library. In addition, I added the following features into this sample app:
- Maps Compose: Jetpack Compose components for the Maps SDK for Android
composePPT
-
30k lines of SwiftUI in production later
Jetpack Compose (Google's alternative on Android, that also works pretty much anywhere you can run a JVM and others like the web [1], terminals[2], powerpoints[3], as well as pretty much anywhere you have an imperative API that you want to transform into a functional model[4]) is infinitely more polished and has better tools than anything Apple has put out in all of SwiftUI's existence. Apple is bringing this upon themselves with their "major updates" concept for SwiftUI coming every other year, where components aren't even available on old versions of iOS. A UI toolkit is a library like any other, version it like a library and match patch releases.
[1] https://compose-web.ui.pages.jetbrains.team/
[2] https://github.com/JakeWharton/mosaic
[3] https://github.com/fgiris/composePPT
[4] https://github.com/googlemaps/android-maps-compose
-
Show HN: Async UI: A Rust UI Library Where Everything Is a Future
Today in "HN never used a reactive framework that is not React and is offended when UI is not written with Dear ImGui".
This is literally the exact style of SwiftUI and Jetpack Compose (down to the author having used the term fragment, I sure hope this isn't leftover trauma from being an Android developer), except written in Rust (hence having to deal with lifetimes in the middle, default parameters, lambdas being quite verbose and needing to move things, etc).
Not blocking the UI thread is mandatory if you ever want to make any kind of complex UI. If you're a web dev, well you only have one thread anyways, good luck, if you're on any other platform, interactions _cannot_ ever block the UI (unless you, yourself, update the UI to say it is blocked). Making this async is a good thing.
Stack traces are a problem, but then again they've been a problem in any remotely capable UI toolkit.
With ReactiveCell, it looks surprisingly similar to what Compose does, where modifying a State causes recomposition of everything observing it. Which means that it might be powerful enough one day to do the same things as Molecule (https://github.com/cashapp/molecule), or ComposePPT (https://github.com/fgiris/composePPT), where everything is a potential target and it interops really well with existing toolkits.
- GitHub - fgiris/composePPT: An experimental UI toolkit for generating PowerPoint presentation files using Compose
What are some alternatives?
Jetpack-Compose-Playground - Community-driven collection of Jetpack Compose example code and tutorials :rocket: https://foso.github.io/compose
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
secrets-gradle-plugin - A Gradle plugin for providing your secrets to your Android project.
Caliburn.Micro - A small, yet powerful framework, designed for building applications across all XAML platforms. Its strong support for MV* patterns will enable you to build your solution quickly, without the need to sacrifice code quality or testability.
Demo_SimpleGoogleMap - Implement Google Map app using Jetpack Compose components for the Android Maps SDK
Learn-Jetpack-Compose-By-Example - 🚀 This project contains various examples that show how you would do things the "Jetpack Compose" way
MapCompose - A fast, memory efficient Jetpack Compose library to display tiled maps, with support for markers, paths, and rotation.
mosaic - An experimental tool for building console UI in Kotlin using the Jetpack Compose compiler/runtime