I’m testing two different drawer patterns for my iOS App (Not revealed here) and I’d love honest feedback from product and UI nerds about which one actually feels better.

The problem: Standard drawer UX uses an overlay. Tap the button, a dark sheet slides in from the side, covering the main content. It works, but it always feels like an interruption.

The experiment: What if the drawer was always there, just hidden behind the main card? A single swipe reveals it by sliding the card right, like pulling back a curtain. No overlay dim, no modal weight. You see both the primary content and the drawer at the same time as you browse.

Option A (Baseline): Dark overlay drawer slides in from the left, full-screen dim fades in, then tap anywhere outside to close.

Option B (Reveal): Swipe or drag the card right, the drawer slides out from behind, the card moves with it, and both stay visible as you browse. Swipe left or tap the card to close.

The tradeoff I’m wrestling with:

• Reveal feels lighter and more playful (no modal friction)
• Overlay is more predictable (everyone knows how sheets work)
• Reveal lets you browse while keeping the main content visible (context win), but it uses more screen space

Which one feels better to you? I’d love to hear if one feels more intuitive or natural, even if you’ve never seen either pattern before. What’s your first instinct?

>

I’m testing two different drawer patterns for my iOS App and I’d love honest feedback from designers and UI nerds about which one actually feels better.

The problem: Standard drawer UX uses an overlay. Tap the button, a dark sheet slides in from the side, covering the main content. It works, but it always feels like an interruption.

The experiment: What if the drawer was always there, just hidden behind the main card? A single swipe reveals it by sliding the card right, like pulling back a curtain. No overlay dim, no modal weight. You see both the primary content and the drawer at the same time as you browse.

Option A (Baseline): Dark overlay drawer slides in from the left, full-screen dim fades in, then tap anywhere outside to close.

Option B (Reveal): Swipe or drag the card right, the drawer slides out from behind, the card moves with it, and both stay visible as you browse. Swipe left or tap the card to close.

The tradeoff I’m wrestling with:

• Reveal feels lighter and more playful (no modal friction)
• Overlay is more predictable (everyone knows how sheets work)
• Reveal lets you browse while keeping the main content visible (context win), but it uses more screen space

Which one feels better to you? I’d love to hear if one feels more intuitive or natural, even if you’ve never seen either pattern before. What’s your first instinct?

>The app is live on the App Store. If you want to try the baseline version to compare, just let me know and I can share a link in DM, just trying to get real feedback here on which direction is better UX, not looking to promote.

I built this app as a fun side project.

>It’s a beautifully crafted pendulum clock for iPhone with customizable dials, gentle chimes, and an immersive full-screen mode. Search "Tempus Fugit" on app store to try it.

It wasn’t supposed to be my “big” project. I wasn’t trying to validate a startup idea or chase a market. I just wanted to build something I’d genuinely enjoy using.

Ironically, it’s ended up outperforming projects that I spent weeks planning.

It reminded me that people don’t always care how ambitious a project is. Sometimes they connect with something that’s simple, thoughtfully designed, and clearly built with care.

If anyone’s interested in trying it, I’m happy to share the link in the comments or via DM, depending on the subreddit rules.

I’d love to hear your thoughts on the video. What stands out to you? Is there anything you’d add, change, or improve?

I’m working on one of my iOS app for people who like keeping a clock around for the look of it, not just the time.

Stuck between two versions and curious where the design crowd lands.

Version A: Solid capsule. Single visual weight, doesn’t compete with the dial.

Version B: Same outer shape, with a transparent inner pill carved out. More detail, reveals the dial behind it, and leans toward the Junghans / Braun aesthetic where the hand itself carries decoration.

The hands rotate over numerals and tick marks, so anything decorative on the hand is something the eye has to parse on top of the dial. My gut says the solid version is more honest, but the cutout adds visual depth that flat shapes can’t.

Does the cutout add interest, or does it just make the hand fussier than it needs to be?

Honest feedback needed. just say A or B please.

I just had a fresh, nutritious meal in Kaohsiung for only NT$100 (less than US$4), and it reminded me why I love Taiwan.

As a traveler, it’s incredibly convenient. Healthy food is easy to find, affordable, and tastes great. You don’t have to spend much to eat well here.

Taiwan keeps proving that great quality of life doesn’t always have to be expensive. ❤️

Not a nostalgia project. I just kept noticing that a continuously moving pendulum gives a clock face a center of gravity that digital displays don’t have, and I couldn’t find an iOS app doing it without piling on Victorian skeuomorphism.

So I went the other way. Stripped the case down to a thin matte panel, kept the dial typography clean, made the bezel a Metal shader instead of a wood texture, and let the pendulum be the only ornamental element on screen.

The pendulum is a real free oscillator, not a sine animation. You can grab the bob mid-swing, and on release it decays back to its natural 10° baseline. Took a few weekends to get the swing feeling honest.

The app is called Tempus Fugit. Happy to chat about the SwiftUI, physics, or Metal shader implementation.

🤷🏻‍♂️

I’ll be honest. I’m writing this because I’ve been personally hurt by the system we all know is broken.

I won’t go into details, but I’m one of those people who experienced firsthand how corruption in India isn’t just a news headline. It touches real lives and real families. For a long time, I felt helpless watching the system protect itself while people like us had no voice.

When the Cockroach Janta Party movement started spreading across social media, something clicked. Not because of the memes, but because of the idea behind it. Peaceful. Creative. Unapologetic. People finally saying, “We see you, and we’re not afraid to say it out loud.”

I wanted to be part of it. But due to personal circumstances, I physically can’t be present at the protest.

