Common questions
Start with the installation guide, browse the category guides and comparisons, or read the engineering notes.
What is PODIE?
PODIE is an independent collection of React UI components with live previews, attributed source code, and installation endpoints. It is operated by world of creator in the United States.
How do I install a component with npm?
Initialize shadcn in your React project with npx shadcn@latest init. Then run the npx shadcn@latest add command shown on the component page. It copies source files into your project and installs declared npm dependencies. Follow the installation guide for a real import example, aliases and styling checks. This is a source registry, not an npm package named PODIE.
Which frameworks and package managers are supported?
The October 1, 2026 production sample used React 19.2.6 and Tailwind CSS 4.2.1 with Vite 8.0.13. It did not test every framework configuration. Installation uses the shadcn CLI with npm, pnpm, modern Yarn, or Bun. Read the recorded installation sample and limits, then follow the framework and alias setup. Compatibility with every React setup is not guaranteed.
Are all components native React elements?
No. Some are native React source; others wrap an isolated scene in an iframe. Check the entry’s implementation notes. An iframe owns its own document and may have separate scroll, styles and bundled libraries.
Can I use the components in my own project?
The website has no paid checkout for these downloads. Each component’s included license or distribution notice governs use of its source. Distribution bases vary; do not assume every listing uses the same license. Preserve the applicable copyright and attribution notices.
What does PODIE MCP do?
PODIE MCP lets Codex or Claude Code search components and App templates, inspect source and dependencies, get recommendations and prepare installation commands. Your editor performs local installation with your authorization. Follow the PODIE MCP connection guide for setup and troubleshooting.
How do I know PODIE MCP is connected?
A saved setup or copied prompt is not proof. Ask your editor to use PODIE to find UI for your project. The connection dialog shows Connected · tool call confirmed after a successful call. Reload the server if the editor has not loaded its tools. A successful search confirms connection; verify installation separately in your application. See connection troubleshooting.
Is PODIE MCP the same as the official shadcn MCP server or MCP Apps?
No. PODIE searches its own curated catalog and returns source and installation plans. The official shadcn MCP server works with configured component registries. MCP Apps provides interactive interfaces inside supporting MCP clients. PODIE’s documented workflow installs UI into your project; it does not provide an embedded MCP Apps interface. See the UI component MCP comparison for official references and task-based choices.
Does copying an install command mean installation succeeded?
No. A copy records installation intent. Success in your project requires running the command, importing the component and checking the actual application. The installation evidence identifies the date, scope and versions of PODIE’s recorded checks; it does not establish success in your project.
Where can I compare components before choosing?
Start with the category guides for currently published components. The comparisons explain source differences, MCP workflows and availability. Historical comparisons identify removed components explicitly; their old installation records are not current installation recommendations.
Why do some gallery previews wait for hover?
App cards and components in the 3D category start on hover or keyboard focus and stop when you leave. Ordinary component previews play while visible, including in search. Reduced motion, a hidden tab or an open PODIE dialog can pause playback. Open the detail page for manual interaction on a touch device.
Do installed components update automatically?
No. PODIE checks upstream sources daily, but new or changed components require review before publication. Source already installed in your project remains local; review differences before reinstalling or accepting an overwrite.
Are all PODIE App templates complete Next.js applications?
No. Check each App template’s runtime, README and delivered files. React frontend templates can require your own backend, routing and authentication. A Vite build does not establish Next.js server-rendering compatibility.
Do the full-site demos call an AI model?
No. The current CODING and DESIGN framework demos use local example replies and browser-saved projects. Developers can connect their own server through the adapter interface; provider keys should remain on that server.
Need a correction or help?
Send the component URL and the issue to zhang.chen@worldofcreator.com. Read about PODIE, the terms of use, and the privacy notice.
Last updated: .