When I first started building mobile apps with CapacitorJS, I was completely lost. There are so many ways to structure an app, choose plugins, and decide what should stay web vs native.

After building more Capacitor apps, I created Capstart: a simple and opinionated guide to build CapacitorJS apps with React, Supabase, shadcn/ui, and useful native plugins.

It’s not “the only way” to use Capacitor, just a clear starting point I wish I had when I began!

https://capstart.dev

TL;DR: https://windframe.dev/mcp

Hi everyone 👋

I’ve been working on a Tailwind-native MCP that gives coding agents better design context when generating  interfaces.

A lot of AI-generated UI still feels inconsistent because the agent has no real sense of design systems, spacing, typography, or visual structure. It can write Tailwind, but it often lacks the taste and context needed to make the result feel properly designed.

So I built the Windframe MCP around that idea.

It gives coding agents access to curated Tailwind-native styles, design tokens, and styleguides inspired by products like Linear, Notion, and other companies that invest heavily in their design systems.

The difference in output quality has been really impressive. The generated interfaces feel polished and visually cohesive, not like a random collection of Tailwind components.

I’ll keep adding new design styles to the MCP as well, so the library will continue to grow over time.

Give it a try here https://windframe.dev/mcp

Would love any thoughts or feedback :)

Write your styles as typed objects directly on your JSX markup and get zero-runtime atomic CSS. Built as a preprocessor for StyleX.

Tired of the usual styling trade-offs?

• CSS modules → no type safety or colocation
• Utility-first classes → stringly typed, less expressive
• CSS-in-JS → runtime cost + hydration issues

Vicinage gives you the best of all worlds.

Just drop styles right where they belong.
Vicinage transforms this into StyleX calls at build time, then StyleX extracts it to atomic CSS.

import { apply } from 'vicinage'
import { color } from 'solarwindcss/color.stylex'

export function Hello() {
  return (
    <div
      {...apply({
        color: color.green500,
      })}
    >
      hello, world
    </div>
  )
}

Features:

• Responsive
• Pseudo-classes
• Pseudo-elements
• Logical styles
• Dynamic styles
• Pass styles between components

Works great with:

• React / Next.js
• Vue
• Vite or any bundler via unplugin

Just put the Vicinage plugin before the StyleX plugin.

Need consistent design tokens? Check out SolarWind CSS, purpose-built tokens for Vicinage & StyleX (colors, spacing, typography, everything).

Try it, break it, tell me what you think. https://github.com/chbybnwr/vicinage

useHaptics - hook it up to any <audio> or <video> on Android Chrome. Bass drop hits, phone hits with it - louder moments buzz harder, quiet ones buzz softer

Hey!

I made an app that makes it incredibly easy to create stunning mockups and screenshots—perfect for showing off your app, website, product designs, or social media posts.

✨ Features

• URL -> Website Screenshot
• Video Support & Animations
• 30+ Mockup Devices & Browser Frames
• Auto Backgrounds
• Annotation Tool:
• Chrome Extension

Try it out: https://postspark.app/templates

Would love to hear what you think!

Hi! I’m the dev behind PostSpark, a tool for creating beautiful image and video mockups of your apps and websites.

I recently launched a new feature: Mockup Animations.

You can now select from 25+ devices, add keyframes on a simple timeline, and export a polished video showcasing your product. It’s built to be a fast, easy alternative to complex motion design tools.

Try it out here: https://postspark.app

I’d love to hear your feedback!

I built a browser-based desktop environment with React, Vite and local-first apps

I have been working on a project called IP Linux: a browser-based desktop environment that runs as a static web app.

Live site: https://ip-os-linux.vercel.app/
GitHub: https://github.com/ikerperez12/IP-OS-LINUX

It is not a real Linux distribution, and it does not run native binaries. The idea is different: I wanted to explore how far a polished desktop-like experience can go inside a normal browser tab.

The result is a small web OS-style environment with:

• A splash / entry screen
• A desktop with icons, folders and widgets
• A top panel with system controls
• A dock and app launcher
• Resizable and draggable windows
• Virtual workspaces
• Snap assist
• A global search / Spotlight-style command palette
• Local-first apps
• Reactive wallpapers
• Glass UI and visual effects
• A public GitHub repo and Vercel deployment

Why I built it

Most web demos are landing pages, dashboards or small single-purpose apps. I wanted to build something that feels more like an environment.

I was interested in questions like:

• Can a web app feel physical and desktop-like?
• How should windows behave inside a browser viewport?
• How do you organize many small apps without making the UI messy?
• How far can local-first storage go before a backend is actually needed?
• How do you publish a visual project publicly without exposing secrets or overcomplicating the stack?

IP Linux became a way to test all of that in one project.

What is inside

The app includes a catalog of built-in apps and tools: Files, Terminal, Browser, Settings, App Store, Music Player, Matrix Rain, games, developer tools, productivity apps and visual utilities.

