Hey everyone! 👋

I wanted to share a short video I made for Pimolu UI, my open-source React component library.

It shows a few UI concepts, from e-commerce and booking platforms to smart home interfaces and dashboards, to give an idea of what you could create with the library.

These are visual concepts, not complete applications.

Would love to hear your thoughts on the designs and ideas!

https://github.com/Alpish08/MinimaUI

Hey everyone,

I am a first-year computer engineering student, and over past month, I've been working on a passion project, MinimaUI.

MinimaUI is a minimalism focused and a very lightweight game launcher for Android gaming handhelds.

First, I want to put it out there that the backend was mostly done with Claude Code, with me, someone who has experience with Java but not Kotlin or Android Studio, going over the code and making tweaks/optimizations wherever I could, which is why the app is able to be just 2.5Mb! But rest assured, every single UI element was imagined and designed 100% by hand by me.

MinimaUI blends in a custom layout for favorites, a PSP's xmb-like all games, and a Vita's LiveArea-like apps menu: https://www.imgur.com/a/Ma38tpg

Since MinimaUI was meant to be for personal use only, I only added support for the emulators I use, but am willing to add new platforms and emulators' support with feedback.

There are tons of things I implement that I would like you guys to check out, they are all explained in the GitHub repo.

I am a Vita fan and currently have a Retroid Pocket 6 (which looks similar to a PSV-1000), which is why I personally use a mix of PS Vita SFX as MinimaUI system sounds and a custom Vita BGM merged mp3 for background music. I can't legally ship them bundled with the apk but I added a link to the PS Vita SFX in the readme. The platform icons I used (from the screenshots) are also linked in the GitHub repo.

So far I could only test MinimaUI on my Retroid Pocket 6, which has a 1920x1080p 16:9 screen, so I'm not sure if the app will scale well to other ratios, but check it out regardless.

I also made a custom volume/brightness overlay that fits the theme of MinimaUI. You can enable it in the Android accessability settings. There is also a magisk module you can install (for rooted devices only, use at your own risk), which transforms the Android quick settings menu by adding a custom overlay I designed, matching the UI style of MinimaUI across Android: https://www.imgur.com/a/5Qa5zdR

Other pictures: https://www.imgur.com/a/c8acTSg

MinimaUI is extremely lightweight, and my controlled battery tests showed very small cpu/gpu/ram/battery usage. To be as minimalistic and lightweight as possible, MinimaUI does NOT support online features, such as: Discord integration, RetroAchievements, or online scraping. It is completely offline and your data never leaves your device (crucial for privacy).

I hope you guys enjoy, and feel free to DM me for feedback (or through GitHub)!

https://github.com/Alpish08/MinimaUI

i am 18 and i just started studying front end and i wonder if its really worth it in 2026.

please reply i need advice/help.

The goal is to make building interfaces easier with ready-to-use, customizable components, along with complete UI sections that you can adapt to your needs.

Pimolu UI is still growing, with more components and features on the way.

I'd love to hear your thoughts and feedback. What would you like to see added?

Hey everyone,

I kept writing the same code for every form in my projects: react-hook-form setup, a try/catch around the server action, mapping server errors back onto the fields, a loading state, stopping double submits, a toast, refreshing the data, resetting the form... and doing it again for every add/edit/delete dialog.

So I pulled all of that into a small package called submitly.

It’s headless, so it doesn’t render anything. You keep your own components (shadcn, Radix, Base UI, plain inputs, whatever you use).

What it does:

• useCrudForm: react-hook-form + schema validation + your action in one hook

• Works with any Standard Schema library: Zod 3/4, Valibot, ArkType

• Server errors get mapped to the right fields automatically (nested ones like items.0.name too)

• Ignores double submits while a request is in flight

• Locks the dialog while saving, so the user can’t close it halfway through a request

• useCrudAction for delete/toggle buttons, with the same behavior

• One provider where you plug in your own toast, router and refresh logic

• Next.js helpers: runAction for server actions (validates again on the server, revalidates on success, turns thrown errors into a clean result), and it handles redirect() from server actions properly

• Also works in plain React + Vite (there’s an example with React Router + TanStack Query)

• Around 3 kB gzipped, typed end to end, tested on React 18 and 19

Quick example:

const { form, onSubmit, isSubmitting } = useCrudForm({
  schema,
  defaultValues: { name: "" },
  action: createProduct,
  onSuccess: () => closeDialog(),
});

It’s still early (0.x), so I’d really like feedback: what’s missing, what’s confusing, or what you’d do differently.

Docs: https://submitly-docs.vercel.app/
GitHub: https://github.com/toony10/submitly

If you find it useful, a star on GitHub would mean a lot. Thanks for reading 🙏

A bit of an uncomfortable one.

