--> "It's not a proper patch unless it breaks something." -Anonymous

When computer programs, equipment, or other projects take too long to complete, sometimes they get rushed out early. This often results in an ObviousBeta of which [[WhatCouldHaveBeen we'll never see the finished version]], but when the program is good enough to stand on its own two feet despite all the bugs and unfinished features, the programmers may be able to [[AuthorsSavingThrow fix it the way it should have been]] with a patch or upgrade.

But sometimes it doesn't stick, and the result has the users feeling like they're participating in (and paying for) one big beta test that never seems to end. Often by the time it feels finished, they'll have a sequel out, [[HereWeGoAgain and it starts all over again]]...

While this usually applies to RealLife software and VideoGames, it can just as easily apply to complex machines and other devices in works of fiction. See BetaBaddie and PsychoPrototype for this taken to a more dangerous level, and SuperPrototype for a subversion of sorts, though they sometimes have problems.
----
!!RealLife examples:

* Microsoft is often accused of this with varying levels of truth. With its monopoly weakened by users outright refusing to adopt Windows Vista when XP still works just fine (repeated with Windows 7 users refusing to upgrade to 8), and the increasing popularity and variety of alternatives, the company might be starting to clean up its act. They have been through more than one DorkAge before, though. (see: Windows ME)
** Although, Service Pack 1 fixed a bunch of problems with Vista (which is why most businesses wait for the first Service Pack before adopting a new Microsoft OS). Microsoft tried to get the word out that [=SP1=] was actually pretty good with the Mojave ad campaign, but it didn't manage to fully vindicate Windows Vista's reputation.
** Windows Vista Service Pack 2 is pretty much rock solid. All of those nagging bugs are gone and it just ''never crashes''. The only problem is that it was released on the verge of Windows 7, which is essentially Vista with said service pack and a new taskbar. In fact the whole reason for Windows 7 was to get rid of the Vista name and start with a clean review slate after they fixed all the errors.
* This is pretty much the case with ''any'' operating systems keeping up to the evolution of hardware. Sometimes developers can't simply make new drivers for new hardware (i.e. due to change of paradigm in hardware design), which means the developers must alter the core (the "kernel") of the OS itself. This is [[{{Egregious}} especially noticeable]] with open source operating systems such as [[UsefulNotes/{{UNIX}} Linux and the BSDs]], that requires you to update what is basically the soul of the system (not as painful nor as dangerous as it sounds).
** Debian, a Linux distribution, has an ''unstable'' branch that is ''meant'' to be this. Almost all packages are first uploaded to ''unstable'', which contains the latest bleeding-edge versions of all software, before they enter the ''testing'' distribution, which, in time, becomes the next stable release.
** Most Linux distributions have the option to use "bleeding edge" repositories, ensuring the latest untested software is used for updates as soon as it's available.
** The [=BSDs=] tend to favor stability.
* A TropesAreNotBad example: many players cannot ever foresee Notch, the creator of ''VideoGame/{{Minecraft}}'', ever letting his creation be truly "finished", even after the game [[https://twitter.com/#!/notch/statuses/136078211284090881 went gold]], and far, ''far'' after the game had become a stable experience.
** Notch he has stated that he wants to include a variety of base features, then release a finished game and essentially turn it over to the modding community. With Mojang announcing their next game, Scrolls, and ''Minecraft'' quickly reaching beta 2.0 status, some fans have speculated that this will happen sooner rather than later.
** Minecraft left Beta and went into its first "finished" version on November 18th, 2011, and it is ''still'' getting updates. Since the full release we have gotten Jungles, ocelots and cats, a new AI system with loads of new behaviors, [[WhyDidItHAveToBeSnakes creepers being afraid of cats]], a new type of golem, new blocks and items, upside down stairs and slabs and even a doubled build height and the ability to have ''thousands'' of different block and item types from mods. Mojang is gearing up to make life easier for modders and players who use mods.
* Not only do nearly all {{MMORPG}} titles release patches, but also new areas and quests.
** For example, powerhouse ''VideoGame/WorldOfWarcraft'' still receives periodic patches that can, in some cases, dramatically alter the entire game. Every single class has been renovated multiple times, entire concepts have been introduced, tinkered with and in some cases finally abandoned if they didn't work right. ''VideoGame/WorldOfWarcraft'' right now, post-Cataclysm (which renovated the entire "vanilla" game world) is practically unrecognizable from its original launch, even ignoring two expansion packs' worth of new content.
** And {{M|ultiUserDungeon}}UDs before them; since they're free to play, they could openly admit they're a perpetual work in progress. In reality, the vast majority of MUD projects die out without ever reaching anything like an even baseline feature-ful, balanced and fun-to-play status; only the real dinosaurs or clones thereof tend to reach the modern polished MMO level of "all systems go, now let's start dreaming up new content." By contrast, MUSHes, their roleplay-intensive counterparts, tend to have established mechanics from the outset that resist change, partly because many directly yank their rule systems from tabletop {{Role Playing Game}}s.
** ''EveOnline'' features an interesting variation on this. Aside from taking game-changing patches and enormous content additions UpToEleven the developer runs a test server available to all subscribers and actively encourages players to help them beta-test the next patch, making the test server a literal PerpetualBeta. This comes partly due to their development strategy, which treats the game as a constantly-evolving entity rather than a 'box' that will eventually be replaced by another box.
*** Many [=MMOs=] are following this model, with public test servers to increase the likelihood of game-breaking bugs being squashed prior to release. Examples include ''VideoGame/FinalFantasyXI'' and ''CityOfHeroes''.
*** With ''VideoGame/FinalFantasyXIV'' screwing the pooch terribly on worldwide release, the game has been in perpetual beta ever since, with no monthly fee while the developers rectify the (many) obvious problems with the game. However, the game was finally re-released as ''A Realm Reborn'' AKA patch 2.0 and the results of the bug squashing showed. Of course, with the game properly fixed, subscription fees came back.
** Most localized Korean, Japanese, Chinese and Taiwanese FreeToPlay [=MMO=]s tend to stagnate at the Open Beta phase long after the parent version has officially gone gold. This could be due to publisher policy, however.
*** They tend to lag behind the parent game by several months in general simply because of translation needs.
* After 7 years, ''VideoGame/DwarfFortress'' is still in ''alpha'', and the [[GoodBadBugs bugs are considered all part of the game]], which includes [[{{Hyperspace Arsenal}} Quantum Stockpiling]] and [[ChunkySalsaRule the Dwarven Atom-Smasher]], and other bugs can be used to engineer unique traps, such as the combination of magma and the (now fixed) low boiling point of water to create a Dwarven Microwave. The typical DF release cycle is a major update with lots of new features and usually an equal number of bugs, followed by a flurry of bugfixes and minor additions and a long and more or less stable period while its creator works on the next bunch of new stuff.
** Unlike most of the examples on this page, there's a clearly-defined list of development goals on the game's website. It's just that WordOfGod estimates that achieving all of them, in addition to anything the userbase think up that Toady One deems sufficiently cool ([[TheDevTeamThinksOfEverything in the highly unlikely event he hadn't already thought of it]]), is probably going to take ''anything up to twenty years''.
* ThisVeryWiki ([[TheOtherWiki and others]]) for that matter. Pages are never really 'finished' and there are always new features and changes being made.
** The scope and the implications of perpetual WIP is discussed in [[http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_is_a_work_in_progress this article]]. This is mindboggling: for as long as new humans are born, there will always be something to add to the body of collective knowledge, assuming Administrivia/ThereIsNoSuchThingAsNotability.
* Pretty much every {{Facebook}} game has a big, shiny "Beta" on their logo.
** Facebook itself is being continually renovated over time. Every time they substantially overhaul one of their core features there will be thousands of people complaining about it - all of whom have forgotten about the whole thing a week or two later. This has happened so many times as to be a RunningGag.
* Website/{{Google}}'s mail service, [=GMail=], was in "beta" for so many years that, when it finally got to an official version, an experimental tool was eventually introduced for the sole purpose of restoring the "Beta" to the logo.
** Google inverted this for many years, calling many of their products "beta" when they were fairly solid, just in case.
** As does their Translator, although this is mainly because new languages (whose translation algorithms often ''are'' in need of testing, at least initially) are added at frequent intervals.
* ''VideoGame/NeverwinterNights''. ''VideoGame/NeverwinterNights 1'' has lots of patches, but by the time they released ''VideoGame/NeverwinterNights2'' there was still a bit left unfinished. Community modules and patches provided lots of content and scripting the original developers didn't. There were engine problems as well (such as characters meant to be flying being treated as if they were walking as normal, thus setting of things like pressure plates connected to traps).
* ''{{Furcadia}}'' is in perpetual ''Alpha'', according to its designers. It's still good enough to work.
** There is a joke amongst the fanbase and devs that it will leave beta right after the heat death of the universe.
* Creator/ArtixEntertainment updates all of their games regularly (once a week for most, monthly for some), so the games are never truly finished, and there's always new bugs discovered and fixed. Also, because it's impossible to test the games with thousands of simultaneous players otherwise, all of their games are made available to play before they're officially "complete"; in particular, ''VideoGame/MechQuest'' was opened to all players in a "Gamma" testing phase because they didn't have time to do a beta before wanting to release it. It worked fine, though, as the team is prompt about bug fixes. In a sense, then, all of their games are perpetually in beta, although their older ones like ''VideoGame/AdventureQuest'' and ''VideoGame/DragonFable'' have been around so long there no longer are {{Game Breaking Bug}}s introduced with every update.
* ''PlaystationHome'' has been in open beta for ''over two years''. PennyArcade once spent a podcast talking about how the program will never, ever leave beta so that it will be impossible to criticize; "I mean, come on guys, it's just a beta."
* Every sports game, but particularly wrestling is one of these because they often are titled for the year after they are released, but by that year, many people who were present in the company during the development stage are no longer there, yet are still in the game, and people who've joined since aren't in the game. As a result they usually represent a brief period of time where anything could have changed. ''WCW Thunder'' and ''WWF/E Smackdown: Just Bring It'' are particularly notable examples of this.
* ''VideoGame/TheSims 3'' is ''very'' guilty of this. Bugs are endemic to the game, and they range from "amusing" to "{{game breaking|Bug}}" -- some of the most notable ones are "hotspot" nightclubs that are deserted, the mutilation of the Photography skill and an inventory bug that eventually froze the game. Players have to constantly check the site for patches and pray that the patch will fix their particular batch of problems. Unfortunately, each patch tends to cause almost as many problems as it fixes, and that's before the newest expansion pack arrives to wreak havoc on your game. The developers seem to be playing a never-ending game of whack-a-mole with every new installment. By the way, if you think you can dodge the problems by avoiding the patches, you can't - each new expansion pack requires you to update to the latest version of the game. And heaven help you if you have custom content installed.
* ''VideoGame/DragonAgeII'' had to be patched almost immediately after its release, and issues are still ongoing. Several quests have only recently been made accessible, and combat is still being tweaked. One major fan bugbear is the cameo of the Warden's love interest in the previous game - Leliana and Zevran either act as if the Warden is dead (even if they survived), or fail to acknowledge their relationship with the Warden (for example, Zevran will accept Isabela's offer of sex, which he is not supposed to do if he's involved or in mourning). Developers claim that this issue is too deeply embedded to be resolved any time soon, and {{DLC}} tends to cause its own set of problems, so players remain braced for more bugs.
* ''VideoGame/FalloutNewVegas'' was first released with great fanfare, with the game scoring very well with most reviewers. However, the developer Obsidian, [[KnightsOfTheOldRepublic as they are known to do,]] did not run proper dfebug routines. The game on release was so crash-prone as to be unplayable at times, a problem that still persists in some parts (the final battle sequence come to mind) after ''four'' major patches. That's not even getting into the faction paths cut off by bugs or scorpions that get stuck in the ground due to clipping errors.
** With ''Ultimate Edition'' announced and all DLC released, support for ''New Vegas'' is essentially over, leaving multitudes of unfixed glitched, ranging from crash-to-desktop game breakers to bookkeeping annoyances (Why are the three helmets from ''Lonesome Road'' the only "Heavy" headgear in the game? When [[PoweredArmor Power Helmets]] are "Light?").
* ArcenGames actually build their business model about this, but their site makes sure buyers know what they're in for. Games at release was feature-complete, fully playable and almost bugless. However, the company knows they could do a lot more and continues development for as long as community interest persists, constantly adding beta updates and periodically pulling back to clean out bugs and release a stable update. This has actually worked very well for them, AIWarFleetCommand has been operating like this for years (all the way to and past official ''6.0'' release, with patch notes approaching novel length in total), with occasional larger chunks of new content released as paid expansion packs to keep the company going.
* Arma II mod ''VideoGame/DayZ'' has been in beta since launch and has been met with constant updates and patches to smooth out the gameplay. The developers of the mod plan to release the mod as a stand alone with revamped features instead of copying over Arma II's gameplay.
* Wolfire's ''VideoGame/{{Overgrowth}}'' has been in ''alpha'' since November 25, 2008.
* Website/ArchiveOfOurOwn, a {{Fanfic}} site which launched in 2008, is still in beta as of 2013. Creating an account requires an invitation by an existing member or adding your email address to the invite queue.
* ''PAYDAY 2'' seems to be stuck in a state between beta and fleshed out final release. While the game had an actual beta for a short period of time, nearly every major update caused some GameBreakingBug to occur and the game's mechanics change almost frequently to the point where players don't bother getting too comfortable with their play style, knowing that the developers will change the rules again.

!!Fictional examples:

* Pretty much all of Tony Stark's ''IronMan'' suits seem to be constantly modified, repaired, rebuilt and replaced, which is handy for writers who [[DependingOnTheWriter have trouble keeping his powers straight]].
** Also true in [[MarvelCinematicUniverse the movies]]. He went through three versions in ''Film/IronMan'', three more in ''2'', by the end of ''Film/TheAvengers'' he was on number seven and in ''Film/IronMan3'', he was up to number forty-two!
*** On the other hand, many of those other thirty-five seemed to be specialized units, which is odd considering his each of his suits was typically a SwissArmyWeapon. Given that his beta testing seems to destroy half the suit in the process, it's strange that he has any of the previous versions.
*** That's addressed in the movie itself, though. Stark actually ''didn't'' beta-test the suits following the Mark 7.
----