Screen recorder and media utility app: what works without code

Teachers making a two-minute walkthrough of a grading portal, support staff capturing a bug for a ticket, gamers clipping a round, small YouTubers who want a recorder without a watermark in the corner: the screen recorders in the store bury the one button you need under ads, and most stamp a logo you have to pay to remove. A recorder you describe yourself has exactly the controls you want and nothing else.

This guide is more candid than most, because recording the screen is one of the few features where the browser preview cannot do the real thing. App Builder Agent's live preview simulates the recorder so you can design and test every screen; the actual capture only happens on a phone, after the APK asks Android's "start recording or casting" permission. We'll be explicit about which is which, then build the utilities around it — trim, convert, gallery — that work everywhere.

What a screen recorder and media utility app must handle

• One-tap record with a countdown — Three seconds to get to the thing you want to capture, then a stop control you can reach.
• The media projection prompt — Android insists the user confirms screen capture every time; the app must handle "cancel" gracefully.
• Microphone and internal audio choice — Voice-over for tutorials, silent for bug reports; internal audio depends on the Android version.
• Quality settings — Resolution, frame rate, bitrate; 720p at 30 fps is the sensible default for file size.
• Gallery of recordings — Thumbnails, duration, size, sorted by date, with rename and delete.
• Trim — Cut the fumbling at the start and the scramble for the stop button at the end.
• Convert and compress — MP4 to GIF for a chat, or a smaller MP4 for email.
• Share and storage management — Share sheet to any app, plus a total-size counter and "delete older than 30 days".

Build it with App Builder Agent, step by step

1. Create a mobile app project and decide what is real in the preview. Tell the agent up front that recording should be simulated in the browser (a timer and a placeholder clip) and real on the device. It will structure the code so the same screens drive both, which saves you rewriting later.
2. Describe the recorder, the gallery and the tools.
   Build a screen recorder app called "ClipDesk". Home screen: big Record button with a 3-second countdown, toggles for microphone on/off and show-touches, quality picker (480p/720p/1080p, 30 or 60 fps). On Android, request screen capture through the media projection permission and show a persistent notification with a Stop action; in the browser preview, simulate the recording with a timer and save a placeholder clip so I can test the flow. Recordings screen: grid of thumbnails with duration and size, tap to play, long-press for rename, delete and share. Tools tab: Trim (drag start and end handles, preview, save as a new file), Compress (target size 10, 25 or 50 MB), Convert to GIF (pick a 10-second range, 15 fps). Settings: save folder, delete-after days, default quality. Store files in the app's own folder and metadata in AsyncStorage. Dark theme, orange record button, no ads, no watermark.
3. Test everything except the capture in the preview. Run the countdown, confirm the recording state shows a timer and a stop control, open the placeholder clip in the gallery, trim it, share it through the share sheet. Use the Simulate panel to deny the microphone and check that the app explains itself rather than crashing.
4. Download the APK and record for real. Install the test APK from the Preview tab, tap Record, and Android shows the "start recording or casting with ClipDesk?" dialog — that is the media projection prompt, and it is the moment the app becomes real. Record thirty seconds of the home screen, open it in the gallery, and check audio if you enabled the microphone. Anything wrong here (black frames, no sound, orientation) goes back to the agent as a message with your phone model and Android version.
   On my Samsung A54 (Android 14) the recording is saved but rotates to landscape when I turn the phone and the video shows black bars. Lock the recording to the orientation at the moment I press Record, and add a "record in landscape" option.
5. Tune quality and storage, then ship. Set the default to 720p/30 fps, add the size counter, and ask for the "delete older than 30 days" cleanup to run on app open. Then build the signed APK and AAB if it is going to the Play Store.

What works in the preview and what needs the phone

Because this is the question everyone asks, here it is plainly. In the browser preview: every screen, the countdown, the simulated recording state, the gallery with placeholder clips, trim and convert on those clips, the share sheet, permission denials via the Simulate panel, notifications, and the image picker for bringing in your own videos. On the phone only: the media projection prompt and real screen capture, microphone and internal audio, real file sizes and encoding speed, the persistent notification's Stop action, and behavior when you switch to another app while recording — the preview cannot leave itself, so that last one is always a device test.

Prompts that work well

The recorder is a base; the utilities around it define the product. Some directions people take it:

Common mistakes (and the fix)

• Assuming the preview recorded something. It didn't; it saved a placeholder. Budget one round of device testing before you tell anyone the app works.
• No plan for "cancel" on the projection prompt. Users tap Cancel; the app must return to idle, not sit in a broken recording state. Ask for it explicitly.
• Recording at 1080p/60 by default. A five-minute clip is hundreds of megabytes and older phones drop frames. Default to 720p/30 and let power users change it.
• Trimming that re-encodes the whole file. Ask for trim to cut without re-encoding where possible; it's seconds instead of minutes.
• Saving into a folder the gallery app can't see. Ask for recordings to be saved to the public Movies folder (with a ClipDesk sub-folder) so they show up in the phone's gallery too.
• Hard-coding internal audio. Internal audio capture isn't available on every Android version or device; ask for it to be an option that hides itself when unsupported.

Make it feel finished

• A notification Stop action — nobody wants to reopen the app to stop.
• Thumbnails generated from the third second, not the first frame, which is usually the countdown.
• File names like ClipDesk_2026-09-08_14-32.mp4 so they sort correctly anywhere.
• A storage bar in Settings: "1.4 GB in 23 recordings" with a one-tap cleanup.
• Elapsed time shown on the lock-screen notification while recording.

Installing, publishing and next steps

The first version is free to build; the test APK from the Preview tab is release-signed and installs on any Android phone without Android Studio. The AI app builder page covers the $1 permanent membership for unlimited test builds and source export, and signed APK + AAB with your own package id for the Play Store, where a recorder must declare its screen-capture use in the listing.

See what others have shipped in the ready-made photo & video apps gallery. If the utility side interests you more than recording, the photo editor and scanner guide covers image tools with the same approach, and the APK install guide explains the prompts your testers will see when they sideload. Open the builder and start with the prompt above — and keep a phone charged for step 4.

Frequently asked