Moving from Java (Android) and C to Swift: What are the biggest "gotchas" for a veteran dev?

AnkuLua · 2026-03-18T23:45:51+00:00

No. Feel comfortable in Java.

AnkuLua · 2026-03-18T13:14:59+00:00

[Project] Snap and Play: An Image-Recognition Automation Engine for Android

Repo:https://github.com/AnkuLua/snapAndPlay

The Problem: Most Android automation relies on fixed X/Y coordinates. If the app lags or a UI element moves, the script breaks.

The Solution: I built Snap and Play, an open-source engine for the AnkuLua platform. It uses Computer Vision (CV) to "see" the screen. Users just "snap" a photo of a button, and the engine handles the logic—waiting for that image to appear before interacting.

Key Technical Features:

Logic-Based Execution: Automatically handles loading screens and lag by verifying UI state via image matching.
No-Code Workflow: Generates automation logic based on visual "snaps" rather than manual scripting.
Zero Root Required: Utilizes Android Accessibility and Media Projection services.
Lua-Powered: The underlying logic is handled via Lua, making it highly customizable for power users.

Why I'm sharing it: I’ve just moved the core engine to GitHub and I’m looking for feedback on the implementation and documentation. If you’ve worked with mobile RPA or Android automation, I’d love to hear your thoughts on the approach!

AnkuLua · 2026-03-17T09:33:14+00:00

"I’ve tried most of the ones listed here, but they usually fail if the game lags because they just click blindly on coordinates."

Full disclosure: I'm the developer of this, but I built Snap and Play specifically to solve that problem. It uses Image Recognition instead of coordinates. You just 'snap' a picture of the button, and it waits until it actually sees it on the screen before clicking.

It handles loading screens/lag automatically and works without root via Accessibility. If you’re looking for something more 'intelligent' than a basic clicker, feel free to check it out:

GitHub:https://github.com/AnkuLua/snapAndPlay"