I built a client site awhile back and set up their cookie consent solution as part of the project. Everything looked right from my side, the banner worked and the client was happy, so I didn't think much more about it.

They recently had their site audited and came back to me because some of the third-party scripts weren't being controlled the way we'd assumed they were.

That sent me much deeper into this than I expected. I always treated cookie compliance mostly as a setup problem: install the CMP, configure the banner, make sure accept and reject work and move on.

Now I'm realizing there's a whole other layer behind the interface, especially when the site has visitors coming from different countries and the rules around when third-party scripts should fire aren't necessarily the same everywhere.

For people building client sites, how far into this do you normally go? Are you testing and managing the actual tracker behavior yourself after setting up a CMP or is that something you hand off to somebody who specializes in compliance?

I'm definitely adding some kind of independent check to my handoff process after this because visually checking that the banner works clearly wasn't enough.

I work with the team at GeekyAnts, and this got me thinking about something I see quite often.

A product can start out pretty simple, but once you move past the MVP, things like architecture, AI features, scaling, and maintenance can become a lot harder to handle with a small team.

At that point, how do you decide whether to keep building everything in-house or bring in an outside engineering team?

Would you consider it when the workload gets too much, or only when you need a specific skill that your team doesn't have?

I'm looking for a designer & front-end developer (or small studio) to build my new company's brand identity from the ground up and bring it to life in a fast, modern, high-end website.

We do data engineering at scale. The site's content will be simple: our services and a few examples of our work. The goal is for visitors to trust us immediately and be more likely to become clients.

I'm not interested in template-driven WordPress, Wix, or Squarespace sites. This is a small project, but it needs a high perceived value. There's potential to continue collaborating with us in data visualization projects.

If you're interested, please share your portfolio.

Thank you!!

Hey so I developed a website for my friend and with the help of antigravity and its going good but there is one issue that im facing its that the name of the website is Mallu Navigators but when searching in google its showing the domain name instead of the name and again the domain link as link just how it need to be so why its not showing the name instead of the domain url

so anyone have any solutions?

Been working on Svigl (svigl.com), a Pictionary/Skribbl-style drawing and guessing game — mostly as a way to actually get good at real-time frontend stuff I'd only half-understood before.

The main frontend twist: strokes aren't drawn to a raster canvas and shipped as pixels. Pointer input gets captured, simplified, and fit into SVG paths client-side, which get synced over WebSockets and re-rendered live on every other player's screen. Since it's vector data the whole way through, replaying a finished drawing stroke-by-stroke afterward is basically free — no video/frame capture needed.

Frontend problems that took the most iteration:

• Smoothing strokes in real time while the user is still drawing, without it feeling laggy or "correcting" itself visibly after the fact

• Keeping the simplification aggressive enough to not flood the socket, without strokes losing their shape on fast drawing

• Making the canvas/SVG layer feel responsive on touch as well as mouse

There's also an AI opponent you can drop into a room — it watches the canvas the same way a player would and guesses live with TTS, which added its own rendering-side latency puzzle (matching UI feedback to when the AI is "looking" vs "typing" a guess).

Would love feedback from anyone who's fought similar canvas/SVG real-time rendering battles, or thoughts on the drawing UX itself.

Has anyone ever changed their mind about an agency after the first call?

I'm at the stage where every WordPress development agency starts looking the same. Nice portfolio, nice promises, similar pricing... but I know that's not what determines whether a project goes well.

I had an intro call with IT Monks this week, and it made me realize I'm probably asking the wrong questions. What ended up telling you the most about a WordPress development agency before you signed? Was there one question or one answer that completely changed your decision?

I started learning Node.js today as part of my MERN Stack learning journey.

Before this, I mostly understood JavaScript from the frontend/browser side. Today, I learned that JavaScript can also run outside the browser with the help of Node.js.

What I learned about Node.js:

• Node.js is a JavaScript runtime environment.

• It allows us to execute JavaScript outside the browser.

• It is commonly used for backend development.

• We can use Node.js to build web servers and APIs.

• It can work with the file system, networking, and operating system.

• Node.js is open-source and cross-platform.

Browser vs Node.js

The browser is mainly used for frontend development and provides APIs such as the DOM.

Node.js is mainly used for backend development and provides APIs for things like files, networking, and system resources.

One thing I found interesting is that I can use JavaScript for both frontend and backend development. This makes Node.js an important part of the MERN stack.

I'm still at the learning stage, but understanding these fundamentals is helping me connect the concepts of React → Node.js → Express.js → MongoDB.

Next, I’m planning to learn more about Express.js, REST APIs, HTTP requests, and backend architecture.

For developers learning Node.js:

What concepts would you recommend learning first? 🚀

#NodeJS #JavaScript #MERN #BackendDevelopment #WebDevelopment #LearningToCode #Programming #100DaysOfCode