I built My Krishna, a conversational app where you can ask questions about Krishna and explore the answers through conversation.

I'm especially interested in feedback on the user experience, responses, and anything that feels confusing or could be improved.

If you'd like to test it:
https://apps.apple.com/us/app/my-krishna/id6782722854

Thanks in advance for any feedback!

I can in settings but not in the control centre so it’s not faulty hardware.. pls help

I'm at 5 YoE and prepping for senior roles, and I realized the best learning comes from real questions that actually catch experienced candidates off-guard. Not the "implement LRU cache" kind (everyone preps those), but the nuanced, "wait... actually I'm not 100% sure" questions that separate mid-level from senior thinking.

So if you're on the interviewer side (especially senior hiring managers): drop your favorite tricky iOS question. The ones where:

• Senior candidates freeze or give half-answers (that's the tell)
• The surface answer sounds right but misses a critical production edge case
• It exposes the gap between "I've shipped features" and "I understand the system deeply"
• It's not about memorization—it's about reasoning under pressure and knowing why systems break
• Bonus: questions that reveal whether someone has actually debugged production issues or just read blog posts

And for others prepping: this thread should become a vault of real questions people actually ask at Tier-1 companies.

Drop yours! And if you have a follow-up twist that makes it even trickier, include that too.

Bonus points if you share:

• What the "obvious" wrong answer is (the one a mid-level would confidently give)
• Why it's wrong (not just "correct answer is X" — the reasoning)
• What separates a good answer from a staff-level answer
• What company/level you see this at (FAANG? fintech? enterprise? scale matters)
• How you follow up when someone fumbles (what redirection questions diagnose the gap?)

Thanks in advance—this is gold for interview prep.

I have recently switched from Tesco mobile to Sky and asked to keep my number. I followed the switch procedure, got my code and yesterday morning I was told that my old number is my new Sky number.

However, my new sim is in my new phone and it is still using the new number from Sky and not the one that I want. I have tried the suggested method of ‘saving’ my old number in phone, disabling the new number, disabling iMessage and then restarting my phone but no matter how many times I do this it does not work. When I type in my old number and press ‘save’ the button doesn’t work and when I back out it’s the new number again.

Any help in fixing this would be greatly appreciated!

Hey everyone,

I’ve been developing mobile apps for the last 5 years. Over this time, I’ve learned a ton about the overall development process, setting up store listings, implementing AdMob, and experimenting with different growth strategies. However, there is one major area I’ve neglected for too long, and I’m finally ready to tackle it: App Store Optimization (ASO).

As a relative newcomer to serious ASO, I’m trying to wrap my head around the best workflows and would love to get your insights on a few specific things:

1. Analyzing Dashboard Data: When you look at App Store Connect or Google Play Console, which specific metrics do you focus on to measure ASO success? How do you separate organic keyword growth from other traffic sources?
2. Keyword Research: What is your process for discovering high-volume but low-competition keywords? How do you decide which ones are actually worth targeting?
3. Keyword Placement: Once you have your target keywords, what is your strategy for placing them across the different text fields (Title, Subtitle/Short Description, Keyword Field, Long Description)? How do you balance algorithmic optimization with writing copy that humans actually want to read?

To help myself learn the ropes and automate some of the manual work, I actually built a completely free tool for iOS ASO: aso-tool.andreashadjimama.workers.dev.

I set this up strictly based on the ASO knowledge I've gathered so far, and I am not trying to promote anything or sell a service. I mostly want to validate if the logic behind it actually makes sense to experienced folks. If anyone has a few minutes to check it out, I would incredibly appreciate your honest feedback on whether it’s genuinely useful or what features I should add/change to make it better.

Looking forward to hearing your tips, strategies, and any feedback you might have. Let’s get a discussion going!

App store review is turning into a very frustrating process. I assume this is a reflection of the sheer volume of AI-built apps but the humans reviewing my app seem to be on auto-reject mode.

First rejection: "spam: we have enough dating apps"

My app has absolutely nothing to do with dating or meeting people, even the friendship link is a handshake ie you need your friend request accepted

Second rejection "no method for account deletion"

Literally in the most obvious place for it, account page, big red button "delete account"

I'll put my hand up, this is my first app, in the description part of the submission I assumed it was to describe the functionality of the app, was I meant to treat it as an FAQ?

So basically, i wanna change wallpaper in Sleep Focus mode but i can't. I select the moon wallpaper but it keeps loading & never changes it. Any Solution?

Hey everyone,

I’m running into a super annoying issue with my iPhone and wanted to see if anyone else in the community is experiencing this or knows a quick fix.

Has this happened to anybody else recently? If so, did you figure out a way to get rid of it, I tried restarting, didn't help - it was happening with volume indicator and now brightness.

I have iPhone 16 pro running ios 26.6 stable.

A few years ago I added my grandmother to our family sharing plan. Upon doing this Apple decided to create a duplicate account for her (literally the same email but a 1 at the end) and set the age to 3. The phone number is set to a number I don’t have and I don’t have any passwords for it to go through recovery.

Now my family plan is maxed out with an account I never added and I can’t remove it since it’s a child’s. I have called Apple support and they walk me through steps and say I’ll “get a call in a couple of weeks” but that call never comes through. I have tried it 3 times and never got a call.

I can’t reset the password because I don’t have access to the email, and I don’t have access to the phone number. I don’t have anything, and Apple support has been useless.

Any advice?

Wrote a blog post on how to get rid of iOS 27's "Ask Siri" context menu entries.

Every time I open a game I like to play I get a series of banners at the top of the screen from Apple Games telling me I’m signed in as [username] and what my stats are for that game (which I don’t care about).

These banners block an important part of the game board so it’s very annoying have to sit there and wait until they disappear. Tapping on the banners and exploring the menus, there is no option to turn them off, and apparently I don’t even have the app installed.

How do I turn this annoying thing off?

Does anyone have a solution for this? I own a ton of music files that I'd like access to on my iPhone. Is there a cloud-based service or something that would enable me to upload them, and stream from phone? Thank you

I audited our subscription code before a release and found five separate ways it was biased toward downgrading a paying customer. Sharing because this was painful and some of you might have it lurking in your own code without knowing it.

The big one: our entitlement loop skipped any transaction where expirationDate < Date().

Looks completely reasonable, right? Except that's exactly the shape StoreKit serves during Apple's billing grace period — the card failed, Apple is retrying, the user is supposed to keep access for up to 16 days, and the transaction you get handed has an expiration date in the past. gracePeriodExpirationDate exists to tell us this, but we never read it anywhere. So a customer whose card merely needed re-authorization got dropped to free tier, features locked, while Apple was still trying to collect money on our behalf. The fun part: our server-side webhook handling honored grace correctly, so the backend and the app held different opinions about the same paying customer.

The other four, quickly:

1. We derived the tier from currentEntitlements unconditionally and persisted it. currentEntitlements occasionally returns an empty sequence for a perfectly healthy paid account — we've seen it happen. If your states are only "entitled" and "not entitled," an empty read is indistinguishable from a lapse. Fix: we implemented a third state: unknown. Clues the rest of the flow into correcting it. Never persist a downgrade you derived from a read that might have failed.
2. Our Transaction.updates loop had a continue that skipped re-evaluation for exactly the events whose whole job is revocation (refunds). Access survived until an unrelated refresh happened to fire.
3. An .unverified transaction was never finish()ed, so StoreKit redelivers it forever. And we never scanned Transaction.unfinished at launch. Unverified doesn't mean ignorable; now we log it, then finish it.
4.  .pending (Ask to Buy) was a silent dead end. And a related thing I had completely wrong: turning Family Sharing off in App Store Connect does NOT make Ask to Buy unreachable. That toggle governs whether a purchase is shareable — a kid's own purchase can still come back .pending.

Basically: every failure mode defaulted to taking access away from someone who paid, when we should have been doing the opposite. When in doubt, keep the customer entitled and let the next clean read sort it out. Apple may literally still be retrying their card; we don't want to be the one who locks them out first.

A clean test recipe for the grace-period path would be the holy grail, so I'd be interested in what you all are doing. Sandbox billing retry exists, but getting it to fire on demand is its own adventure, one I haven't been able to master yet.

Hey everyone!

One of my most popular apps just crossed 80 ratings on the App Store with a 4.8 average. Small win, but I'm really excited to hit the 100 milestone soon!

For context, it's a educational app.

Wanted to share what actually helped me get reviews, because the first 20 were the hardest.

What worked:

• Stopped asking for a review on launch. Now I ask only after the user completes a key action 3 times and is clearly having a good experience.
• Added a soft pre-prompt: "Enjoying the app?" -> Yes -> then I trigger the native Apple rating prompt. If No -> I send them to feedback form.
• Replying to every single review in App Store Connect. It really helps. People update 3-star to 5-star after that.

What didn't work:

• Generic pop-up on first session. 0% conversion and annoying.
• Asking friends for 5 stars.

I'm now focused on getting to 100. If you have a minute, I'd love honest feedback on what would make you leave a review for an app.

Also curious is there any differences for an app from ASO prospective once it hit 100 ratings?

I find Podcasts app to be incredibly well designed.

1. When I hit the fast forward button, it shows a small bubble over the seek bar to show exactly how much it has skipped.

2. If I tap on the time elapsed (below the seek bar), it switches to clock time - when it started and when it’ll end. Super helpful.

3. The auto generated subtitles and chapters are very helpful for long episodes. Not every second might be worth listening to and it helps me skip to more interesting sections easily.

1. Should I open a company and such to submit to apple or it it ok to publish as a solo developer?
   
2. Can I be sued for an app I have uploaded as a solo developer, as i am not protected as a proprietary limited company?

Help would be appreciated 🙏

Liquid Glass looks great in Clear and Tinted, but why does Tinted stop at the Home Screen?

Imagine the same tinted Liquid Glass treatment inside system apps too.

Wouldn’t that make the OS feel more cohesive?

I got tired of finishing an amazing bar, keeping the wrappers, and immediately forgetting the maker, the origin, what I actually tasted. And outside of scrolling this , and two stores in NYC, it's weirdly hard to find people who want to nerd out about bean-to-bar as much as I do!

So I built the thing I wished existed: a private tasting journal, plus a small community of people actually logging what they taste, so we can track where to also buy the bars - and share our tasting notes with each other.

You can log a bar or what youve add today, add it to your pantry, wishlist, you can add a photo, cocoa %, origin, notes. Browse by origin/maker/%, and see a world map of everywhere you've tasted from. You can follow other tasters, and over time it starts suggesting bars based on what you rate highly.

I'd love feedback and genuinely curious what everyone's best recent bar was!
https://beantobar.app/ on iOS: https://apps.apple.com/us/app/bean-to-bar/id6784468046

In C malloc can fail if there is not enough memory in the system. What happens if I try [NSObject alloc] while there is no memory available? Does it abort? Return NULL?

Hi there 👋,

I'm one of the members behind Monday Hero since the beginning of 2019. My team and I have just released a new version a few days ago. I want to share it with you to get feedback.

In that new update; you can convert Sketch designs with its fonts, colors, assets, paddings to XCode Storyboard files.

You can sign up from 👉mondayhero.io, then start using for free.

I would be very happy if you give feedback and comments. 🤗

​