The apps are loaded lazily, so the initial shell does not need to download every app upfront. The virtual file system and user preferences are stored locally in the visitor's browser with IndexedDB/localStorage. There is no backend, no account system and no required environment variables for the public release.

What I focused on

The main focus was the shell experience:

• Window resizing and dragging
• Dock behavior
• Desktop icon grid
• App launcher workflow
• Keyboard shortcuts that do not interfere with inputs or the terminal
• Responsive behavior for compact viewports
• Wallpaper rendering that respects reduced motion and tab visibility
• Public-safe security posture
• A README that presents the project like a real product

There were also a few important constraints. For example, a full YouTube page cannot be embedded in an iframe because YouTube blocks that for security reasons. So IP Linux includes a YouTube Lite / embed-aware fallback instead of pretending that every website can load inside the internal browser.

Stack

The project is built with:

• React
• TypeScript
• Vite
• Tailwind CSS
• Radix UI primitives
• Lucide / React Icons
• DOMPurify
• IndexedDB via idb-keyval
• Vercel static hosting
• Vercel Web Analytics

The repo also includes a public release setup:

• README with screenshots and GIF
• MIT license
• SECURITY.md
• Vercel config
• Security headers
• Robots and sitemap
• Manifest
• GitHub Actions CI for audit, lint and build

What I learned

The biggest lesson was that a desktop UI is mostly about small interaction details.

A window that opens slightly too small feels broken.
A dock icon that scales inside a clipped container feels wrong.
Desktop icons that can overlap make the whole shell feel unfinished.
Keyboard shortcuts that steal Tab from the terminal are frustrating immediately.

Fixing those details made the project feel much more real than adding another decorative effect.

I also learned that public release work matters. A project can look good locally but still feel unfinished if the repo has a generic README, no security notes, no screenshots, no CI and no clear deploy story.

Feedback welcome

I am sharing it because I think browser-based desktop interfaces are a fun area for frontend experimentation.

I would especially appreciate feedback on:

• Window management
• Desktop organization
• Accessibility
• Performance
• App ideas
• Whether the repo presentation is useful for other developers

Live: https://ip-os-linux.vercel.app/
Code: https://github.com/ikerperez12/IP-OS-LINUX

Built an open-source Arabic poetry platform containing ~945k verses from 932 poets across 10 historical eras.

The project includes: static Astro frontend, API on Cloudflare Workers, shared oRPC contracts, OpenAPI generation, Turborepo monorepo, PostgreSQL dumps + HuggingFace dataset.

One of my goals was making this a clean real-world example of: Turbo monorepos, contract-driven APIs, static-first architecture, shared typed contracts across apps/packages.

I’d genuinely appreciate feedback on: architecture decisions, package boundaries, API design, over-engineering, scalability concerns, anything that looks fragile or awkward long-term.

Repo:  https://github.com/alwalxed/qafiyah

Hello everyone, we've just released the 1.5 version of our small music player.

What's the motivation behind this? We are tired of the streaming paradigm, always renting, never owning, and we're tired of the lack of innovative design or unusual designs to say the least.

Everything is either too cold, black and white, two-toned squared designs (it works, but this is all there is now!) or the classic vibe-coded UI with neon colors.

So we chose to do exactly what every sane person would do: take months to build our own music player :).

We want to bring back the cool effects of the early 2000s, the "we did it because we could" mentality. Our goal is not to be a better Apple Music, Spotify, Deezer, or even a foobar2000, but to be a simplified local music player that simply works, offers a new design in the form of a widget, and doesn't phone home, doesn't ping the internet, doesn't lock you out with a subscription, account, or email.

You take the app and you can keep it forever, inciting the "own your medias point of view" (starting by owning the software that plays your medias).

I said that it was a "just work" type of app, but it has more than simply play/pause features:

Core Music Player Features

• Load music from an entire folder or specific directory
• Enable on-click and drag-and-drop loading capabilities
• Display metadata automatically (artist name, album name, artwork, track ID, bitrate, etc.)
• Display full metadata on a dedicated screen
• Include an equalizer with customizable presets
• Adjust left / right balance.
• Offer a mini player mode (hidden or locked)
• Display a small bar visualizer

Playback Controls

• Play and pause music playback
• Manage volume levels
• Seek through tracks using a timeline
• Enable shuffle and repeat settings
• Handle media session control via keyboard/media keys or AirPods

File Support

• Support various audio file formats: MP3, AAC, M4A, ALAC, AIFF, FLAC, WAV, OGG, Opus

User Interface

• Utilize a skeuomorphism UI design
• Detect the user's theme and adjust the screen theme accordingly
• Allow manual selection of a custom screen theme

Additional Features

• Enable filtering by artist name, album name, or song title
• Handle drag functionality for the app itself
• Include click sound effects (that you can disable)

If you want to see more here is our github page to download the app (MacOS, Windows10/11, Linux (debian/fedora))

And if you want to be updated on it here is our subreddit r/ResonanceApp :)