[{"_1":2,"_66":-5,"_67":-5},"loaderData",{"_3":4,"_15":16,"_19":20},"root",{"_5":6},"analytics",{"_7":8,"_9":10,"_11":12,"_13":14},"enabled",true,"key","phc_oB9H4iqQJ8otg7L2NNeTyouNuo8weGuQ8BXJbKkVwjkW","host","https://eu.i.posthog.com","environment","production","routes/lang",{"_17":18},"lang","en","routes/lang.blog.$slug",{"_17":18,"_21":22,"_64":65},"post",{"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":8,"_38":39,"_40":41,"_46":47,"_54":55,"_58":59,"_60":61,"_62":63},"title","When Software Adapts to the Way You Work","slug","when-software-adapts-to-the-way-you-work","author","Sarah Ghidalia","date","2026-05-26","excerpt","Adaptive interfaces no longer just respond to clicks: they learn from your habits, anticipate your needs and step back when they are not useful. A concrete challenge for business software.","category","UX Design","image","https://asset.gencior.ai/landing/blog/adaptive-user-interface-engineer.png","published","publishedAt",["D",1779753600000],"tags",[42,43,44,34,45],"User Interface","AI","Business Software","Productivity","keywords",[48,49,50,51,52,53],"adaptive user interface","adaptive software interface","AI engineering software","intelligent business interface","reducing engineer cognitive load","enterprise interface personalization","translations",{"_56":57},"fr","quand-le-logiciel-sadapte-votre-facon-de-travailler","content","\nFor decades, business software has rested on one deeply entrenched principle: it is up to the user to adapt to the tool. Cascading menus, frozen dashboards, features piled up without hierarchy… We were at the mercy of rigid forms and unforgiving monster applications. The interface was not a living workspace. For companies, that translates concretely into employees forced to navigate dozens of screens to reach the information they need, at the precise moment they need it. A genuine waste of time and a daily source of frustration.\n\nThe age of AI brings plenty of promises with it, including that of **personalization**. Today, a new generation of interfaces is emerging under the name : interfaces that dynamically modify their structure, their content and their features according to the user, their context and their way of working. It is no longer you who spends hours learning how your software works, but your software that learns to know you in order to interact with you better.\n\n## What Is an *Adaptive User Interface*?\n\nThe notion of an adaptive interface is often reduced to a question of or cosmetic personalization. In reality, their goal is not merely aesthetic but functional.\n\nAn AUI rests on four distinct components :\n* The **user model**: a profile built continuously from observed interactions, behaviours and preferences.\n* **Context awareness**: the system's ability to detect changes in the environment of use, the user's role, or the nature of the task at hand.\n* The **adaptation engine**: the algorithmic core that decides how and when to modify the interface by combining those two streams of information.\n* **Adaptive elements**: specific interface components that can be modified, such as the layout, the content displayed, the navigation and the interaction modes. They are the visible surface of the invisible decisions taken by the three preceding component types.\n\nTwo concepts that are often confused also need to be distinguished. An **adaptable interface** gives the user full control: they configure, they personalize, they choose what they see. An **adaptive interface**, by contrast, gives the system enough intelligence to assess the current state and trigger an adaptation with no user intervention. Between the two, a third model known as \"**mixed initiative**\" shares that control: the system proposes, the user confirms. It is this last model that tends to win out in demanding professional environments, because it preserves the user's decision-making power while reducing the configuration burden.\n\nWhat makes AUIs possible today is the convergence of available computing power, the maturity of machine learning algorithms and the rise of large language models, two components of Artificial Intelligence . The interface no longer waits for the user to formulate an explicit request: it interprets the intent, anticipates the context and prepares the workspace accordingly.\n\n## Why Software for Engineers Needs This Most\n\nToday's software interfaces suffer from a problem that is well documented in the enterprise software industry: the \"**feature overload**\" paradox. To answer the diversity of needs within a company, tools grow needlessly complex with hundreds of menus and dashboards: every user ends up swamped by an interface of which 80% of the features are useless to them. That accumulation is not harmless: it generates a cognitive load that slows work down, increases errors and discourages adoption.\n\nJohn Sweller describes cognitive load as \"*the mental effort required to process information in short-term working memory*\" . That working memory is limited: presenting too much information at once, or requiring the user to follow many mental steps in parallel, is enough to saturate it.\n\nIn highly technical environments, informational complexity is a major brake on productivity: when tools and processes needlessly add to mental load, they end up stifling expertise, durably undermining engineers' concentration, speed and motivation. When working memory is overloaded, errors multiply, creativity declines and progress slows. And frequent context switches — moving from one module to another, one view to another, one project to another — are one of the most underestimated drains on the productivity of technical profiles.\n\nAdaptive interfaces, by applying the principle of , absorb the software's complexity without exposing it . An engineer in a regulatory verification phase does not see the same commands as when exploring raw data. A project manager sees an aggregated view where a technician sees the detail of the calculations. The interface does not change its nature: it changes its point of view.\n\nMore than personalization at any price, business software needs relevance. The idea is not to create chaotic interfaces that change constantly, but to make the software more intuitive and better suited to the context, without losing stability.\n\nTo be more relevant, the best interfaces should :\n* **Prioritize functions:** surface the most useful shortcuts and tools according to the context, while keeping a stable base architecture.\n* **Reduce complexity:** simplify the interface (for example, *Assistive Access* at Apple) for users who need fewer distractions, while keeping the door open to advanced functions.\n* **Anticipate needs:** offer help or suggestions at the precise moment the user needs them, thereby avoiding fruitless searching.\n\nAs the article points out: \"*many products disappoint users by presenting them with too much information too early*\". The challenge is not to hide features, but to offer progressive support, where the user reaches the advanced tools at their own pace.\n\nFor a company, this simplified ramp-up is an immediate gain: it considerably reduces the training time for new engineers while getting them operational faster.\n\n> If your current AI solution is not meeting your expectations, it may be because it is not personalized, either at the interface level or in its features. We explain why in [this article](https://gencior.ai/en/blog/ai-you-tested-vs-ai-that-could-really-help-you).\n\n## Adapting Without Disorienting: The Real Design Challenge\n\nThe benefits of AUIs are real, but designing them raises a serious challenge: **adapting without disorienting**.\n\nAdaptive interfaces can cause specific usability problems, notably disorientation and a feeling of losing control. A user who finds their workspace changed without having asked for it can feel lost and lose trust in the solution.\n\nSeveral design principles help avoid the pitfalls inherent to adaptive interfaces :\n* **Give control to the user**: any automatic adaptation must remain reversible. The user must be able to \"lock\" a configuration that suits them, disable certain adaptive behaviours or revert to a previous state. Systems that decide on the user's behalf with no recourse generate resistance, even when the adaptations proposed are objectively relevant.\n* **Transparency**: the interface must signal its adaptations, even discreetly. A message along the lines of \"We have reorganized your dashboard based on your most-used reports\" turns a potentially destabilizing change into evidence of attentiveness. The more the user understands why the interface has changed, the more trust they grant it and the less they feel watched by the application.\n* **Do not abandon traditional UX**: adaptation must sit on top of a stable, predictable base structure, not replace it. Main navigation, critical functions and reference data must stay accessible in the same place, whatever adaptation logic is in play.\n* **Monitor frustration as much as engagement:** an engineer who clicks a lot is not necessarily an engineer who is working well: they may be looking for what the interface has moved, or working around an adaptation that does not suit them. An interface that optimizes engagement without measuring friction creates a false impression of success. The signals to watch are not only clicks and session time, but detours, repeated searches for the same functions, and manual reversions to previous configurations. It is these behaviours that reveal when an adaptation has missed its target.\n* **Ensure gradualness:** an interface that changes too fast, too often, or too radically breaks the mental models the user has built. Adaptation must be gradual, consistent with usage observed over a sufficient period, and proportionate to the stakes: you do not adapt a navigation shortcut the same way you adapt the organization of a critical calculation module.\n\nTaking these five principles on board is the indispensable foundation for deploying effective adaptive interfaces.\n\n## Key Takeaways\n\nAdaptive User Interfaces are not just another UX trend. They represent a paradigm shift in the relationship between a professional and their digital tool: from a relationship of imposed learning towards one of evolving collaboration.\n\nBuilding an AUI does not come down to plugging in a personalization module. It involves thinking hard about engineers' real usage patterns, about the data to collect and its governance, about the levels of adaptation that create value without creating disruption. It is a design investment, not a feature add-on.\n\nBear in mind that an interface which hides critical information on the grounds that it is \"rarely used\" is not a good adaptive interface: it is an interface that has optimized the wrong metric. Designing an AUI for engineering environments must include explicit safeguards: certain data, certain alerts, certain functions must never be hidden, whatever the adaptation logic.\n\nThis, incidentally, is where the complementarity between AI and human expertise takes on its full meaning. AI reduces the effort needed to explore alternatives, interpret results and set up studies. It strengthens the engineer's creativity and judgment. It does not replace them. A well-designed interface for a design office or an industrial setting is not a system that makes decisions in place of the engineer: it is a system that protects their attention so they can spend their energy on what genuinely requires their expertise.\n\nAt Gencior, these principles align with our vision: building interfaces, in particular for [BatiSearch](https://batisearch.com), that learn from your teams, adjust to your projects and step back where they are not needed, so that the engineer stays at the centre of the decision.\n\n**Want to know more about how we bring these principles into our tools?**\n\n","compiledSource","\"use strict\";\nconst {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n a: \"a\",\n blockquote: \"blockquote\",\n em: \"em\",\n h2: \"h2\",\n li: \"li\",\n p: \"p\",\n strong: \"strong\",\n ul: \"ul\",\n ...props.components\n }, {CallbackRequest, LinkPreview, TermTooltip} = _components;\n if (!CallbackRequest) _missingMdxReference(\"CallbackRequest\", true);\n if (!LinkPreview) _missingMdxReference(\"LinkPreview\", true);\n if (!TermTooltip) _missingMdxReference(\"TermTooltip\", true);\n return _jsxs(_Fragment, {\n children: [_jsx(_components.p, {\n children: \"For decades, business software has rested on one deeply entrenched principle: it is up to the user to adapt to the tool. Cascading menus, frozen dashboards, features piled up without hierarchy… We were at the mercy of rigid forms and unforgiving monster applications. The interface was not a living workspace. For companies, that translates concretely into employees forced to navigate dozens of screens to reach the information they need, at the precise moment they need it. A genuine waste of time and a daily source of frustration.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"The age of AI brings plenty of promises with it, including that of \", _jsx(_components.strong, {\n children: \"personalization\"\n }), \". Today, a new generation of interfaces is emerging under the name \", _jsx(TermTooltip, {\n term: \"Adaptive User Interface (AUI)\",\n definition: \"An interface that dynamically modifies its structure, content and features according to the user.\"\n }), \": interfaces that dynamically modify their structure, their content and their features according to the user, their context and their way of working. It is no longer you who spends hours learning how your software works, but your software that learns to know you in order to interact with you better.\"]\n }), \"\\n\", _jsxs(_components.h2, {\n id: \"what-is-an-adaptive-user-interface\",\n children: [\"What Is an \", _jsx(_components.em, {\n children: \"Adaptive User Interface\"\n }), \"?\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"The notion of an adaptive interface is often reduced to a question of \", _jsx(TermTooltip, {\n term: \"responsive design\",\n definition: \"Responsive design is a web design technique that allows a page to adapt automatically to the size of the screen it is viewed on.\"\n }), \" or cosmetic personalization. In reality, their goal is not merely aesthetic but functional.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"An AUI rests on four distinct components \", _jsx(LinkPreview, {\n text: \"(1)\",\n url: \"https://www.monitask.com/business-glossary/adaptive-interface/\"\n }), \":\"]\n }), \"\\n\", _jsxs(_components.ul, {\n children: [\"\\n\", _jsxs(_components.li, {\n children: [\"The \", _jsx(_components.strong, {\n children: \"user model\"\n }), \": a profile built continuously from observed interactions, behaviours and preferences.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Context awareness\"\n }), \": the system's ability to detect changes in the environment of use, the user's role, or the nature of the task at hand.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [\"The \", _jsx(_components.strong, {\n children: \"adaptation engine\"\n }), \": the algorithmic core that decides how and when to modify the interface by combining those two streams of information.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Adaptive elements\"\n }), \": specific interface components that can be modified, such as the layout, the content displayed, the navigation and the interaction modes. They are the visible surface of the invisible decisions taken by the three preceding component types.\"]\n }), \"\\n\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Two concepts that are often confused also need to be distinguished. An \", _jsx(_components.strong, {\n children: \"adaptable interface\"\n }), \" gives the user full control: they configure, they personalize, they choose what they see. An \", _jsx(_components.strong, {\n children: \"adaptive interface\"\n }), \", by contrast, gives the system enough intelligence to assess the current state and trigger an adaptation with no user intervention. Between the two, a third model known as \\\"\", _jsx(_components.strong, {\n children: \"mixed initiative\"\n }), \"\\\" shares that control: the system proposes, the user confirms. It is this last model that tends to win out in demanding professional environments, because it preserves the user's decision-making power while reducing the configuration burden.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"What makes AUIs possible today is the convergence of available computing power, the maturity of machine learning algorithms and the rise of large language models, two components of Artificial Intelligence \", _jsx(LinkPreview, {\n text: \"(2)\",\n url: \"https://salfati.group/topics/generative-ui\"\n }), \". The interface no longer waits for the user to formulate an explicit request: it interprets the intent, anticipates the context and prepares the workspace accordingly.\"]\n }), \"\\n\", _jsx(_components.h2, {\n id: \"why-software-for-engineers-needs-this-most\",\n children: \"Why Software for Engineers Needs This Most\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Today's software interfaces suffer from a problem that is well documented in the enterprise software industry: the \\\"\", _jsx(_components.strong, {\n children: \"feature overload\"\n }), \"\\\" paradox. To answer the diversity of needs within a company, tools grow needlessly complex with hundreds of menus and dashboards: every user ends up swamped by an interface of which 80% of the features are useless to them. That accumulation is not harmless: it generates a cognitive load that slows work down, increases errors and discourages adoption.\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"John Sweller describes cognitive load as \\\"\", _jsx(_components.em, {\n children: \"the mental effort required to process information in short-term working memory\"\n }), \"\\\" \", _jsx(LinkPreview, {\n text: \"(3)\",\n url: \"https://www.hashicorp.com/en/blog/3-ways-engineering-leaders-can-reduce-cognitive-load-and-process-friction\"\n }), \". That working memory is limited: presenting too much information at once, or requiring the user to follow many mental steps in parallel, is enough to saturate it.\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"In highly technical environments, informational complexity is a major brake on productivity: when tools and processes needlessly add to mental load, they end up stifling expertise, durably undermining engineers' concentration, speed and motivation. When working memory is overloaded, errors multiply, creativity declines and progress slows. And frequent context switches — moving from one module to another, one view to another, one project to another — are one of the most underestimated drains on the productivity of technical profiles.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Adaptive interfaces, by applying the principle of \", _jsx(TermTooltip, {\n term: \"Just-in-Time UX\",\n definition: \"Just-in-Time UX means generating or displaying only the interface the user needs, at the precise moment they need it.\"\n }), \", absorb the software's complexity without exposing it \", _jsx(LinkPreview, {\n text: \"(2)\",\n url: \"https://salfati.group/topics/generative-ui\"\n }), \". An engineer in a regulatory verification phase does not see the same commands as when exploring raw data. A project manager sees an aggregated view where a technician sees the detail of the calculations. The interface does not change its nature: it changes its point of view.\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"More than personalization at any price, business software needs relevance. The idea is not to create chaotic interfaces that change constantly, but to make the software more intuitive and better suited to the context, without losing stability.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"To be more relevant, the best interfaces should \", _jsx(LinkPreview, {\n text: \"(4)\",\n url: \"https://yenra.com/ai20/adaptive-user-interfaces/\"\n }), \":\"]\n }), \"\\n\", _jsxs(_components.ul, {\n children: [\"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Prioritize functions:\"\n }), \" surface the most useful shortcuts and tools according to the context, while keeping a stable base architecture.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Reduce complexity:\"\n }), \" simplify the interface (for example, \", _jsx(_components.em, {\n children: \"Assistive Access\"\n }), \" at Apple) for users who need fewer distractions, while keeping the door open to advanced functions.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Anticipate needs:\"\n }), \" offer help or suggestions at the precise moment the user needs them, thereby avoiding fruitless searching.\"]\n }), \"\\n\"]\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"As the article \", _jsx(LinkPreview, {\n text: \"(4)\",\n url: \"https://yenra.com/ai20/adaptive-user-interfaces/\"\n }), \" points out: \\\"\", _jsx(_components.em, {\n children: \"many products disappoint users by presenting them with too much information too early\"\n }), \"\\\". The challenge is not to hide features, but to offer progressive support, where the user reaches the advanced tools at their own pace.\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"For a company, this simplified ramp-up is an immediate gain: it considerably reduces the training time for new engineers while getting them operational faster.\"\n }), \"\\n\", _jsxs(_components.blockquote, {\n children: [\"\\n\", _jsxs(_components.p, {\n children: [\"If your current AI solution is not meeting your expectations, it may be because it is not personalized, either at the interface level or in its features. We explain why in \", _jsx(_components.a, {\n href: \"https://gencior.ai/en/blog/ai-you-tested-vs-ai-that-could-really-help-you\",\n children: \"this article\"\n }), \".\"]\n }), \"\\n\"]\n }), \"\\n\", _jsx(_components.h2, {\n id: \"adapting-without-disorienting-the-real-design-challenge\",\n children: \"Adapting Without Disorienting: The Real Design Challenge\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"The benefits of AUIs are real, but designing them raises a serious challenge: \", _jsx(_components.strong, {\n children: \"adapting without disorienting\"\n }), \".\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"Adaptive interfaces can cause specific usability problems, notably disorientation and a feeling of losing control. A user who finds their workspace changed without having asked for it can feel lost and lose trust in the solution.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"Several design principles help avoid the pitfalls inherent to adaptive interfaces \", _jsx(LinkPreview, {\n text: \"(5)\",\n url: \"https://blog.logrocket.com/ux-design/adaptive-interfaces-risks/\"\n }), \":\"]\n }), \"\\n\", _jsxs(_components.ul, {\n children: [\"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Give control to the user\"\n }), \": any automatic adaptation must remain reversible. The user must be able to \\\"lock\\\" a configuration that suits them, disable certain adaptive behaviours or revert to a previous state. Systems that decide on the user's behalf with no recourse generate resistance, even when the adaptations proposed are objectively relevant.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Transparency\"\n }), \": the interface must signal its adaptations, even discreetly. A message along the lines of \\\"We have reorganized your dashboard based on your most-used reports\\\" turns a potentially destabilizing change into evidence of attentiveness. The more the user understands why the interface has changed, the more trust they grant it and the less they feel watched by the application.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Do not abandon traditional UX\"\n }), \": adaptation must sit on top of a stable, predictable base structure, not replace it. Main navigation, critical functions and reference data must stay accessible in the same place, whatever adaptation logic is in play.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Monitor frustration as much as engagement:\"\n }), \" an engineer who clicks a lot is not necessarily an engineer who is working well: they may be looking for what the interface has moved, or working around an adaptation that does not suit them. An interface that optimizes engagement without measuring friction creates a false impression of success. The signals to watch are not only clicks and session time, but detours, repeated searches for the same functions, and manual reversions to previous configurations. It is these behaviours that reveal when an adaptation has missed its target.\"]\n }), \"\\n\", _jsxs(_components.li, {\n children: [_jsx(_components.strong, {\n children: \"Ensure gradualness:\"\n }), \" an interface that changes too fast, too often, or too radically breaks the mental models the user has built. Adaptation must be gradual, consistent with usage observed over a sufficient period, and proportionate to the stakes: you do not adapt a navigation shortcut the same way you adapt the organization of a critical calculation module.\"]\n }), \"\\n\"]\n }), \"\\n\", _jsx(_components.p, {\n children: \"Taking these five principles on board is the indispensable foundation for deploying effective adaptive interfaces.\"\n }), \"\\n\", _jsx(_components.h2, {\n id: \"key-takeaways\",\n children: \"Key Takeaways\"\n }), \"\\n\", _jsx(_components.p, {\n children: \"Adaptive User Interfaces are not just another UX trend. They represent a paradigm shift in the relationship between a professional and their digital tool: from a relationship of imposed learning towards one of evolving collaboration.\"\n }), \"\\n\", _jsx(_components.p, {\n children: \"Building an AUI does not come down to plugging in a personalization module. It involves thinking hard about engineers' real usage patterns, about the data to collect and its governance, about the levels of adaptation that create value without creating disruption. It is a design investment, not a feature add-on.\"\n }), \"\\n\", _jsx(_components.p, {\n children: \"Bear in mind that an interface which hides critical information on the grounds that it is \\\"rarely used\\\" is not a good adaptive interface: it is an interface that has optimized the wrong metric. Designing an AUI for engineering environments must include explicit safeguards: certain data, certain alerts, certain functions must never be hidden, whatever the adaptation logic.\"\n }), \"\\n\", _jsx(_components.p, {\n children: \"This, incidentally, is where the complementarity between AI and human expertise takes on its full meaning. AI reduces the effort needed to explore alternatives, interpret results and set up studies. It strengthens the engineer's creativity and judgment. It does not replace them. A well-designed interface for a design office or an industrial setting is not a system that makes decisions in place of the engineer: it is a system that protects their attention so they can spend their energy on what genuinely requires their expertise.\"\n }), \"\\n\", _jsxs(_components.p, {\n children: [\"At Gencior, these principles align with our vision: building interfaces, in particular for \", _jsx(_components.a, {\n href: \"https://batisearch.com\",\n children: \"BatiSearch\"\n }), \", that learn from your teams, adjust to your projects and step back where they are not needed, so that the engineer stays at the centre of the decision.\"]\n }), \"\\n\", _jsx(_components.p, {\n children: _jsx(_components.strong, {\n children: \"Want to know more about how we bring these principles into our tools?\"\n })\n }), \"\\n\", _jsx(CallbackRequest, {\n lang: \"en\",\n CTAText: \"Get in touch\"\n })]\n });\n}\nfunction MDXContent(props = {}) {\n const {wrapper: MDXLayout} = props.components || ({});\n return MDXLayout ? _jsx(MDXLayout, {\n ...props,\n children: _jsx(_createMdxContent, {\n ...props\n })\n }) : _createMdxContent(props);\n}\nreturn {\n default: MDXContent\n};\nfunction _missingMdxReference(id, component) {\n throw new Error(\"Expected \" + (component ? \"component\" : \"object\") + \" `\" + id + \"` to be defined: you likely forgot to import, pass, or provide it.\");\n}\n","readingTime","9","dnsName","gencior.ai","actionData","errors"]