The inner-platform effect describes a common anti-pattern where developers build overly customizable systems that essentially duplicate their underlying platform. This tendency often results in inefficient, hard-to-maintain software that fails to leverage the strengths of existing tools and frameworks.

Classic examples include plugin systems that recreate operating system functionality, such as Firefox add-ons that build FTP clients or file browsers. Database developers sometimes abandon relational database management systems entirely, storing everything in generic entity-attribute-value tables. While this approach offers flexibility, it sacrifices performance, query optimization, and data integrity constraints that RDBMSs provide out of the box.

XML developers face similar temptations, using generic element names with attributes to store meaningful data, which complicates XPath queries and validation. Web desktops represent another extreme case, running entire desktop environments within browsers. While inner platforms can serve legitimate purposes like portability and privilege separation—Java being a prime example—they often emerge from developers recreating libraries of custom functions that duplicate existing platform capabilities, resulting in slower and less reliable code.