Feature/android camera controls

[diegurrio]

⏺ Add touch camera controls to Android renderer

Adds gesture-based camera control to the Android NativeActivity renderer via a self-contained handle_touch() function in android_main.c — no changes to scene.c.

• 1-finger drag → orbit around vehicle (yaw + pitch, elevation clamped ±89°)
• 2-finger pinch → zoom (proportional to orbit distance, min 2m)
• 2-finger drag → pan orbit target along camera right/up axes
• Finger-count transitions reset gesture state to prevent camera jumps

How to Test

• 1-finger drag orbits smoothly without flipping at extremes
• Pinch zooms proportionally; stops at ~2m
• 2-finger drag pans; vehicle re-centers correctly
• 1↔2 finger transitions produce no camera jump
• ./gradlew assembleDebug passes

Screen_recording_20260416_222129.mp4

[Copilot]

Pull request overview

Adds gesture-based camera controls to the Android NativeActivity renderer by introducing a self-contained per-frame touch handler that directly updates the scene camera without modifying shared desktop camera logic.

Changes:

• Added handle_touch() in android_main.c to support 1-finger orbit, 2-finger pinch zoom, and 2-finger pan.
• Enabled Raylib gesture input on Android and initialized orbit state (target + previous touch tracking).
• Added design + implementation plan documents describing the touch control approach.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
android/app/src/main/cpp/android_main.c	Implements touch-driven orbit/zoom/pan camera updates for Android.
android/docs/superpowers/specs/2026-04-16-touch-controls-design.md	Documents gesture behavior and architecture for Android touch controls.
android/docs/superpowers/plans/2026-04-16-touch-controls.md	Step-by-step implementation plan for the touch control feature.
.claude/settings.local.json	Expands allowed gh command permissions for tooling automation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MikePehel]

I haven't had a chance to test it properly, but just from the video I can note a few things. It looks like mtl colors aren't being loaded on the drone obj. Do you know where and how that failed? I also see a volume bar, but this won't include audio from the log files, so that can probably be stripped.

The camera movement looks intuitive, but Ramon and I just chatted the other day about a weapon wheel style selection of features like the diegetic trails, or orthographic view switching. I just want to make sure your single finger presses wouldn't conflict with a long press hold on either the left side of the screen.

[diegurrio]

Hi @MikePehel nice to meet you.

Do you know where and how that failed?

Yup, it has to do with how Android handles assets. They need to be included in the APK and reading them from the JNI layer is a pain in the butt. I'll fix that in this PR.

I also see a volume bar, but this won't include audio from the log files, so that can probably be stripped.

Do you mean after pressing the volume button? That is normal system behavior but if you guys want to kill it I can intercept the event and handle it. I can also add that to this PR and we can decide if we keep the code. I would recommend we let the event go through and display the volume bar.

[diegurrio]

Long press / weapon wheel: No conflict with the current implementation. The touch handler only enables GESTURE_DRAG | GESTURE_PINCH_IN | GESTURE_PINCH_OUT, so GESTURE_HOLD isn't recognized at all right now. When the weapon wheel is implemented, the touch handler would need to check touch region or gesture type before routing to the camera. It should be straightforward to add at that point.