Hacker News new | past | comments | ask | show | jobs | submit login

So it seems that you have never worked in a real company, where it can't easily be done to make a major technical rework of some components in a 3 months timeframe. With debugging, conception of a fix, implementation and testing, it is not often possible.

Teams are also not standing by to be available anytime for such works, often those apps are being worked on with contractors.




> So it seems that you have never worked in a real company,

Pretty much all of us who are posting here, even many of the students, have in fact worked at real companies. Perhaps you mean to say that not all of us appreciate that some organizations are a mess and simply cannot design and release a feature in a 3 month timeline even with a year or two of deprecation notice.


Most companies (and banks) seem to manage alright, without their apps breaking, or their customers being given inane advice. Or is this not your experience?


There are at least 3 in this thread that have made a warning, there could be others. It will most likely happen to apps using some special features (security, connectivity, ...), not to the most common table view.


If an app has "security, connectivity" as important features there is a greater not less an onus to keep abreast of platform changes and ensure your userbase isn't exposed.


Banking apps have always been the bottom of the barrel to me, with many (non critical) bugs taking months to get fixed. Gov. apps and utilities app come second and third from the bottom.

My personal experience is, many mammoth companies are not managing that alright.


It's fairly reasonable to assume a new major iOS version will come out around September or October every year, with multiple betas before the final release.


The question is more what to do when you find a major issue from let’s say the third or fourth beta, and your dev company tells you refactoring is needed and it will take 3 months to ship.

I feel most people’s opinion in this thread stops at “just don’t be in that situation”


It’s very unusual for major technical reworks to be required as a result of a new version of iOS unless you’re using APIs that have been deprecated for a long, long time and have been kicking the can of migrating to the new APIs down the road for years.


The companies that care have dedicated iOS teams that work on precisely this. Perhaps this bank should funnel some of the outrageous sums of money they presumably skim off the top and spend it here?


Depends on how much their users actually use it. Maybe the app is just a gadget and not their main business tool.

Most companies with such kind of app usage won't have a team all year round for their app and will work with contractors on a project basis.


Sounds like "app doesn't work on iOS 16" would be an appropriate thing to get a contractor team to fix?


And every client of every iOS contractor is asking the same "please check and fix" within the same 3 months (2 of which are also during summer holiday period in many places).




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: