Software applications frequently use forms, tables, dialogs, and dashboard layouts. Developers must modify component source code to satisfy custom application requirements.

UI-Package provides an open-source registry of prebuilt user interface components, blocks, charts, and templates. The registry supports Vue, React, Angular, Svelte, and Lit Web Components. You can preview components and copy source code directly into your repository.

Architecture Overview: • Installed components do not depend on a runtime package from UI-Package. • You own and maintain all installed source code in your repository. • React, Vue, and Svelte use their respective shadcn command-line interfaces. • Angular uses the UIPKGE Angular command-line interface. • Lit Web Components follow the setup guide in the documentation. • Dashboard blocks read top-to-bottom so you can modify layout and data fields easily.

Installation Procedures: Run the command for your framework to install a component:

Vue: npx shadcn-vue@latest add https://uipkge.dev/r/vue/button.json

React: npx shadcn@latest add https://uipkge.dev/r/react/button.json

Application Starter Templates: Starter templates are available for Nuxt, Next.js, Angular, and SvelteKit. These templates include optional configurations for authentication, databases, billing, email, and error monitoring. Configure only the services that your project requires.

License Terms: UI-Package is open-source software under the MIT license. It is free for personal and commercial projects without subscriptions or paid tiers.

Architecture Preview Image: https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/yya4abkyohze2zxgopcm.png

Documentation and Repository: • Documentation and Registry: https://uipkge.dev/?utm_source=reddit&utm_medium=community&utm_campaign=multiframework_launch&utm_content=frontend • GitHub Source Repository: https://github.com/uday-a/uipkge-registry?utm_source=reddit&utm_medium=community&utm_campaign=multiframework_launch&utm_content=frontend

Which component or framework do you plan to use for your next project?

So I'm a frontend engineer and I always wanted to try the on scroll animation. I explored some pre-existing liberary but didn't find any that would help me achieve an on scroll growing vine thingy.

But then after a lot of failed attempts and I achieved something that was good enough for me!

I did'nt wanna do any self promotion but just wanted to showcase this onscroll animation and get some form of feedback.

Here: blog/author

Before Posting about how I achieved it and potentially launching a claude skill / liberary I wanna see what you guys think before putting efforts!

Thanks!

