22 ms·
Outdated vs. Complete: In defense of apps that don’t need updates
- TillE 4y agoThis is another case where Apple fundamentally doesn't "get" games. They had a plan for clearing out crap from their store which probably sounded reasonable, but nobody even thought about an entire class of programs. Lots of stumbles and missed opportunities - like, what if they had actually been serious about making the Apple TV a Wii-style games console? They have the hardware expertise to do that at a reasonable cost, but they just have no idea about the market, and apparently no desire to learn.
- musicale 4y agoI understand that Apple is trying to deal with the sort of shovelware/accumulation problem that the Wii had, but the blanket approach of culling games based on release date seems wrongheaded. If Nintendo took that approach then they'd end up throwing away Super Mario Odyssey and Zelda: Breath of the Wild.
- spullara 4y agoProbably not since they get plenty of downloads...
- themagician 4y agoOh, they get it. Apple products very much have a time and a place. Their plan is recurring revenue. Something that happened 3 years ago is almost entirely irrelevant to them. It's true with both hardware and software. Wii-style games on AppleTV would not be a win for them. They don't want to sell a few million copies of Wii Sports once every 3-5 years. They want you buying a new 99¢ game at least once a month. They want you spending $5-10 in micro-transactions a month. They want you subscribed to AppleOne for $15-30 a month. They want you to buy a whole new iPhone every 2-3 years and start the process all over again with some new AirPods, cases and bands in between. Apple doesn't want to sell you a new game for $59 every 2 years. They want to sell you what amount to an average of $59 worth of goods and services a month… forever. And while that sounds like a lot, that's a low target. If you have your TV subscriptions through Apple and Apple Care you can easily be contributing $100/mo or more to Apple's bottom line.
- _jal 4y agoApple is starting to remind me of auditors, but instead of trying to keep people honest/push trendy practices, they're pushing whatever's trendy in Apple's management class this month. When do we get to the point of companies hiring "review specialists" who used to work for Apple?
- jaywalk 4y agoAnyone who could afford a "review specialist" is probably already getting the white glove treatment this post describes, and wouldn't actually need one.
- mattgreenrocks 4y agoI am convinced the world doesn't understand the concept of something being "complete." It's like part of their brain can't comprehend that something is functionally whole, and any changes would actually detract from what is there. Related: open source devs fret if a library hasn't been updated in the last month, even if it is feature complete with no bugs.
- electroly 4y agoFor open source code, I think the concern is practical: bit rot is real, and libraries with no recent updates are more likely to have suffered bit rot. It's not that a library can't be finished, but that the world in which it lives never stops moving. It can be a bigger or smaller problem depending on the ecosystem. Old C89 libraries have a good chance of still working, because the ecosystem isn't moving so much any more. Old C# libraries almost definitely don't, because the ecosystem is moving quickly.
- forgotmypw17 4y agoPerhaps the solution is a monthly "NOOP" release?
- twicetwice 4y agomaybe commit to a log indicating that the test suite has run correctly as of <today's date>?this assumes you have a useful test suite but also at least indicates that you're still paying attention & trying to ensure your library works
- forgotmypw17 4y agoGreat idea!
- svieira 4y agoquid custos ipsos custodiet still applies. The fact that your test suite ran in Esolang v27.8 successfully doesn't mean what you-the-consumer want it to mean if the last supported version of Esolang is v96.2. It just means someone down-stack of you is committed to backwards compatibility.
- musicale 4y agoI don't think culling games/apps based on age is the right approach to improving discoverability. I don't see Nintendo removing old Switch games from the eShop. I don't see Apple Music removing the Beatles because they haven't updated recently. My recommendation, which Apple's (obnoxious) ad business would never accept, would be to 1. Remove the obnoxious and generally useless ads which eat up the top half of the first page of app search on the iPhone. 2. Improve app search with more options and a fast, responsive UI. Also they might consider allowing you to consider ratings from other sources such as critical reviews vs. user reviews (a la metacritic.) 3. Better human curation with more categories. This is the same approach that Apple Music takes and it seems to work well. Games should have Artist/Studio/Developer pages as well as Essentials lists to facilitate discovery. Same with genre/category essentials, which have a rotating list that can be saved/bookmarked.
- II2II 4y agoThe missing point is that they are culling apps based upon age and downloads. I think this is a reasonable criteria if Apple is trying to make space for popular and potentially upcoming apps. Yes, space is an issue if you think of it in terms of the customer's attention span. The real problem is that developers have no choice except to offer their app through Apple's store. There is no room for the developer to offer their labour of love or niche product in a storefront that better serves their needs, or even from their own website.
- musicale 4y ago> The real problem is that developers have no choice except to offer their app through Apple's store How is this different from other walled garden game systems/game stores like Nintendo's eShop? Yet they seem to keep older games and apps, even niche titles for a limited audience (such as music production apps or BASIC programming apps) which I greatly appreciate. I would agree that discoverability isn't great on the eShop, but there are dozens of enthusiast web sites which are pretty good for game discovery (also aggregators like metacritic.) And, as I noted, I think Apple already has a good approach which they're using with Apple Music - better human curation including category/genre/time period/artist/etc. playlists. Podcasts/radio shows also help. Many games (at least ones that aren't in the "live service" category) are more akin to movies, music, or books than to some sort of perishable produce, so a curation approach that balances older content with new content makes sense.
- Kwpolska 4y agoEh, this is Apple you’re talking about. They don’t know what backwards compatibility means, and your app might randomly break on the newest version of iOS. Or it might be slightly ugly around the Dynamic Island™ and Apple users would hate that.
- musicale 4y ago> They don’t know what backwards compatibility means Platforms are supposed to absorb developer pain, but Apple offloads a continuous and multiplicative update burden onto all of their developers.
- 0x37 4y agoI've personally witnessed several unnecessary and costly refactorings in my job that were done due to this weird perception the blog is talking about. All those weeks and months that were spent removing a perfectly fine tool that was working without issues.
- renewiltord 4y agoIn a world with security concerns, can anything be complete?
- hmcamp 4y agoYes. The ls Unix command.
- renewiltord 4y agoHaha you got me, but I wouldn't be surprised if there were Unicode issues etc as you have to support modern filesystems Like this https://www.exploit-db.com/exploits/33508 https://www.exploit-db.com/exploits/33508
- Gigachad 4y agoI’m not sure the ls command has to do much if anything to support new file systems since the file system driver should present a standard interface for them.
- 0x457 4y agoThe standard interface for paths on Linux is "bag of bytes", do you want to see bag of bytes or do you want to see human-readable path?
- Aissen 4y agoHere are a few implementations that did not get the memo: coreutils ls: https://git.savannah.gnu.org/cgit/coreutils.git/log/src/ls.c https://git.savannah.gnu.org/cgit/coreutils.git/log/src/ls.c freebsd ls: https://github.com/freebsd/freebsd-src/commits/927f8d8bbbed70f6c88d05c19b5b366f8e7532c9/usr.bin/find/ls.c https://github.com/freebsd/freebsd-src/commits/927f8d8bbbed7... busybox ls: https://git.busybox.net/busybox/log/coreutils/ls.c https://git.busybox.net/busybox/log/coreutils/ls.c openbsd ls: https://github.com/openbsd/src/commits/master/bin/ls/ls.c https://github.com/openbsd/src/commits/master/bin/ls/ls.c The latter seems to be the most stable, yet has been updated two years ago, many years after its first introduction.
- colonwqbang 4y ago"Planned obsolesence" as a matter of official policy. Any cultural expression older than a few years is not worth the bits encoding it. Meanwhile, GTA V from 2013 is still one of the top selling games on Steam.
- crazygringo 4y agoGTA V has been updated countless times since 2013, including entire re-releases for two newer console generations.
- colonwqbang 4y agoThe Windows port being sold at Steam is from 2015. But of course you have a point; there have been updates in the meantime. It's conceivable that those updates are what's keeping the game marketable. Still, I don't think Steam would confess to deleting a game just because it is old. They carry a lot of games which haven't been updated in years and which still sell.
- bsdetector 4y ago> My old code simply did not work anymore with the latest versions of Xcode. In other words if there was some actual reason to do an update, like a security flaw or serious bug, she wouldn't have been able to readily do so. This seems to support Apple's policy to make developers update the app every once in a while.
- layer8 4y agoApple is causing this issue in the first place by breaking compatibility and requiring projects to be updated for each new Xcode version.
- newtritious 4y agoThat’s because the platform is actually changing.
- layer8 4y agoThat’s not a reason, unless the platform is changing in incompatible ways, which is exactly the problem, and a largely avoidable one, as other platforms demonstrate.
- newtritious 4y agoOther platforms don’t care if applications fingerprint the device without the user’s consent. Closing off APIs that facilitate fingerprinting is just one of many incompatible changes Apple has been making. Some other reasons are deprecating power hungry technologies and asking for more permissions to access private data. These are changes that benefit users on a massive scale. Why shouldn’t a developer be expected to respect users needs?
- layer8 4y agoThere are ways to still maintain API compatibility in that case (Windows does it all the time), and it’s also not a reason to require projects not affected by those changes to recompile with the newest Xcode version each year. I’m maintaining a Swift library/framework that doesn’t use any iOS APIs at all, only basic Swift standard library calls, and I still have to produce a new build each year from unchanged source code so that the library can be consumed with the new Xcode version. That’s just insane.
- crazygringo 4y agoHate away, but in this case I'm on Apple's side here. The author may be the exception where no updates are actually needed, but that does seem to be the exception. In my experience, most iOS apps I've tried downloading that were last updated 2-3 years ago simply don't work. Apple requires an update in the past 3 years or else a minimum threshold of downloads. Presumably the latter is required so there are simply enough newer reviews to indicate whether it's broken (lots of 1-star) or not. These seem like pretty reasonable indicators that it's still working. > My old code simply did not work anymore with the latest versions of Xcode. So I had to spend four hours on Saturday upgrading all my platform libraries simply so that I could compile the damn app. Honestly that's just good hygiene. Because if they waited another 2 years, it might have taken 4 days to get the thing working. New versions of libraries come with all sorts of improvements, whether it's for accessibility or security or a hundred other things. It doesn't seem unreasonable to me that if you're maintaining software in a public app store, you should be able to compile it semi-regularly with new versions of packages.
- masklinn 4y ago> In my experience, most iOS apps I've tried downloading that were last updated 2-3 years ago simply don't work. Not sure what category of software that was but e.g. for games it’s usually not an issue. I used to have a bunch of games and game-adjacent software from the first AppStore year, we’re talking the time when you’d pay a buck for a virtual rain stick which’s use the accelerometer. They kept working until the 64b switch killed them. Rebuilding them would undoubtedly have been difficult for the author even if they’d not moved away from them, but because those’d use only minimal is features (raw-ish inputs, and setting up opengl) there’s basically nothing to break which would not be flagrant.
- musicale 4y agoI also had many games killed off by the 64-bit switch (on both iOS and macOS), but even after that a number of games that still worked were removed from the app store.
- 4y ago
- alberth 4y agoDon't forget "Feature Complete". It's a real thing especially when you're building something under the unix philosophy of "do one thing only, really well".
- BowBun 4y agoI couldn't really accept this blog post because the author doesn't even realize they benefit from Apple's walled garden: > Most people are trying to build well-designed, useful mobile apps and then proceeds to say how the review process is not helpful because they don't weed out many malicious apps. First, confirmation bias. Second, do they have any idea how things are in Android land? It's a constant struggle against nefarious app devs trying to abuse new technologies or means of getting ad/install revenue. It's one of the things I like the least about the ecosystem I use.
- WesolyKubeczek 4y agoIn an ecosystem like npm, having such thing is next to impossible. The useful libraries that don’t depend on anything else from npm are rare, and those that are need to review their lockfiles and run npm audit and whatnot every once in a while, even if their own code doesn’t change. Otherwise it’s quite a pain to integrate them with newer codebases. In any ecosystem at all: if it speaks HTTPS, it’s either never complete, or it ceases to function past some date. I get the sentiment very much, but there are cases when you can’t have nice things.
- layer8 4y agoGod, the UX in that karalof video is so much better than what iOS has become today.
- logicalmonster 4y agoI would advocate for Apple and other app marketplaces to adopt the carrot and not the stick. Incentive App developers who make good and substantial updates, whether its new features or updating to newer system APIs, with a positive % modifier to their search results in the App store. This way well-maintained Apps should show up higher in search rankings and there's a natural incentive for developers to keep their programs maintained. But at the same time, this would allow developers to call a program "finished" and leave it on the store without being scared of having their hard-work destroyed. Their hard-work might not be as visible, but that would be on them.
- GuB-42 4y agoHey, Apple, people still play Super Mario, they didn't change a single bit since it was released, 37 years ago. But there is one reason I somehow understand Apple stance. First is security, almost all apps are online now, and new vulnerabilities are found regularly. Super Mario has bugs, be no one cares, in fact, speedrunners have fun with them, because a NES is not online and there is nothing sensitive in there to begin with. Second is Apple's own fault: they break their own system and want you to make sure you keep up.
- bena 4y agoI don't think the Super Mario comparison is entirely fair here. Super Mario Bros runs on a single piece of unchanging hardware. Even when you play it on any other platform, you're playing it through an emulator designed to mimic the original hardware. And that's the case with all video game consoles. Even when the physical hardware changes, you're given the guarantee that it won't be breaking to the software. The few times that has not been the case has been notable. iOS devices don't have that guarantee. The hardware can have breaking changes. You software now has to contend with the fact that there is no guarantee that certain features may or may not be present. Things that were previously not customizable, now are. If you want your software to run on the latest iOS, it is at least partly your responsibility to ensure that it does.
- kcb 4y agoYet somehow I can load up 15 year old PC games on decade newer hardware pieced together from random vendors and it all works fine.
- bena 4y agoBut he didn't compare 15 year old PC games to iOS applications. He compared a 37 year old console game. You also need an emulator to run 31 year old PC games like Civilization on modern OS/hardware.
- jmbwell 4y agoLooking at the metrics Apple tracks in the App Store, it seems to me that "engagement" is all that really matters. You could have some huge number of happy users, but if they open the app only occasionally, you get numbers in red. Or you could have an app that solves an important issue but only for a small number of users, and you get numbers in red. If you're not releasing hits that people use all the time, you sink. If tons of people don't spend tons of time in your app, you sink. Author complains about the time required to update libraries, and that's an aggravating process, but that's just an unfortunate part of maintaining an app. The real issue, again it seems to me, isn't that you have to do a lot of work just to increment the version string; it's that, ultimately, modern content ecosystems are designed according to engagement-driven revenue models. And solid, simple, quiet, long-lived, useful or fun little apps simply can't thrive when all the sunlight is blocked by towering marketing-tech giants. IMHO.
- klabb3 4y ago> Looking at the metrics Apple tracks in the App Store, it seems to me that "engagement" is all that really matters. This has been the name of the game in ad tech like fb, Google and social media in general. I think two worlds are clashing with each other, where consumer tech is somewhat aware of the problems around mindless scrolling and addiction, but the growth & engagement mindset of the 2010s is cemented in the culture. Apple has little reason to follow this model because they primarily make money from selling hardware. Having a software platform that protects the user from this crap is a competitive advantage against Google, who depends on ad-based revenue. Apple seems to have an identity crisis, fearing they lose out on sweet subscription fees and ad revenue, now that most apps are free. This in turn is creating conflicts of interest, where they end up fighting their own customers. If regulators would bark and bite harder around anti-competitive behavior, it might actually force corporations to focus on what they're good at instead of everyone building their own mediocre walled gardens that grow like a cancer and eats the company from within. At least, that's my wishful thinking..
- noobermin 4y agoThey are trying, just look at gdpr. It's just not happening in the US.
- plorkyeran 4y ago> So I had to spend four hours on Saturday upgrading all my platform libraries simply so that I could compile the damn app. I sort of assume this is the actual point? Apple presumably wants to drop support for older versions of the SDKs, and that requires that app developers update to the newer versions. I think you can make a reasonable argument that dumping work on third-party developers to simplify things for themselves is bad, but the author's belief that it was simply pointless busywork is probably incorrect from Apple's perspective. I suspect the minimum download threshold to be exempt from this is _very_ high. Maintaining backwards compatibility for a small fixed set of apps doing things an old way is a categorically different problem from maintaining backwards compatibility for every app out there.
- bsuvc 4y agoThis is a great point, but if true, Apple should do a better job of communicating the reason, including specifics, not just say "your app is rejected because it is outdated".
- dahfizz 4y agoIf they have specific libraries or APIs that they wanted to deprecate, I think developers would understand that. But the current implementation of "anything 2 years old is too old" is arbitrary. If this was really about deprecation, they wouldn't have a "minimum monthly downloads" exemption either. This policy is just a way to clear out old, unpopular apps from the store
- tomxor 4y ago> This policy is just a way to clear out old, unpopular apps from the store Except popularity doesn't correlate with utility when it comes to apps. Probably only addictive games and social network apps will pass whatever arbitrary threshold has been set. This will harm any one off apps built to satisfy a niche purpose downloaded by a small set of users. Which Apple probably think are not important, like all of the little high street shops, except cumulatively they might affect a majority of users. Also if it's measured by "downloads" rather than "installed", then it could take out larger more widely used apps that are considered complete by both authors and users, but don't have enough daily new users to pop up on their radar as important enough... this is similar to the "maintenance" fallacy of NPM, where frequent patches = better, even though if your package is small and well written you should be making no patches as a sign of quality.
- armchairhacker 4y agoI hate to see a piece of open-source software abandoned and broken. But I love to see a piece of software “abandoned” and still working because it has been designed for long-term use and simply doesn’t need updating. That is how open-source grows. Because you can’t grow a codebase if you have to keep updating and fixing what you’ve already done. As you have to keep updating and fixing stuff, new progress slows and eventually stops. It’s the same for “codebases” like ecosystems/package repos and open-source in general
- api 4y agoThe use of recency as a proxy for quality or usefulness is one of the more perverse trends of recent years, but it's understandable. There is just so much of everything that a strong demand is created for any method of filtering. Of course I have to add that it does matter a lot for certain types of software. Anything that interacts with ever-changing APIs, hardware specs, and protocols needs to be kept up at least frequently enough to stay useful.
- t_mann 4y agoFrankly, isn't that just what you signed up for as a mobile developer? The WorldAnimals app would probably have worked perfectly fine as a web app, but then the author would have had to figure out payments and discoverability himself. That's what the App Store offers, and in exchange Apple gets tremendous power to tweak every nook and cranny to maximise their profit. I'm sure Apple has good commercial reasons for the process that the author has experienced. I think the real answer here isn't to try and beg Apple to be nicer to the small fish, but to instead use the "old", non-walled version of the web.
- Tijdreiziger 4y agoWell, no, a native app and a web app aren’t one-for-one interchangeable. Apple acts as a gatekeeper by only allowing native apps to be distributed through the App Store, so it is not unreasonable to ask that they refrain from making the process too onerous.
- neilparikh 4y agoIt doesn't apply here, but there are a few app ideas I have where I don't really care about payments or discoverability; I would need use native just because the features are not supported in iOS Safari. For example, here's a list of standards that the Webkit team has said that they have no plans to implement: https://webkit.org/tracking-prevention/#anti-fingerprinting https://webkit.org/tracking-prevention/#anti-fingerprinting (for me, WebBluetooth and Web NFC are the big blockers). Until those gaps are fixed, native apps are your only option.
- jaimex2 4y agoAnother day, another Apple rant about the walled garden. They know you wont leave, they know you'll put up with it.
- stabbles 4y agoOn a related note, I feel that some websites at are a point where they're complete, and adding new features makes the experience worse. Take Github: to me it feels that it's now at an optimum where adding new features that make it more social or more "fun" would simply make it worse. Similarly Youtube: tons of good material, user interface is fine. Then they introduced shorts, and to me it feels like these type of video's are simply not part of youtube's identity, adding them only makes it worse. At some point it might be best to stop adding new features and just agree that things are fine now as they are.
- koreth1 4y agoSurely it's possible for GitHub to add features that aren't related to making it more social or "fun," though? For example, they could improve their support for stacked PRs in a number of ways; that's an area that is far from fine at the moment IMO.
- _dain_ 4y agothey could show the linecount of each file in the repo browser
- dkarl 4y ago> The impact of the App Store Improvement policy is nonexistent for VC-funded companies. Not true. More often than not, our iOS releases get delayed hours if not days, while our long-suffering iOS lead patiently walks yet another green reviewer through the policies and our previous interactions with reviewers to convince them that our app is in compliance. Among other things, our app repeatedly gets flagged for failing to comply with rules that don't apply to it. This is usually resolved with a simple message to the reviewer, but depending on the turnaround, that can effectively add a day to the time it takes to get a bug fix out. Dealing with these bogus issues probably accounts for 5% of the productive time of our iOS lead. And this is despite keeping our release cadence slow (every two weeks except for the most critical bugs) and after we've made many reasonable low-to-medium effort changes in our app to stop triggering false positives in their tools. God help us if Apple ever went the Google route. Apple reviewers might be inexperienced and undertrained, but at least they're human and capable of talking through issues.
- deleted 4y ago[deleted]
- peterkelly 4y agoHow is releasing a new version every two weeks "slow"?
- deleted 4y ago[deleted]
- steve_taylor 4y agoIt’s slow compared to a continuous delivery process in which other dev teams (e.g. web) release multiple times daily.
- scarface74 4y agoSince when has releasing an application ever been as fast as releasing something that runs on the web? Besides, users aren’t going to be updating their app multiple times per day as they would a website that is continuously updated.
- ineedasername 4y ago>I think the asymmetry of App Review is still lost on Apple. For indie developers our hopes and dreams (and sometimes our finances) hang in the balance, for the App Review team it’s just another app rejection among tens of thousands. I know they think they get it, they just don’t. I really don't think it's lost on Apple or the app review team. They simply have no incentive to change and a captive audience in both developers & app users/buyers. Better customer service (to devs) on the app review process when there are issues, and continuing support for older SDK's, cost time and money and Apple does not see the value in that investment. Absent competition there's also no pressure to change this. There's effectively a duopoly in mobile software between Apple & Google. They don't even need to explicitly communicate with each other to act as a cartel, they just need to silently follow each other's lead. Android is at least marginally better for allowing-- through a few scare-tactics hoops to jump through-- sideloading of apps, but I don't consider that sufficient competition to overcome the duopoly label. Neither is Android's allowance of alternative app stores, no more than MS allowing users to install alternate browsers was sufficient to overcome their uncompetitive practices when it came to IE. The primacy of the Play store on initial setup & its extremely deep integration in the OS is difficult to overcome. Alternatively, I am slightly conflicted on this due to the security aspects of app installation. Mobile certainly isn't perfect, but the prevalence of malware seems significantly reduced from what is seen in PC's. (well, windows. MacOS is not as bad as Windows, but I've always considered that to be a produce of it's lower market share & therefore lower cost/benefit ratio for attackers.)
- User23 4y agoI’ve never even heard of anyone getting promoted by saying “this app is perfect, let’s leave it alone except for bug fixes.” The overwhelming incentive for everyone involved in most commercial software work is to continually make changes, necessary or not.
- jeffalyanak 4y agoI think there's something to be said about this in regards to consumer electronics as well. One of the oldest electronic devices that I still use on a daily basis is my ereader, which is a very early model. It simply does everything it needs to do, it's feature-complete. Unfortunately there aren't many consumer electronics that fall into that category and a huge portion of consumer electronics that end up in the dump are not physically damaged in any way, but simply can't run the latest software, firmware, or OS. Or else they're missing the latest wifi or cellular radios, high end cameras, wireless charging protocols, etc.
- SilasX 4y agoSimilar thoughts about my PlayStation 2 from 2004[0] that I still play Dance Dance Revolution on. I don’t have to worry about anything changing that breaks the experience. (Except finding a TV that minimizes upscale lag but that should have been a trivial thing for TV makers to get right.) [0] The PS2 platform is from 2000 but I use a miniaturized PS2 slim which was released and probably manufactured in 2004.
- jeffalyanak 4y agoActually, I realized that much of my _music_ equipment falls into this category as well. My mixer is an early example of a MIDI-controllable analog mixer but since the MIDI protocol is still ubiquitous, it still fits right into my modern workflow. New mixers don't really bring much to the table that am average person would need.
- jongjong 4y agoI can relate to the frustration of the author. I wrote an open source library which gets downloaded 50K+ times per week. At one point, I hadn't updated it in several months and people started asking if the project is dead... In fact, it wasn't updated in a while because it had been working perfectly and was built in a forward-compatible way; that makes it more healthy and therefore more alive than probably 99% of libraries on the internet. The expectation that software libraries or frameworks should break every few months is disturbing. I think this may be due to the fact that many of the most popular frameworks do this. I find that React-based apps tend to break every few months for a range of reasons; often because of reliance on obscure functionality or bundling of binaries which aren't forward-compatible with newer engine versions.
- testingwaters4 4y ago> built in a forward-compatible way What do you mean by this?
- tinalumfoil 4y agoI don’t know the details of your particular library but I think 50k/week downloads and no problems is an outlier. In my experience even projects with small audiences tend to accumulate outstanding bug reports faster than they’re fixed.
- oliveshell 4y agoI’m sure you’re right, but it sounds like it’s an outlier not by random chance, but because it was built carefully. I think there’s a useful lesson there.
- smaudet 4y agoBuilt carefully, extremely tiny, or single purpose. "Do one thing and do it well" - the unix philosophy, and why I still use cd, ls (dir on windows) today. If a project exceeds two functions its probably doomed to become either redundant or broken. If a project does one thing well, even if something else uses it, you can always decompose to it (your software is always useful, even when somebody writes the fancy bells and whistles version).
- NaOH 4y agoAs a user, there are two issues I could face from this type of culling. First, I keep older devices—maybe just for RSS or news apps or podcasts or in-car music or video players. Relatively simple, straightforward uses. If I have additional uses in mind, apps won't be available. Similarly, the same would be true for someone who wants to let a child use an older device for something like games. The other issue is the number of iOS hiccups which can lead to support documents saying to reinstall the OS. Doing that will make older, removed apps unavailable after reinstallation of the OS if the user relies on iCloud backups. This risk necessitates iTunes backups to insure such apps remain available after reinstalling the OS. I doubt a situation like this contradicts the overall value of the culling. But I do know it has an effect on me and there are some people—certainly, a small number—who will lose apps because of the shortcomings in iCloud backups.
- faeriechangling 4y agoI don't know why Apple is doing this if they want to maintain their monopoly, I only see them throwing fuel on the fire of the breaking up of the App Store for some pretty marginal benefits for themselves. They are literally targeting the smallest and poorest developers explicitly.
- 0xbadcafebee 4y agoDon't spend your time defending your app. Spend your time lobbying your representatives to either break up Apple or force them to open up their devices to other stores. Even Ma Bell couldn't tell you who you could buy a telephone from, who you could call, or what you could do on the call, much less take a percentage of anything you ordered over the phone. Enough is enough.
- scarface74 4y agoActually Ma bell could tell you who to buy a telephone from early on. They controlled what devices were allowed to be connected to the network.
- insane_dreamer 4y agoRequiring an update to ensure compat with the latest SDK/API seems reasonable. Apple has never maintained eternal backward compatibility (a-la-Microsoft), so that behavior is pretty consistent and known for devs on their platform. Having some rule that looks at number of downloads is unreasonable. That has nothing to do with compatibility or security.
- XCSme 4y agoThis is why the products I sell are in plain PHP + MySQL, nothing to really update as most PHP/MySQL language updates are usually backwards compatible.
- selfhoster11 4y agoAs someone who recently did a large classic LAMP migration: nope. Lots of things to break.
- XCSme 4y agoWhat exactly broke? With migrations there might be stuff like httpd.conf or mysqld.conf that don't get properly copied. But if everything stays on the aame machine, thinks rarely break by themselves, even when upgrading the OS, database, PHP version or web server.
- selfhoster11 4y agoThis was a huge upgrade. PHP <6 + MySQL 5 to the latest versions of everything (except substituting MySQL for Maria). A whole variety of scripts that used constants without quoting (`CONSTANT_NAME`), which later became a problem because the language mandated them in quotes (`'CONSTANT_NAME'`). We were finding those in various places literally months later. mysql_ family of functions was gone from PHP, so we had to patch files to include a "polyfill" snippet to translate those calls to mysqli_ MySQL (/MariaDB) itself was another idiot-fest because of the way it handles Unicode. This is a slightly too long story and would risk doxxing myself, so I will simply give you some highlights, and then ask you to imagine that everything that could go wrong, did go wrong: 1. MySQL storage engines have a fixed upper limit on how long an index can be for each row. For 4-byte UTF-8, that is an upper limit of 768 characters. 2. MySQL defaults to utf8mb3 rather than utf8mb4. 3. Unicode characters in column names are rarely a good idea. Apache, surprisingly, went relatively fine. I really don't like the ancient way it does things, but it's serviceable if you're fine with banging your head against the wall to do something that seems like it would obviously work.
- garrickvanburen 4y agoThere have been a couple times I’ve built software that just worked for years on end with no need for updating. Felt like magic both times.
- hcarvalhoalves 4y agoI agree. Some software from the past that made me feel that way: 1. Adobe Photoshop 7 Felt feature-complete, never ran into a bug, not resource-intensive (I would run it on a Pentium 200), no online activation/membership BS 2. Apple Aperture 3 Also felt feature-complete, had everything I needed. Nowadays I need to use 2 or 3 different software to have the features of a 2003 app. Unfortunately the app stopped working after 64-bit transition, and Apple retired it in favor of the much simpler Photos. Shame on you, Apple. 3. iTunes 10 Pretty much the sweet spot of features for managing your music library. Apple replaced with the Music app, because nowadays users consume streaming vs. maintain their own libraries, but the app is a buggy mess. 4. Winamp Solid, just worked. More software should be like that, but never will, because it isn't profitable to have users using the same version for many years. The revenue maximisation strategy is to release continuous beta-quality software, and apps should provide a steady revenue stream. That's why the Apple Store just assumes an app that didn't update is "abandoned". That's the perspective of users in general today, too.
- criley2 4y agoPhotoshop 7 struggled in larger PSDs with lots of layers or just a huge resolution/dpi. The memory management was really bad in that era too featuring manual scratch drive configuration. Constant crashing in large projects was the norm for me. I thought CS2 was a good upgrade and my final point before the nonsense of subscription based software took over. Now I just use photopea because 99% of my photoshop needs can be met by a single dude on a single webpage
- selfhoster11 4y ago> More software should be like that, but never will, because it isn't profitable to have users using the same version for many years. You can get some of it back with FOSS applications, even if the quality normally isn't the same as with old freeware/proprietary applications. At least with a FOSS application you get to keep it forever, unlike SaaS which evaporates into thin air the moment the parent company decides to pull the plug.
- badsectoracula 4y ago
- sylware 4y agogoogle forced gmail users to use a javascript web engine to re-authenticate their account then I wrote my smtp server, 5 years ago, did setup a pi with it, I don't recall adding/modifying anything since. I wrote my own video player based on ffmpeg/vulkan/x11, changes did happen mostly because of a core change in ffmpeg or for some workarounds for hls streaming since my ISP has really trash peering with live stream CDNs. I am still with x11, I use dwm and st, change are really rare. Don't forget, open source software is not immune to planned obsolescence, this seems very true with open source software with strong ties with "corpos".
- eternityforest 4y agoIt's Apple being Apple. I don't think apps that truly don't need updates are possible, because platform APIs will change, and if they read or write files, or talk to anything on the network, other apps will change and compatibility will need to keep up. But we shouldn't require updates for no reason, and we should probably be way more careful about messing with those platform APIs. Android and I assume iOS is much better than something like Linux, where "platform APIs" don't even exist and things are provided by stacks and stacks of distro, version, and customization specific things, so there's no reason stuff shouldn't keep working for years.
- ghoward 4y agoI think this applies to more than just apps too; it would apply to software in general. "Update or perish" is a bad model for software. https://gavinhoward.com/2019/11/finishing-software/ https://gavinhoward.com/2019/11/finishing-software/
- junon 4y agoI am a maintainer of Chalk (Javascript library for outputting color codes for terminals). We consider chalk 'finished' and probably won't release another major version that changes the API - perhaps just typescript maintenance as Microsoft messes with the language even further and we have to fix types. Sometimes, software is complete. I hate this new industry dogma that code rots over time and needs to constantly be evolving in order to be "alive".
- JoeOfTexas 4y agoI think when a project heavily depends on dependencies it is easy for security issues to make it too risky. Lately, I've been seeing more and more npm packages that keep "extending" a dependency to add more features, which eventually gets abandoned. I'll use this package, multer-s3-transform, as an example. Its been abandoned. It depends on multer-s3, which depends on AWS-SDK and multer, which then depends on busboy. Now, AWS-SDK, Multer, and Busboy have organizations maintaining them. However, the random projects overlayed on top of those are by single individuals. The answer is to two-fold. Avoid overlayed projects and avoid big projects managed by a single individual.
- junon 4y agoChalk has no dependencies aside from those vendored into the source tree.
- JoeOfTexas 4y agoI took a quick look at Chalk. I would say using yoctodelay dependency is kinda useless, and is maintained by a single individual. I sense potential danger there. The other dev dependencies should be audited too.
- junon 4y agoSo? They're dev dependencies. They're not needed to actually use the code.
- reilly3000 4y agoFor me it’s all about security updates, so it depends on the posture. If it’s not taking external traffic, non-critical, and does something simple, it’s probably fine to use an old version without a lot of concern. Otherwise I’d like to see at least a steady stream of dependency updates. With Dependabot and the like this is a relatively low effort commitment to merge its PRs when they come up. If there isn’t some security auditing on it and it’s serving on the open web it’s out of the question for prod IMHO.
- skybrian 4y agoCompare with media files. Music and movies don't expire. The most common audio and video formats will probably be supported forever. (Perhaps there are exceptions for obscure codecs?) It seems like this could be done for at least some games, but defining a virtual machine and binary format that's both good enough that game developers will want to use it, and at the same time stable enough that it lasts forever, seems like a challenge? Also, it needs to be non-networked, or it will stop working when the server goes down. This was done a long time ago for interactive fiction, but doing it for modern mobile games seems like a challenge. WebAssembly should probably be involved, but the user interface will need a huge API surface that's also stable.
- ChadNauseam 4y agoI think Wasm + WebGPU is probably very close to what you want
- selfhoster11 4y agoNo, thank you. I'd rather target Dosbox.
- heisenbit 4y agoNot only the file format. The content also gets supported and legal protections were extended and not shorted over the years.
- titzer 4y agoI want to make WebAssembly the Unicode of executable code formats, stable indefinitely far into the future. That requires backwards compatibility for all code format features and simple, stable APIs.
- fortran77 4y agoAnd despite all of Apple's efforts, the number of misleading, scammy, or useless apps in the app store is huge. I don't search the appstore any more. I have to see a link to the app from a trusted source.
- michaelsalim 4y agoReminds me of a game I published on the play store. Years after, I got an email saying that I needed to do something (don't remember exactly what), otherwise it'll be removed from the store. I was busy at the time and it wasn't that great of a game anyway. So now it's gone forever. It's things like this that discourage me from developing anything mobile.
- sriku 4y agoTotally relate to the OP. I recently got my app kicked out of Apple App store for not being updated to the latest SDK. No patience or time to change programming language. layout engine, audio API, graphics, screen sizes etc. I just said "screw that" and now point people to a crippled-but-usable web version of it instead when they ask. My app is 5+ years old and I basically considered it "done". It came to be exactly how I wanted and nothing more .. and users kept discovering new possibilities even after years of usage. It's a metronome https://talakeeper.org https://talakeeper.org .
- robust-cactus 4y agoSoooo the wild thing is, apple gets more aggressive with it's app store policies the larger you get. Some small feature that may have been ok at a million users may be seen as inappropriate when you hit 10 or 100 million. Their requirements just balloon and they just get more and more annoyingly involved in your business.
- lawgimenez 4y ago3 years without updates? What would it take for the author to download the newest Xcode and compile? It won't take me a day. If you're in the mobile development space, you have to keep up and compile with the latest as much as possible. This is the way to get Apple and Google off your ass.
- lapcat 4y ago> What would it take for the author to download the newest Xcode The author is a professional mobile engineer and has the newest Xcode. The app is an old project not related to the author's current job.
- lawgimenez 4y agoYes I am aware it's a hobby project. But nonetheless, same as every mobile project uploaded on the App Store, it should be updated frequently including the dependencies.
- lapcat 4y ago> If you're in the mobile development space, you have to keep up > This is the way to get Apple and Google off your ass. The article author has a full-time job as a mobile developer, does keep up, and is not lazy. Your comment was insulting. > Yes I am aware it's a hobby project. You show no recognition that people are busy and have better things to do than to constantly update a hobby project to satisfy Apple's whims.
- lawgimenez 4y agoIs updating once a year considered constantly updating? That's the least a "professional" iOS developer should do.
- lapcat 4y ago> Yes I am aware it's a hobby project > That's the least a "professional" iOS developer should do. You continue to show no recognition of the situation, and you also continue to be insulting by putting "professional" in quotes.
- Jenda_ 4y ago> I was essentially told that I hadn’t updated my app in three years and now it counts as outdated. I needed to update the app within 90 days or it would get automatically taken down. There are "obsolete" devices that require Internet Explorer 6 with some ancient Java or ActiveX for configuration. I have a Windows XP virtual machine for this. Recently, there was an article about someone servicing trains using Windows 98 https://news.ycombinator.com/item?id=32884814 https://news.ycombinator.com/item?id=32884814 Nowadays, devices are configured with a smartphone app. In a few years, the apps will all be unavailable, and there will be no possibility to use such devices.
- xwdv 4y agoHere’s a cheap trick: update the version number of your app regularly even if there’s no real change. People will be convinced the app is still fresh.
- mips_avatar 4y agoAt least in Microsoft it’s very bad for your career to be involved in a “complete” project. Most Windows code just hums along doing it’s thing generating value and not breaking. But that value will never counted in a performance review of any engineer/manager.
- ano88888 4y agoAs a developer myself, I can relate to the author and hope that app review process needs to be reformed to give more power to the developers. As a consumer user, I have to say that I will actually prefer the apps to be updated and usable in my new devices.
- CharlesW 4y agoRandom note: I loved "malicious apps are relatively rare; arguably, Apple doesn’t do a great job filtering them out anyway". We sure are lucky that bad actors only target Android!
- perryizgr8 4y agoThere is a simple solution to this issue. Since Apple's distribution is not working well for these app developers, they should choose another mechanism that suits their purpose better. They can simply choose to distribute binaries for all the machines they like to support. As long as the target platform APIs work, their app will continue working for anybody who wants to run it.
- nathan_f77 4y agoI've been thinking about this topic for a while. If I ever build any kind of language or framework, I would prioritize backwards compatibility and make sure I don't waste anyone's time with unnecessary changes or deprecations. I've also had to archive a few of my mobile apps and remove them from the App Store because it just wasn't feasible to get them running again. I've adopted this practice with my SaaS startup (docspring.com) out of necessity, since I never want to change anything that might break a customer's templates or API integration. I also never remove or rename any database columns. It's been totally fine! I have a handful of feature flags sprinkled through the code, and a solid test suite that makes sure I keep supporting legacy behaviours. It has never bothered me. I don't understand companies or maintainers who are constantly changing things and breaking stuff. I had a look at a Ember.js project recently and wanted to update everything to the latest version. I couldn't believe how many dependencies were broken, and how painful it was to even migrate to the next minor Ember version. Why??!?! What are all these extremely important changes people are making? The same goes for Rails, React, and every popular library. It's just a treadmill of things constantly breaking for no good reason. But if you ignore upgrades for a while and fall behind, then suddenly a security vulnerability is announced and you've gotta spend the next 1-2 weeks upgrading libraries just so you can fix the vulnerability. I had the idea to start a "upgrades as a service" development agency. We would monitor all your Dependabot PRs and fix any broken CI builds, and make sure you stay up to date. I wanted to build an automated code-mod tool that would know how to upgrade libraries between versions. Especially for simple things like a method or class being renamed. I'd really love to be a customer of that service if it already exists. I waste so much time on this when I should be building new features and fixing bugs. Maybe GitHub Copilot will be able to handle it one day.
- martin1975 4y agoImagine my shock, Apple's being greedy....
- ArcMex 4y agoInteresting argument. If you take a look at Sublime Text packages, you will see that some of them were last modified years ago but they are still downloaded and sometimes even trend according to the packages site metrics. You then have to ask, can I trust these packages? Or do I look elsewhere like VSCode on Neovim whose extensions and plugins are often regularly updated and maintained in comparison?
- account-5 4y agoHaving read this I can only assume apple is trying to gouge money as usual. No recourse for the developer but to waste their time and money on a pointless number update. Were I developing an app I would never target an apple device, and anything I developed would be in the same vein and the article's app. At least with android I could develop an app and target the fdroid store.
- cf 4y agoOne thing also to keep in mind is it's often hard to keep a project working because the ecosystem evolves around the project. So updates are needed just for existing functionality to remain. Features and APIs are deprecated/ removed from libraries, and if you don't update your project stops working in most user environments.
- deleted 4y ago[deleted]
- masswerk 4y agoSo, what self-respecting programmings languages are there that wouldn't offer some new syntactic sugar every year so that you can keep your codebase up-to-date? ;-) (Basically, programming is all about engagement nowadays, like with everything else.)
- janandonly 4y agoMaybe I misunderstood her, but she says it cost her several hours to rewrite her code to be able to compile her app again for the newest iOS and iPadOS versions. Doesn’t this imply that her app would not have worked on the latest OSses? In other words: if she had done nothing then her app would not work on newer devices? If so, then isn’t it useful for apple to warn her about this?
- jerrre 4y agoYou misunderstood. Otherwise the whole article wouldn't make sense, she clearly states that it still works fine on new devices. Compiling with the newest versions of the libraries/tools can be a lot of hassle including downloading/instaling multiple GB's The newest OSes will run apps made with earlier versions of the libraries/tools fine, up to a point of course.
- vkoskiv 4y agoEarlier this year I set out to completely rewrite an old project[1] using minimal, battle-tested dependencies to avoid having to constantly patch code rot associated with more modern languages and toolchains. The rewrite[2] is now complete, more performant and lightweight than the old one, and I'm confident I won't have to touch it much, if at all, and it will compile and work in 20 years. [1] https://github.com/vkoskiv/NoMansCanvas https://github.com/vkoskiv/NoMansCanvas [2] https://github.com/vkoskiv/nmc2 https://github.com/vkoskiv/nmc2
- teddyh 4y agoThus spake the master programmer: “Though a program be but three lines long, someday it will have to be maintained.” — The Tao of Programming, Geoffrey James
- arcticbull 4y agoThe only app that doesn't need an update 2-3 years later is one that runs on a VM.
- c3534l 4y agoIt seems like not a day goes by without someone writing an article about their experiences dealing with well-meaning, but none-the-less insane policies and procedures of the apple app review process.
- fullstackchris 4y agoThe real problem is that any native developer is essentially slave to Apple or Google's requirements (or both!). Where or how did we go wrong with native development and applications? Its all owned (and thus gated) by these industrial behemoths. The web, for example, is a much more 'open' platform. There needs to be an open platform like the web that can be used on mobile devices.
- jimkleiber 4y agoYup, my very simple/basic/i-thought-forward-compatible app broke when the stores required 64bit only. Maybe that's a simple change, but I can imagine how more complex apps may break much more frequently with OS changes.
- butthatsit 4y agoWhat's wrong with the web on mobile devices? PWAs are going to get better support even on iOS now. What remains to be done?
- JanSt 4y agoBluetooth on iOS is one example
- AshleysBrain 4y agoGenuine question: what would it take for a lot of indie mobile developers to move to the web? It seems app stores are pretty punishing with their capricious rules and high fees, and the web avoids that with greater freedom, better backwards compatibility, and lower fees. Some of the tech was flaky 10 years ago, but a lot of web tech is impressive now, and still advancing (e.g. WebGPU and CSS container queries). I guess discoverability and monetization are key points, but what about free art projects or small games built as side-projects and such? It seems to me they wouldn't have much to lose and a lot to gain by moving to the web.
- zac23or 4y agoI see some people defending Apple. Bizarre. The support Apple has in the most absurd decisions led me to classify it as a religion, not a company. Apple is a trillion dollar company with over 154,000 employees. Apple has the resources to keep the code for two years, DOS programs still work on Windows 10. The decision is arbitrary, someone who doesn't understand software has a lot of power over Apple.
- scarface74 4y agoHow well do your DOS programs run on Microsoft’s successful mobile platform that doesn’t have swap, limited memory and has 24 hour battery life on the latest processor node?
- BjornW 4y agoA similar thing happens in the Open Source WordPress plugin repository. All of my WordPress plugins are free & Open Source. Most are tiny plugins using functionality (filters, actions) part of WordPress core. Unless WordPress becomes backwards-incompatible they will function perfectly fine for the foreseeable future. From my perspective these plugins are feature complete & unless there's a bug, don't need any attention from me. Sadly the WordPress repository expects me to update the version number or else the plugin will be become less visible in search results and a notice will be placed above the plugin's title stating: "This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress." So for some of my plugins I occasionally 'bump' the version number to make sure people can still find it in the search & for some plugins I just leave it be because I have better things to do. However it didn't feel quite right to keep people using my work in the dark, so I've added a text to communicate this to them. This is the text from my 'Redirect To Homepage' plugin: "Is this plugin actively being developed? Yes and no. Let me explain: I consider this plugin to be feature complete and unless bugs are found there will be no development on this plugin. In other words this plugin is in maintenance mode and will be maintained for the foreseeable future. Due to other obligations I’m not always able to keep up with WordPress version’s and updating this readme’s ‘Tested up to’ version number. However, unless WordPress significantly changes the way the login_redirect filter works it should work perfectly fine even though the ‘Tested up to’ might be of a lower version number. As always, when in doubt, test it (and when it does give you issues, feel free to leave a comment)." I think this balances both interests, those of people using (perhaps depending on) my work as well as my own. A similar approach could be used by commercial app stores to restore autonomy & balance interests.
- cybrox 4y agoIn our case, Apple actively destroys user experience with this kind of stuff. We have an old iOS app for our products that runs fine even on the latest version and while there is a next gen app available that most users have switched to, some prefer the old one. For some use-cases, even for new users, the old app just fits a lot better. We cannot rebuild and republish that app, because it depended on third party software that we no longer have access to. The app will continue to work fine for users that own a correspinding device but will most likely be removed from the app store for no real reason in a few months. This will force all userd that want to actively use it to switch to the next gen app that they maybe don't want as soon as they add someone new to their device.
- ydlr 4y agoDoes removing a program from the apple store also delete it from users' telephones?
- cybrox 4y agoI don't think so, no, but I don't think they will be able to sync it to a new device when they buy one. In our case, the apps are linked to hardware that the user owns and shares with multiple others. Due to very restrictive changes in iOS background activity over the years, we had to restructure some of the functionality, so the apps are not really interoperable. I think in this case, as soon as the user wants to add a new user to the device or an existing user gets a new phone, all users tied to that device would have to switch to the next gen app to keep having a consistent user experience. This is not the kind of experience we want to provide for our users but we simply cannot invest as much money as would be required into completely mitigating the effect of Apple's decisions (such as heavily restricting background activity) year after year.
- loufe 4y agoIt is ridiculous that not all apps are held to the same standard. Before traveling with my partner recently we decided to buy some of the top paid games from the App Store on her iPad. A bridge building game I wanted to get into that cost maybe $5 CAD had severe scaling issues which meant I frequently couldn't see elements. Why should high purchase count work TOWARDS exemption from updating and not AGAINST? The more people who use your app should mean more frequent updates, in my mind.
- t43562 4y agoIt's just as well to produce releases every so often to prove that its' still possible. That is an aspect of safety - lets say some security problem arises in a library that your code uses - the more uptodate your code the greater the chance that merely updating the library will fix the problem without forcing an update of your app.
- eadmund 4y ago> the update description mentions the evil rival mobile platform Do Apple really forbid apps mentioning that they are also available on Android?
- greyhair 4y agoPWA Oh, that's right, Apple doesn't fully support PWA, because it breaks their rent model.
- dusted 4y agoI recalled having a bit of an argument with IT at a previous position, I wanted netcat installed, they told me no, since they didn't have any good arguments they told me it hadn't been maintained, I told them it was because it was done.
- deleted 4y ago[deleted]
- HeavyStorm 4y agoI don't know what more evidence we need that iOS and Apple are rotten and regulation is necessary. Too bad legislators are walking at a turtle's pace. Were the platform open to competition, we could have multiple stores that would have better policies. It would still elude the common user, unfortunately, but it would be a solution.
- scarface74 4y agoSo you’re going to “legislate” that Apple must maintain compatibility forever?
- devopsexpert 4y agoThe frustrating thing about software is that we still haven't quite mastered knowledge transfer to the point where you can exclusively communicate through code all of the information about a given piece of software. As long as you are depending on the software, all that matters is what it can currently do, which you can learn from the source. If it's been so long since the original developers left, whatever they originally intended it to do is probably either no longer relevant or already known to all users.
- wiseleo 4y agoThis helps to drive iOS updates. My iPad 4 is locked to iOS 10.3, so I can't easily download newer releases of apps. I am aware of being able to "buy" an app on a newer device and then download the last compatible version on that iPad. This policy could impact that ability.
- egberts1 4y agoIn offense to apps that do not get updated, notably on Apple App Store: You must update the software to show what the privacy levels are. Apple App Store mandates spelling out how the users’ data are being used starting in 2021. Sadly, this only applies toward new updates. Hiding behind how our data are being used … by the virtue of not updating your app … is not a defense.
- kderbyma 4y agoApple and many other services are truly becoming unhealthy for the society at large. not individuals, but the global ecosystem. they are destroying information at a rate that is almost unprecedented. I think they probably burn a library worth of information pretty frequently and just move along after salting the earth.... I see it with all sorts of platforms that claim to be innovative....they are so short sighted and think they can subtle hide their greed...
- PovilasID 4y agoWe built an Android app long time ago. When GDPR came in we did not need to do any code work because we respected our users data upfront. Only thing we needed to do is add a link to policy. And people are still using it. Crashes do happen but it's rare. So it's frustrating to get proded to update it.