I m testing my iOS app on an iPhone running a pre-release/beta version of iOS.
When trying to leave an App Store rating/review, I get this message: You can t write reviews while using a prerelease version of iOS.
Has anyone faced this issue before?
Is there any official way to submit an App Store review while staying on the iOS beta, or is using a device running the public/stable iOS version the only option?
I ve been thinking about this while working with an interview-practice platform that already runs as a web application.
The core experience works well on desktop, but the way people use the product on mobile is quite different. Interview practice can involve voice interaction, microphone access, short practice sessions, progress tracking, and returning to the platform regularly.
That makes me wonder - whether simply making the website responsive is enough for this kind of product.
At what point does it make sense to give users a dedicated mobile experience rather than continuing to optimize the browser version?
Finding interesting software is easy, but keeping track of it is a mess. Every week I come across several tools on Product Hunt, think "that looks useful," close the tab, and forget the name within an hour. Then, when the exact problem pops up weeks later, I cannot remember what the app was called.
Right now, my system is just a single notes document crammed with dead links and half-finished descriptions. It does not work.
How do you keep a shortlist of software you want to test? Do you use browser bookmarks, a dedicated notes app, a spreadsheet, or a read-later queue? Also, do you actually check back through your list, or does it turn into an unorganized graveyard?
We were picking a CRM for the studio, and I went down a hole. Ended up reading about 180 reviews of the best-funded tool in the category. $116M raised, most of it this year. G2, Capterra, Trustpilot, the app stores, a pile of Reddit threads.
I expected the complaints to be about missing features. Nope.
A two minute check for anyone who lets a script, a CI job or an agent run commands in their repository. List the commands that ask before they do something. Then find out what each one does when nobody is there to answer.
Mine is the schema migration generator. Its job sounds like writing a file: compare the models against the database and produce a migration for the difference. To compare honestly it needs the database up to date, so if any migration has not been applied yet, it asks whether to apply them now. The default is yes.
Nobody reads that as dangerous, because there is a question, and the question is the safety. There is a second safety underneath it: the console framework checks whether it is attached to a terminal, and if it is not, it marks the run non-interactive, and a non-interactive run refuses instead of applying anything.
I read the code this morning to find out why neither of those had ever stopped it. The terminal check only runs if the input object has a stream to test. The ordinary input, the one built from the command line arguments, has none. So the check is skipped, the run is treated as interactive, the question is asked, and reading the answer hits the end of an input that was never connected to anything. The library treats end of input as no answer, and no answer as the default. Yes.
I keep seeing apps add smart generation buttons that just make the interface clunky. Extra menus, extra popups, and prompt boxes cover up what I was trying to do.
|Some tools solve real problems, but others just throw in smart shortcuts because it is trending. The worst part is when the automated option takes longer or feels less predictable than doing the task by hand.
Has a tool you used gotten worse after an update like this? Or has one actually surprised you by being useful instead of decorative?