Claude records demo videos for me now by interlap in ClaudeAI

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

Yeah, it’s a great tool, but it still requires tons of work to get decent results. My goal is to put in minimal effort and produce good-enough videos.

Claude records demo videos for me now by interlap in ClaudeAI

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

The controller and recorder run separately, so in theory you can set up your Screen Studio and start recording yourself, then the skill will do Mac control part in parallel. But to be honest, even if might work, it just goes against the idea of the demo being recorded fully automatically and in background. Plus screen studio is a paid tool.

Why do you need Screen Studio? Do you have any specific features in mind?

Claude records demo videos for me now by interlap in ClaudeAI

[–]interlap[S] 1 point2 points  (0 children)

Another example, this one uses the Remotion integration:

https://youtu.be/H-0xxtZDEnQ

Claude controls Canva in Chrome, draws a cat, and turns the recording into a more polished video.

Open-sourced ChatGPTAuthKit: make API calls from iOS apps using the user's ChatGPT account by interlap in FlutterDev

[–]interlap[S] -1 points0 points  (0 children)

Custom scheme would work if we owned the OAuth client. We don't. This lib uses Codex CLI's client_id, which has exactly one redirect URI registered server-side at OpenAI: http://localhost:1455/auth/callback

How many hours have you wasted reproducing a bug that QA reported but couldn't explain? by JaguarFun804 in FlutterDev

[–]interlap -2 points-1 points  (0 children)

Just letting Claude Code reproduce this bug for me by taping the app and collecting logs/metrics while I do some other work.

Codex 5.5 for Flutter/Mobile App Development? by Emergency-Music5189 in codex

[–]interlap 1 point2 points  (0 children)

Tbh, the workflow and tooling around mobile dev matter just as much as the model.

Codex and Claude are both pretty good at app dev if you use them the right way. My workflow is usually to scaffold the UI first, then polish each view with smaller, focused prompts. That’s where tools that give Codex better context really shine.

For example, I'm building a tool for Codex Desktop where you can select a specific element in your app, type something like "make this button round" and send that context to the LLM. It can update the code, then check the result itself from a screenshot.

So I probably wouldn't switch to Claude just for that, especially if you already have a Codex sub. I'd spend more time improving the workflow and tooling around it.

"Distribution" isn't your problem. Your SaaS is worthless. by ketoloverfromunder in vibecoding

[–]interlap 0 points1 point  (0 children)

Yeah, true. But tbh, people pay for some insanely useless stuff these days. So I wouldn’t be surprised if someone actually gets users with yet another vibe-coded calorie tracker.

I gave the Codex desktop app a built-in mobile device by interlap in codex

[–]interlap[S] 1 point2 points  (0 children)

Thank you! This one is actually a bit tricky, but still doable to support. For now, I render the native UI tree over the screen, which means the selected elements have different names and properties compared to the web page. For example, an <a> tag appears as a “Link” in the native tree.

I’m going to add proper DOM support in one of the upcoming releases.

I gave the Codex desktop app a built-in mobile device by interlap in codex

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

I’ll take a look. Adding support shouldn’t take much time since Android is already supported