Some frontend decisions behind halloween.js (repo: https://github.com/rogulia/halloween.js).

It has to work when the site owner can only paste a script tag into a header field and add a class, with no control over execution order. So the public API is the class list on body. A MutationObserver re-syncs on every class change, so toggling a class later from a CMS field or a page builder works the same way.

Things I'd like a second opinion on:

• Effects render in one fixed overlay layer with its own z-index variable, so they never shift layout. Does anyone see a case where that breaks (iOS Safari toolbars, sticky headers)?
• The IIFE injects its own styles, so there's no CSS file to forget. I assume the trade-off is that a strict CSP has to allow injected styles, but I haven't tested that.
• Malformed config (a bad season date) fails open instead of disabling the library. I went back and forth on that.

Live demo: https://halloween.js.org

Seeing new css features get implemented, particularly ones that have been on my “wishlist” for years, is such a complicated feeling with how much Claude has invaded day to day work.

I was just reading about linked parameters and responsive iframes, thinking about potential projects I could have used them on, trying to store use cases somewhere deep in my brain for later use.

And suddenly I wondered if I will ever end up actually writing any of these new features myself. Or if I’ll have a chance to use them in an unexpected way and get a moment of feeling smart and clever. Or if I’ll ever have to think about their existence at all.

It’s just a weird new feeling of ennui I didn’t see coming and thought I’d yell into the void of Reddit on a Friday night.

A formatter, minifier or deobfuscator can be made to turn one script into another.

You can go try out all 186 techniques with this script: https://divergence.trustsig.eu/

Or try the Tetris-Snak demo here: https://divergence-game.trustsig.eu/

Techical breakdown: https://trustsig.eu/blog/javascript-divergence/

Whenever I have an AI agent update my front-end code, reviewing the changes in Git or raw code diffs feels super inefficient.

Writeup/devblog: https://blog.gaborkoos.com/posts/2026-10-17-How-Not-to-Build-a-Five-in-a-row-Game_engine/

I have been experimenting with client-side LLMs with WASM and WebGPU to investigate if this architecture could be used to create new SaaS features. Here is a product demo showing this concept in action

My one sponsor pays $200 a month for my React drag and drop library and wants a real homepage with demos, so I set a rule that every demo has to use the library itself. Three weekends in I have half a hero and a drag demo that fights page scroll on iOS Safari, the same bug as two open issues, while 41 issues sit waiting. Do you even open a library's homepage, or go straight to the docs and last commit and would you trust it less if the homepage obviously was not built with the thing it is selling?

Hi.

At my company basically all code is written by agents now, so reviews got split by whoever is free instead of by who knows the area.

This week I'm a React dev and I approved 6 PRs in Go, two of them touching payments. Our manager says the AI review covers it, and coderabbit / claude review do catch real things, I'm not saying they don't.

The problem is I can't tell if what they didn't flag is fine, because I don't know Go. My name is still the one on the approval.

Is this happening at your company too or is it just us?

Hey frontend friends! 👋

I've been working intensively on making frontend code simpler to write — both for humans and for LLMs.

My current goal: figure out whether any frontend code can be written declaratively, without piles of state and effects that just keep things in sync.

I'd love to see examples from your own practice — pieces of code that today still require a huge amount of imperative logic in whatever framework you're using. The more unusual and rare the case, the better. 🙏

I'll start.

My first-ever JS library was a Tooltip — a small popup that appears when you hover a button or a label. Sounds trivial, but in practice you need:

• a delay before it appears
• coordinate updates once per animation frame — and no more
• animate show / hide
• package all the logic into a single component
• let the developer attach it to any element (or several at once)
• no extra wrapper divs that break layout

Below is a concept of such a declarative component plus a usage example.

interface TooltipProps {
  content: string;
  slot(refs: ElementRefs<HTMLElement>): void;
}

const ToolTip = component<TooltipProps>(props => {
  const refs = elementRefs<HTMLElement>();
  const position = event(
    refs, "mousemove", ev => ({x: ev.clientX, y: ev.clientY}), {x: 0, y: 0});
  const active = event(refs, [
    ["mouseenter", () => true], 
    ["mouseleave", () => false]
  ], false);
  const transform = frameThrottled(
    `translateX(${position.x}px) translateY(${position.y}px)`);
  const opacity = active ? "1" : "0";
  const visible = timeout(active, 500);

  <>
    <Slot model={props.slot} refs={refs}/>
    <Overlay>
      <If condition={visible}>
        <div class="tooltip" style={{transform, opacity}}>
          {props.content}
        </div>
      </If>
    </Overlay>
  </>;
});

const UsageExample = component(() => {
  <ToolTip content="Hello world!" slot={props => {
    <label for="name" write-element={props.refs}>Name:</label>
    <input id="name" write-element={props.refs} />
  }}/>;
});

I asked a few LLMs to describe what the code does. They couldn't recognize the custom primitives, but based on their names they still described the behavior correctly. Then I asked them to reimplement the same logic in other popular frameworks. Only Solid.js produced genuinely clean code.

Thanks for reading — and I'd genuinely love to see your examples. 🙌

I built a multi-model AI tool as a pure static site, and a few frontend decisions turned out more interesting than the AI part.

Storage

Everything lives in IndexedDB: chats, workflows, and generated media as blobs, with persistent storage requested. There's an optional mirror to a local folder using the File System Access API.

Security

API keys sit in the browser, so the Content Security Policy only allows the site's own scripts and blocks remote images. That stops a model from leaking data by writing an image URL into its output.

Sharing

A whole workflow is compressed into the URL fragment, which browsers never send to a server. No backend needed to share.

Offline

A service worker precaches the app shell. It opens offline, and only the model calls need the network.

What I'd like to hear

What would you have done differently, and what's the first thing you'd worry about with this setup?

Source: https://github.com/shrinathprabhu/fusellm

I used open source code of Ladybird browser, extracted only rendering engine (HTML + CSS), removed Javascript and replaced it with Python bindings with same API.
So basically, now you can write desktop applications with HTML interface. It supports most modern CSS features and frameworks like tailwind, but I deloberately removed all browser-specific features like networking, localstorage, canvas and others.
This is not Electron-like, it's not a full packed browser, only UI renderer, but a thing that I dreamt for a long time. 25Mb wheel size, around 90Mb RAM for a running GUI python app.

I don't understand whether it's still useful at this point of technology, where you either use Electron or switch to native render like GPUI, but I need some feedback on whether the community needs this at all.

​

Hey everyone! I'm looking to get better at building polished, modern websites and would appreciate some recommendations.

I'm particularly interested in:

- UI/UX: Tools, resources, and design principles to improve layouts, typography, visual hierarchy, and overall user experience.

- Animations: Libraries and resources for smooth transitions, scroll-driven animations, and interactive components.

- Component libraries: Lesser-known resources for high-quality UI components and creative interactions.

- Claude Code: Tips, workflows, skills, plugins, or other tools to get better results from Claude Code, especially for frontend design and implementation.

- Feedback: How do you approach improving a website's design when the initial AI-generated result looks generic or underwhelming?

I'd appreciate any useful resources, personal workflows, or advice. Thanks!

I’ve been messing around with AI coding agents lately, and I hit a massive roadblock that I think is worth talking about if you're trying to use these tools in prod. We’ve all seen the cool demos of AI assistants dynamically "writing their own data tables" and building UI on the fly. It looks awesome on paper. But I stumbled on a post over at Claude Builders that perfectly captures the nightmare scenario: they let an agent loose to build a basic Svelte table, and the thing literally generated over 1,000 lines of custom code from scratch. The core issue is that these agents have zero engineering common sense. They are brutally literal. If you tell them to build a feature, they will happily reinvent the wheel, write massive amounts of custom CSS, and burn through your token budget completely ignoring the fact that lightweight, battle-tested libraries like TanStack Table already exists. Instead of getting a clean component, you get stuck with an absolute mountain of technical debt to maintain, higher API bills, and code that usually completely misses out on modern framework features (like Svelte 5 runes) because the LLM got lost in its own logic.

as the title says.

maybe both choices works since it is just an internal company dashboard, not SaaS b2b,b2c dashboard...

So just choose the one that devs prefer so they spend less time builiding it right?

or how do you see it

those who generate logos with aione icon being good tells you almost nothing about whether you have an icon set, so maybe put 12 together and suddenly i'm often looking at:

different visual weight. different corner treatment, objects occupying the box differently, also one shape that is technically centered and somehow still looks wrong. from my experience this happens often and that's why i think editability becomes more interesting than generation pretty quickly and svg generators are often still underused. vector models, for example, make the generated asset edited at shape and point level, so we can move or scale a shape, recolor an element, or select several points and adjust that part of the form together. i don't think this was possible like 3 years ago even.

i'd still expect a normalization pass for a real set

would like to ask people building icon systems: what do you standardize first? like, is it size, optical weight, corners, or something else? visual: 8 to 12 related icons in a row. select only the 2 or 3 obviously relevant shapes or points in one icon

This question is only for developers IN THE EU who create websites and act as retainers.

I’m assuming the majority of you have clients create accounts on strapi, Wordpress, sanity, etc and you manage.

If so do you need a dpa agreement between you and the client because acting as a retainer makes you a data processor.

Any tools to generate a dpa?

Sup everybody!

5 years ago I published Puppertino, my own CSS framework targeting macOS and iOS design. Lot of things have changed since then both for Apple users and my personal growth!

So this year I sat down and rebuilt Puppertino from the ground up, got Liquid Glass working for UI items and surfaces, and updated everything to macOS 27 and iOS 27.

Would love to see what the community thinks of it, mostly because things like Acessibility, theming and semantics should be 1000 times better in this new version.

I've spent around eight months working on a WhatsApp-based operations tool using ChatGPT and Codex.

The software itself is real: React frontend, backend, persisted operational states, message events, and explicit human decisions.

But presenting what makes it different has become a surprisingly difficult problem.

The product is built around one distinction: a conversation's latest message doesn't necessarily tell you who is responsible for what happens next.

I wanted to communicate this through an interactive website.

The visitor would first experience a few conversations and the responsibilities left behind. Then the narrative would transition into the actual product, allowing them to explore, make operational decisions, and see their consequences.

Not a traditional SaaS landing page. Not a video. A guided narrative that becomes interactive at meaningful moments.

Here's where the process repeatedly breaks down.

With ChatGPT, we can discuss the idea in remarkable detail. We can define the sequence, interaction principles, user decisions, visual continuity, technical constraints, and what the visitor should understand.

But when we try to materialize it, the process keeps collapsing into something smaller and fundamentally different:

• Static mockups instead of an experience.
• Generic dashboards instead of meaningful interactions.
• Beautiful but disconnected visual experiments.
• Endless planning and refinement without testing the actual experience.

Our latest attempt is almost absurd: after extensive discussion about narrative, interaction, and visual continuity, we ended up producing a basic HTML chat inbox screenshot.

Technically correct. Almost irrelevant to the actual problem.

This has happened across multiple approaches, including an audiovisual project, image generation, detailed specifications, and direct HTML/CSS.

I'm starting to question whether this is a limitation of the tools, a missing creative/interaction design skill, or a fundamentally wrong workflow.

I'd genuinely like to hear from people who've shipped something similar:

1. How do you move from a strong conceptual narrative to a real, cohesive interactive experience without reducing it to static screens?
2. What do you actually build first to validate the experience itself?
3. Where do you draw the line between AI-assisted implementation and the need for a human interaction designer or creative developer?

I'm not looking for another “use better prompts” answer or a new collection of AI tools.

I'd particularly appreciate concrete examples, failed approaches, and actual workflows from people who've dealt with this gap.

And if the realistic answer is that this requires creative direction or skills I don't currently have, that's useful to know too.

We’re in the middle of redesigning the DevHandler site and the new version is still being built. I’ve added a few screenshots of where it’s heading, and the current site is here https://www.devhandler.com/ . Curious if anything jumps out that you’d change before we get too far with it. Could be layout, mobile, interactions, accessibility, or just something that looks like it’ll be annoying to build or use.