So I did what I know best. I built something.

"Roach Attack" is a free iOS app I made entirely on my own. You pick any photo, and watch a swarm of cockroaches eat it. You can save it as a video and share it. That’s it. It’s stupid simple. It’s satirical by design. It’s not meant to incite anything. It’s meant to let people laugh at the powerful instead of fear them, which is honestly one of the oldest forms of protest.

There are zero ads. Zero in-app purchases. Zero subscriptions. I’m not making money from this. I just wanted to build something anyone could use freely as a form of expression.

The app is on the App Store. Search for "Roach Attack", or use the link to download.

App link: https://apps.apple.com/in/app/roach-attack-meme-video-maker/id6777873315

If this isn’t your thing, I completely understand. But if you’ve ever felt like you had no way to push back, maybe this gives you one small, ridiculous, satisfying way to do it.

Jai Hind. 🇮🇳

Got hit with Guideline 2.3.4 today:

"The app preview includes device frames. App previews should allow users to see what the app does and how it will appear on their device when the preview is played in full screen."

Fair enough. I removed the device frame, uploaded a new preview, and replied in the Resolution Center.

What frustrates me is the inconsistency:

• My previous submission for the same app was approved with device frames in the screenshots. No comments.
• Browse the App Store and you’ll still find plenty of app previews that appear inside device frames.
• Apple’s own developer marketing often showcases app previews within device frames.

It feels like there’s no consistent internal standard. The rule depends on whichever reviewer picks up your submission that day. Very frustrating sometimes.

My 2y old daughter got fascinated by an old grandfather clock, so I decided to build a modern version for iPhone.

The first proof of concept took just a few hours with Claude Code. I then spent another 2-3 weeks polishing it into something I’d actually be happy to ship.

Tech stack:

• 100% SwiftUI
• Metal shaders for rendering the clock dial and pendulum
• System Timeline API, so the animation stays smooth without constantly waking the CPU or draining battery
• Supports widgets, StandBy mode, auto start when charging connected, and multiple clock skins with optional chimes 🔔.

From idea to App Store took about 3 weeks.

One interesting part of this project was experimenting with vibe coding. Claude Code handled most of the implementation, while I focused on architecture, code review, debugging, and polishing with app icon design, assets, and Xcode configuration.

Apple also approved the app in just 18 minutes, which is probably the fastest review I’ve ever had.

I’m continuing to experiment with new clock designs and features, so I’d love to hear any feedback or ideas.

https://apps.apple.com/us/app/tempus-fugit-pendulum-clock/id6770431075

Thanks in advance!

I just received this email “Your Apple Business login is blocked” and it says my account has been blocked from accessing my organization in Apple Business.

What exactly does “Apple Business” mean in this context? Is it related to the Apple Developer Program, App Store Connect, Apple Business Manager, or something else?

If you’ve seen this before, what caused it and how did you resolve it?

I built "Roach Attack" as a fun side tool on iOS. The concept was simple: users upload a photo, watch digital insects consume it over 12 seconds, and save the result as a shareable video. It was a fun idea, nothing extraordinary. After launching on the App Store, the app remained relatively quiet.

Then something unexpected happened.

In early June, India experienced a significant moment. The #CockroachJantaParty movement gained traction across social media as a political protest. The timing was unusual because my app featured cockroaches as its core mechanic, insects that literally “eat” photographs.

The Unexpected Discovery

A user from the movement’s online community discovered the app and shared it on some WA group. The connection was immediate and fit perfectly with the movement’s humor and messaging. Within days, organic installs from India began accelerating rapidly.

Taking Action

Rather than simply watch the coincidence unfold, I decided to lean into it. I refined the app’s visual presentation, updated the screenshots to reflect the moment, and expanded the insect roster to strengthen the swarm concept at the heart of the app.

The Results

What started as an unexpected intersection between a side project and a protest movement grew into something meaningful. The app now has thousands of installs, driven primarily by organic discovery in India.

I intentionally kept the app free to use because I have virtually no ongoing expenses other than the dev account. I also promote my other apps within it, which ultimately helps me acquire users for those apps as well.

The biggest lesson from this experience is that timing, authenticity, and responsiveness matter. When your audience finds you, you need to be ready to meet them there.

No press since elected. Wtf

The cockroaches have questions 🪳

This subreddit may have accidentally inspired me to build an app.

You can now deploy cockroaches onto any photo and create campaign.

No ads. No subscriptions. Completely free.

I’m probably the only developer paying Apple $100/year so strangers can put cockroaches on their target’ faces.

App:
https://apps.apple.com/in/app/roach-attack-meme-video-maker/id6777873315

Long live the Party. 🪳

Hey CJP 🪳

I'm building this iOS app, inspired by what this movement stands for.

"Roach Attack iOS app". Pick any photo, summon a swarm (cockroach, ant, mosquito, scorpion, spider, cricket, or worm), and watch the boys devour it. Saves as a clean MP4 ready for reels and shorts.

Just to be upfront:
This is 100% satire. No other intention behind it. The whole point is so any youth can peacefully “protest” against someone they feel has it coming by leaving cockroaches on their face. Catharsis without anyone actually getting hurt. That’s the entire pitch.

Building natively in iOS. No paywall. No ads. No tracking. Photos never leave your phone. 100% free when it launches.

Apple is reviewing it right now. I’ll drop the App Store link in the comments the moment it’s live.

Demo attched.

If there’s a feature you’d want to see in the app, drop a comment. I’m reading everything and happy to ship more, either before launch or in a follow up update.

Who wants to eat aamrus?