feat: add quick shortcuts on Android

[MarmoPL]

quick shortcuts - quick win :)

they change names based on currently selected phone language
they appear only on Android

[greptile-apps]

Greptile Summary

This PR adds three Android static launcher shortcuts (Parkings, Radio LUZ, Map) that appear when a user long-presses the ToPWR app icon. The implementation is clean and idiomatic: the android.app.shortcuts meta-data is correctly placed inside the existing AudioServiceActivity declaration (which is the registered main activity), the shortcut intents use full HTTPS deep-link URLs that are already handled by the app's Flutter deep-linking layer (flutter_deeplinking_enabled = true), and label strings are provided in both English and Polish.

Key points:

• android:targetClass / android:targetPackage correctly point to com.ryanheise.audioservice.AudioServiceActivity / com.solvro.topwr, matching the registered activity in the manifest.
• Label localisation works correctly through the standard values/ and values-pl/ resource folders.
• Icon drawables (map.xml, parking.xml, radio_luz_logo.xml) are valid VectorDrawables; the radio_luz_logo.xml has minor cosmetic issues noted in previous review threads.
• All three shortcut intents have identical short and long labels — a separate _long variant could improve future extensibility (previously flagged).

Confidence Score: 5/5

Safe to merge — no P0/P1 issues; all remaining concerns are minor style notes previously flagged or cosmetic.

The implementation is technically correct: correct activity target class, valid deep-link URLs, proper resource scoping for i18n. No logic errors, security issues, or data-integrity problems were introduced. All findings are P2 style/cosmetic items mostly already raised in prior threads.

No files require special attention; radio_luz_logo.xml has minor cosmetic issues already flagged in previous threads.

Important Files Changed

Filename	Overview
android/app/src/main/AndroidManifest.xml	Correctly adds the android.app.shortcuts meta-data inside the existing AudioServiceActivity declaration, matching the activity that owns the deep-link intent filter.
android/app/src/main/res/xml/shortcuts.xml	Defines three static shortcuts (parkings, radio, map) using correct targetClass / targetPackage values; intents fire HTTPS deep-link URLs handled by Flutter's deep-linking layer. Short and long labels are identical (already flagged). Missing EOF newline.
android/app/src/main/res/drawable/radio_luz_logo.xml	Vector drawable for the Radio LUZ shortcut icon; previously flagged issues include unused xmlns:aapt namespace and a path subcommand (H-0.1) that slightly exits the left viewport boundary.
android/app/src/main/res/values/strings.xml	English string resources for shortcut labels; minor mixed-indentation style (tab on first entry, spaces on others).
android/app/src/main/res/values-pl/strings.xml	Polish translations for the three shortcut labels; minor mixed-indentation issue already flagged in a previous thread.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Android Launcher long-press]) --> B{Static Shortcuts}
    B --> C[Parkings shortcut\nhttps://topwr.solvro.pl/parkings]
    B --> D[Radio LUZ shortcut\nhttps://topwr.solvro.pl/radio-luz]
    B --> E[Map shortcut\nhttps://topwr.solvro.pl/buildings]
    C --> F[AudioServiceActivity\ncom.solvro.topwr]
    D --> F
    E --> F
    F --> G[flutter_deeplinking_enabled\nroutes intent URL to Flutter]
    G --> H[Parkings screen]
    G --> I[Radio LUZ screen]
    G --> J[Buildings/Map screen]
    K[values/strings.xml\nEnglish labels] --> B
    L[values-pl/strings.xml\nPolish labels] --> B

Loading

_{Reviews (5): Last reviewed commit: "fix: changed quick shortcuts icons" | Re-trigger Greptile}

[simon-the-shark]

yeah nice, but can we use the same icons we already have in the app for these to have consistently feeling UI?

[MarmoPL]

Can I leave Radio Luz icon or change it to general radio icon?

[MarmoPL]

it's good to go

and i don't think that build failure is an issue on my end, they are only icons after all... (it's something with device_info_plus)