Skip to content

Add LG City Historic Engine to Liquid Galaxy GO Store - #96

Closed
Yasmina-R-S wants to merge 7 commits into
LiquidGalaxyLAB:mainfrom
Yasmina-R-S:add_lg-city_historic_engine
Closed

Add LG City Historic Engine to Liquid Galaxy GO Store#96
Yasmina-R-S wants to merge 7 commits into
LiquidGalaxyLAB:mainfrom
Yasmina-R-S:add_lg-city_historic_engine

Conversation

@Yasmina-R-S

Copy link
Copy Markdown
Contributor

Description

This pull request introduces LG City Historic Engine to the Liquid Galaxy GO Store, developed as part of Google Summer of Code 2026.

City Historic Engine is an application designed to provide historical and cultural information about different cities, in my case I did Lleida. The main objective of the project is to make relevant information about the heritage, history, and historical events of different cities more accessible, using the visualization and interaction capabilities of Liquid Galaxy.

Relevant Links
Source Repository: LG City Historic Engine

Contributor & Mentors
Contributor: Yasmina Ramadan
Mentors: Claudia Diosan

Yasmina-R-S and others added 3 commits August 17, 2026 11:09
Description

This pull request introduces LG City Historic Engine to the Liquid Galaxy GO Store, developed as part of Google Summer of Code 2026.

City Historic Engine is an application designed to provide historical and cultural information about different cities, in my case I did Lleida. The main objective of the project is to make relevant information about the heritage, history, and historical events of different cities more accessible, using the visualization and interaction capabilities of Liquid Galaxy.

Relevant Links
Source Repository: [LG City Historic Engine](https://github.com/LiquidGalaxyLAB/lg-city-historic-engine)

Contributor & Mentors
Contributor: Yasmina Ramadan
Mentors: Claudia Diosan

@yashrajbharti yashrajbharti left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the .idea folder

Images are inconsistent in size

please check the instructions on reducing app size in #question_and_answers section

@Yasmina-R-S

Yasmina-R-S commented Aug 17, 2026 via email

Copy link
Copy Markdown
Contributor Author

@yashrajbharti

Copy link
Copy Markdown
Member

Please remove the .idea folder
please check the instructions on reducing app size in #question_and_answers section

@yashrajbharti

Copy link
Copy Markdown
Member

Please try this:

A. Code Shrinking & Obfuscation (R8/ProGuard)
Add isMinifyEnabled = true to build.gradle.kts. The Android R8 compiler analyzes your code to find out exactly which classes and methods are actually invoked. It then aggressively strips out the "dead code" (methods and classes that are never used). As a bonus, it obfuscates the code by renaming long class names to single letters, saving even more bytes.

B. Resource Shrinking
Add isShrinkResources = true to build.gradle.kts. How it works: Code shrinking removes unused code, but what about images, layouts, and XML files that were associated with that dead code? Resource shrinking works hand-in-hand with R8. Once R8 determines which code is removed, the resource shrinker safely deletes any .xml, .png, or .webp files that are no longer referenced by the remaining code.

C. ABI Splitting (Application Binary Interface)
Use the flutter build apk --split-per-abi command instead of the standard build command. How it works: Android devices run on different CPU architectures (primarily arm64-v8a, armeabi-v7a, and x86_64). A standard APK bundles the C++ Flutter engine for all three of these architectures into one massive file ("fat" APK). By splitting it, we generate a separate, small APK tailored perfectly for each specific processor, ensuring the user downloads only the binary their phone actually needs.
(NOTE: The arm64 is the modern standard for a phone/tablet, & most android emulators and Chromebook uses x86_64. So, prefer standard build, if there are no constraints on APK size as such, and for extended support for different architectures ; while prefer split build for niche requirements.)

D. Use WebP Images instead of PNGs/JPGs
WebP provides superior lossless and lossy compression. An image saved as a WebP will look identical to a PNG but often consumes 30% to 50% less space.

These are some ways to reduce the APK size without touching the technical aspects.
I hope this helps anyone dealing with bloated build sizes!

@Yasmina-R-S

Yasmina-R-S commented Aug 17, 2026 via email

Copy link
Copy Markdown
Contributor Author

@Yasmina-R-S

Yasmina-R-S commented Aug 17, 2026 via email

Copy link
Copy Markdown
Contributor Author

@yashrajbharti

Copy link
Copy Markdown
Member

@Yasmina-R-S let me know if you can delete the idea files and make sure the app size comes down under 50mb.

I am seeing github is up.

If you are unable to, please make a new PR and close this one.

@yashrajbharti

Copy link
Copy Markdown
Member

Please file a new PR with the changes!

@Yasmina-R-S
Yasmina-R-S deleted the add_lg-city_historic_engine branch August 18, 2026 06:57
@Yasmina-R-S

Yasmina-R-S commented Aug 18, 2026 via email

Copy link
Copy Markdown
Contributor Author

@yashrajbharti

Copy link
Copy Markdown
Member

Please make a new PR and thanks!

@Yasmina-R-S

Yasmina-R-S commented Aug 18, 2026 via email

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants