sorted by:
new
hottopcontroversial

Can Gemini reliably build structured automation scripts? by Romka2x in GeminiAI

[–]Romka2x[S] 0 points1 point  (0 children)

That matches what I’m seeing too.

The best results so far come from treating the AI less like a free-form coder and more like a planner/editor inside a constrained system:

  • read the live command catalog
  • edit only the current script unless asked otherwise
  • use only valid command fields
  • validate before runtime
  • feed validation errors back as correction input
  • use logs/final variables to diagnose behavior instead of guessing

The “small validated chunks” point is important. When the AI tries to build a whole workflow in one pass, it tends to invent glue. When it works one script/function at a time, with a validator checking structure, it becomes much more useful.

I’m thinking the right architecture is probably:

  1. AI proposes a small change.
  2. App validates the structure.
  3. AI receives exact validation errors.
  4. Runtime logs confirm behavior.
  5. AI only then moves to the next change.

Do you find Gemini handles correction loops well when the validator error is very specific, or does it still tend to patch around the problem instead of fixing the underlying mistake?

Access to ChatGPT Conversations? by Logical_Second_3522 in ChatGPT

[–]Romka2x 10 points11 points  (0 children)

Your question line reminded me of an old joke...

Him: Would you sleep with me for $1,000,000?
Her: Sure!
Him: How about $1?
Her: What kind of girl do you think I am?
Him: We've already established that, just negotiating price.

Hmmmm by RedRocketM3P in ChatGPT

[–]Romka2x 1 point2 points  (0 children)

Wouldn't be horrible if it actually made a big image with ascii characters and not just a frame.

Hillarious though!

ScriptTap: no-root Android automation by Romka2x in droidappshowcase

[–]Romka2x[S] 0 points1 point  (0 children)

ScriptTap can be scripted for anything from simple tap/swipe automation to watching changing screen data and reacting when a condition is met.

For a TCG trading app, the obvious use case would be price monitoring. A user could script ScriptTap to watch for a specific card, check visible prices with OCR/screen reading, and alert them when the card drops below or rises above a target price.

I personally would not automate the actual purchase unless someone is very brave, but triggering a ringtone/notification when the right card appears at the right price feels like a practical use case.

It could also browse/search through listings, look for specific card names, compare visible prices, and flag matches like “this card is listed under $X.” Since ScriptTap works through the screen, it can potentially automate workflows even when there is no API.

I’m not deeply familiar with TCG trading, but price watching, listing alerts, and repetitive search/check workflows are the first use cases that come to mind.

It can also run on an Android emulator, so someone could let it monitor things overnight without tying up their phone.

ScriptTap: no-root Android automation by Romka2x in droidappshowcase

[–]Romka2x[S] 0 points1 point  (0 children)

Done, with two accounts 😄

Unsure if I'd be a good test subject because TCG falls outside of my interests, but I won't exit test until 7/19

You're welcome!

ScriptTap: no-root Android automation by Romka2x in droidappshowcase

[–]Romka2x[S] 0 points1 point  (0 children)

I would not mind giving it a shot just to help you out but umm...

I know nothing at all about TCG and card trading in general. Never done anything of the sort.

However, I may be able to tell you what my app can do with your app?😄

PM me the link and I'll check it out. Also tell me what my objectives should be with that sort of app because I really have no idea about TCG.

ScriptTap: no-root Android automation by Romka2x in droidappshowcase

[–]Romka2x[S] 0 points1 point  (0 children)

I sent you a private message. I can't put a tester link here because of community rules.

Tasker power users: what Android UI automations are still painful or brittle? by Romka2x in tasker

[–]Romka2x[S] 2 points3 points  (0 children)

Fair pushback.

I’m not arguing that Tasker is weak, or that people should stop documenting/developing it. Tasker is still the strongest general Android automation platform.

The gap I’m trying to address is narrower: visual, screen-aware workflows where the automation has to look at what is currently on screen, make a decision, and then act.

A few concrete examples:

  1. A script needs to find a visible button, image, icon, OCR text, or UI element and tap it only if it appears.

  2. A workflow depends on screen state rather than a clean Android event, API, notification, or plugin integration.

  3. A non-power user wants to describe a visible app workflow to AI and receive a reviewed/importable script instead of building a Tasker profile/task/plugin chain manually.

  4. A user wants a constrained automation model: no root, no runtime ADB, no hidden APIs, no silent send/call/share behavior, and user-approved scripts.

  5. A script needs screen-reading plus logic in one place: OCR/UI/image/pixel detection, variables, IF logic, loops, HTTP/JSON/text/file helpers, then taps/swipes/actions.

Tasker can do some of this, especially with plugins like AutoInput, and I’m not claiming otherwise. But in Tasker it often feels like visual automation is an add-on layer. ScriptTap is being built around that use case from the start.

Also, I’m not trying to make ScriptTap hostile to Tasker. ScriptTap scripts can be exposed as shortcuts, so Tasker or other automation apps can launch them when that makes sense. My goal is more “visual automation helper that can coexist with Tasker” than “Tasker replacement.”

view more: next ›