u/PositiveMaterial5297

Hi r/AppStoreOptimization!

I recently launched CocoCut (https://cococut.app), an iOS app that helps people capture 1-second daily clips and automatically stitches them into a mini vlog without manual editing.

I'm currently trying to optimize our US App Store product page conversion rate (CRO) and would love some blunt feedback from this community.

Current Metadata Setup:

• Title: CocoCut - 1s Vlog Diary
• Subtitle: Daily Video Diary, No Edits
• Primary Category: Lifestyle
• Screenshot Structure:
  1. One second at a time (Lifestyle value hook)
  2. Tap once. Capture one second. (Core interaction)
  3. Clips stitch themselves (Automation feature)
  4. Stickers, captions & film looks (In-camera aesthetic)
  5. Ready to share in one tap (Export)

🔍 Questions I'd love your take on:

1. First 3 Screenshots: Do they communicate the value proposition fast enough, or does the text above the phone mockup get lost?
2. Subtitle Keywords: Does "Daily Video Diary, No Edits" sound natural and high-intent, or should I lean more towards "1-Second Video Journal / Mini Vlog"?
3. Contrast & Framing: Does the soft gradient background work, or should the device frame and text have stronger contrast?

Appreciate any harsh critiques or suggestions to improve conversion!

I kept opening my camera roll, seeing a pile of almost-moments, and never making anything from them. Not because I didn't care. Editing just always felt like homework I was going to skip.

So I built CocoCut.

You tap once. It records one second. Those clips stack into a mini vlog on their own. No timeline. No "I'll finish this later" folder that never gets opened.

What it does:

• Tap once, capture one second
• Clips stitch themselves into a vlog
• Stickers, captions, and film looks while you shoot
• Export in one tap
• No account, no cloud. Videos stay on your phone

I made it for ordinary days. The ones that don't feel worth filming, then disappear anyway.

Site: https://cococut.app

If you try it, blunt feedback is welcome:

1. Is one second the right default, or too short?
2. Does auto-stitch feel obvious, or still confusing?
3. What would stop you from using this for a week?

Hey Flutter devs,

If you've ever built video recording in Flutter on Android with the official camera package, you've probably hit this:

You tap record, and nothing happens for about half a second. The preview freezes, the button feels dead, and users double-tap because they think the app missed the first press.

We measured it on a Pixel 8 Pro: 436-511ms before recording actually started.

After digging through the native CameraX bindings in camera_android_camerax, the cause was pretty simple. We patched it, and start latency dropped to 33-60ms.

What was wrong

In the official plugin:

1. VideoCapture is only bound when startVideoRecording() runs
2. As soon as stopVideoRecording() finishes, VideoCapture is unbound again

So every record tap forces CameraX to tear down and rebuild the native CaptureSession. That session reconfig is most of the lag.

The fix

Keep VideoCapture permanently bound alongside Preview.

Once it stays warm:

• record no longer rebuilds the capture session
• MediaCodec surfaces are already ready
• shutter latency falls from ~500ms to ~33-60ms

Hardware edge cases

Keeping VideoCapture warm makes rapid lens flips and backgrounding more fragile on some Android devices. We serialize camera ops with a small queue so the previous native generation fully finishes before the next one starts:

Future<R> _enqueue<R>(Future<R> Function() operation) {
  final completer = Completer<R>();
  _operationFuture = _operationFuture.then((_) async {
    try {
      completer.complete(await operation());
    } catch (e, s) {
      completer.completeError(e, s);
    }
  });
  return completer.future;
}

Separate issue, same camera stack: CameraX often reports multi-lens phones as one unknown logical camera with a zoom range like 0.5x-5x. We detect minZoom <= 0.5 and expose the ultra-wide control from that range instead of waiting for a clean physical-lens type.

Pixel 8 Pro numbers

Metric	Upstream camera_android_camerax	Persistent VideoCapture patch
recording_start_ms	436-511 ms	33-60 ms
CaptureSession reconfig	every record tap	zero while warm
rapid lens-flip crash rate (our internal log)	~2.4%	0.0% after serialization

Patch

Repo: https://github.com/xcc3641/camera_android_camerax

dependency_overrides:
  camera_android_camerax:
    git:
      url: https://github.com/xcc3641/camera_android_camerax.git
      ref: 9dd36c8

Happy to answer questions about the lifecycle queue or the CameraX binding change.

I’ve always been obsessed with retro-futurism, 90s VHS textures, and digital glitch aesthetics—especially Pixel Sorting.

Whenever I wanted to quickly turn a photo into glitch art on my phone, I found the options frustrating: either you needed desktop software like Photoshop/After Effects, or mobile apps were super clunky with laggy controls.

So over the past few months, I built Yan — a lightweight, mobile-first editor using real-time custom shaders, so you can tweak and layer cyberpunk and Y2K effects in seconds.

---

🌐 Official Website & App Store

• Official Website: https://yan.yichenlab.com
• App Store: https://apps.apple.com/app/id6757863100

---

✨ What Yan actually does:

• Live Pixel Sorting: Drag and tune glitch threshold/angle directly on your screen.
• VHS & CRT Scanlines: Replicates authentic analog TV static and tape color bleeding.
• Frosted Glass Layering: Creates atmospheric layering for portraits and cityscape shots.
• Cyberpunk UI: Clean, distraction-free interface built for fast mobile editing.

---

💬 Looking for Feedback

I’d love to hear what you think or what other glitch styles/features I should build next! Thanks for checking it out! 🚀