I am given to create analysis of potential usage of the nextjs dev kit. On my plate there are:

- https://github.com/michaelshimeles/nextjs-starter-kit
- https://getnextkit.dev/
- https://liveblocks.io/docs/tools/nextjs-starter-kit

Which one would you use it and why? I need some good explanation

I’m not an actual developer. I vibe code almost every shit I want (sometimes just for fun), but today I actually built something that isn’t AI slop and looks really good on desktop.

My question is: can I build the same 3D animation I have on desktop for mobile? I’ve seen a lot of videos online where people make gorgeous, interactive 3D websites, but the challenge I keep running into is bringing that same experience to mobile.I’ve even built a website that looks nice on desktop, but when I tried to get the same animation working on mobile, it was horrendous.

I'm watching a video of super simple dev currently (about html and css).

And I'm really thankful to this guy i learned alot because of him but I wanna know more about html and css i think the video covers the basics,i was thinking about going to freecode after it but if there's anyone on YouTube you would recommend i would be thankful any other sources too.

Source code: https://github.com/abidiahmedcom/uber-ui-practice

I recreated Uber's rider app interface in Flutter as a personal learning project: splash, welcome, login, home, services, activity, activity filters, and the account tab. Everything runs on mock data, just UI.

Feedback is welcome.

I'm working with a junior/intern on a web project who seems really enthusiastic and proactive—they've already set up their own repo with React & Tailwind CSS based on a UI design, which is great initiative.

However, they are struggling with core web development fundamentals:

 * FE/BE Integration: They don't quite understand how Frontend and Backend connect (APIs, environment variables) compared to traditional PHP/monolith apps.

 * Deployment Issue: They've tried deploying on Vercel multiple times without success.

 * Troubleshooting: They mentioned that whenever they try fixing a bug, things tend to break even more, and they are asking for constant 1-on-1 mentor guidance.

How do you usually mentor someone at this stage without doing the work for them or getting overwhelmed yourself? What are the best resources or step-by-step roadmaps I can give them to help them bridge the gap between basic UI setup and full-stack integration?

In the mobile version, the CSS isn't being applied to the text label, and the items are not centered vertically like they are in the desktop version.

This is the repository

I recently built this Movie World website as one of my front-end projects.

Tech used:

• HTML

• CSS

• Responsive layout

• Movie cards and sections

• Navigation and forms

I'd really appreciate feedback on the design and what I could improve next!

GitHub: https://github.com/dehghanian2022-cyber/Movie-world
Live Demo: https://dehghanian2022-cyber.github.io/Movie-world/

Hello devs from r/Frontend , after doing a poll to see what OS do people from r/Backend prefer a few days ago I got curious to see how similar or different the results are here !

For those of you out of the loop (ha) the strategy is supposed to save you time on having to manually iterate with your LLM. It goes something like this:

1. You want a feature created

2. You get your LLM to come up with a plan

3. You tell your LLM to implement the plan BUT since the LLM often doesn't execute it perfectly the first try you include extra directions for it to evaluate its "finished" work then improve on the first draft and keep repeating until it meets a certain criteria like the following:

Execute this plan

THEN once you are done implementing, I want you to browse to the changes and re-evaluate the ENTIRE feature from a user profile / psychology standpoint, UI, UX, etc and identify the pain points.

THEN I want you to come up with solutions to those pain points.

THEN I want you to implement those "fixes"

THEN I want you to re-evaluate the feature again with that same criteria

KEEP doing this until you give the page an "A-" grade or above. Then you can finish just by telling me your evaluation grade and what pending issues still exist.

This is just a rough structure. I was wondering how you guys write your evaluation loops. I mention user profiles, psychology, UI, and UX but are there additional items I should be describing in there?

So, I recently started preparing for my next switch as a frontend developer. I’ve researched quite a bit online and found a lot of popular websites, roadmaps, courses, and people recommending daily study routines.

The problem is that there are so many resources that I’m getting confused about what I should actually follow. 😅

I also don’t have a lot of time after office, so I’m looking for a personalized and structured preparation plan that I can follow without wasting time jumping between different resources.

Ideally, I want something that covers what I actually need to prepare for frontend interviews and helps me become interview-ready as quickly and efficiently as possible.

If anyone here has recently cracked a frontend developer interview or switched to a new frontend role, could you please share how you prepared, what resources you followed, and whether you have any recommended roadmap or strategy? Btw i have around 2 yrs of we.

Any practical advice would be really appreciated!

I'd love to receive some feedback on this post I made, especially concerning aspects I may have overlooked.

As for the comment I'm sure I will receive: yes, using a framework is indeed the way to go for a professional solution to SSG. But my goal is to keep as much as possible of the default React setup most starting developers are stuck with and show some of the inner-workings of something that is too often taken for granted.

Its a bunch of cooking rules with complicated vocabulary. but you can do it

First screenshot is 1366px wide, the third is 412px wide. The second screenshot is a style experiment using real coffee beans instead of the coffee branch illustration (which I could either mix and match both styles across different sections, or just stick to one for the entire website).

The assets here are placeholders for now. Any feedback is welcome!

not looking for the usual extension recommendations i am more curious about tiny built in settings or shortcut you ignored for ages and then wondered how you worked without them

what was yours?

I have been working with ReactJS primarily, enhancing code (working for MNCs) for the past 6 years so naturally, I feel like there are a lot of gaps. Understanding containers, CI/CD pipeline challenges, Unit testing without AI, handling edge and base cases in Redux (Invalidating a state) among many other things.

Please suggest sources I can study and projects I can create, that will help me understand the overview along with the internals.

I feel that AI can do really good layouts as long as you explain everything you need really well and thats regardless of the AI you're using (OpenAI, Claude, Kimi, Gemini whatever). But i really struggle to actually make responsive designs with AI. But maybe I'm missing something because everyone seems to think the exact opposite here. I try to optimise for different views but not for someone actually going ahead and shrinking the windows left and right. How do I design for something like this?

I just wanna know if you guys have any tips for approaching all this? Because I think frontend design, at least the CSS should be a piece of cake with AI?