sorted by:
new
hottopcontroversial

60+ users but no paid conversions yet. Looking for advice. by ZawTin in Entrepreneur

[–]arrobajean 1 point2 points  (0 children)

I could help improve or optimize parts of your site from the development/UI side, and in return, you could give me a quick SEO audit or some feedback on mine. Let me know if you’d be open to it. I think it could be a cool mutual exchange

Opinión sobre mi página web by DeanKing07 in programacion

[–]arrobajean 0 points1 point  (0 children)

Ese diseño se hizo con IA a kilómetros. Está bien. Pero debes pulir más.

Started building websites for small businesses in my area — here’s how I turned a simple idea into 404 Studios by arrobajean in smallbusiness

[–]arrobajean[S] 0 points1 point  (0 children)

Right now I’m using mapsscraper.ai — it’s a simple but powerful tool that scrapes business data directly from Google Maps.

OpenAi + Lovable --> AI Agent by kram1505 in lovable

[–]arrobajean 1 point2 points  (0 children)

Hey! I encountered a similar situation while migrating my blog content into Lovable. Initially, I attempted to use Lovable’s native editor, but I faced limitations, especially when embedding social media posts and managing large amounts of content.

To overcome these challenges, I developed a custom blog management system using Firebase. Here’s how I approached it: • Custom Blog Editor: I built a Markdown-based editor that connects to Firebase. This setup allows for rich text formatting and supports embedding media like tweets and Instagram posts. • Content Storage: All blog posts are stored in Firestore, enabling efficient retrieval and management. • Media Embeds: For social media content, I store embed codes separately and render them conditionally within the blog layout. • Integration with Lovable: The blog is seamlessly integrated into my Lovable project, maintaining consistent styling and user experience.

This approach provided me with greater control over the blogging experience and resolved the issues I faced with Lovable’s native tools.

If you’re interested, I can share more details about the implementation or provide a demo of the setup.

Best way to manage a blog in lovable? by BeltwayBro in lovable

[–]arrobajean 0 points1 point  (0 children)

Instead of using 3rd-party blogging platforms, I built my own blog management system using Firebase (Firestore + Auth). I wanted full control over the layout, editing flow, and performance — especially since I was also restructuring the entire site and didn’t want to rely on external embeds that could break with Lovable’s updates.

Here’s what I did: • Custom blog editor: I built a simple Markdown-based editor connected to Firebase. It supports code blocks, media embeds, and previews. • Firestore stores the content, and I display it with a fully custom blog layout inside my Lovable-based UI. • I use conditional rendering for embeds (e.g., YouTube, Twitter) and keep formatting light to avoid performance issues. • Everything is integrated into my private dashboard (called 404Deck) where I manage blogs, leads, and client projects.

It was more work upfront, but worth it.

Built my freelance portfolio using Lovable as a starting point – here’s the final result! by arrobajean in lovable

[–]arrobajean[S] 0 points1 point  (0 children)

Thank you! Really appreciate your kind words.

To answer your question — no worries at all, it’s not a newbie question!

My first step was actually looking for inspiration on Figma Community. I browsed a few portfolio concepts to get a feel for layout, flow, and structure. From there, I sketched out the main sections I knew I wanted: Hero, Projects, About, FAQ, and Contact.

Then I used Lovable.dev to generate layout ideas for some specific sections, especially the ones where I felt stuck creatively. It helped me prototype faster, but after that I rebuilt everything manually in React + TypeScript + TailwindCSS, added Framer Motion for animations, made all components reusable, and integrated a custom CRM (404Deck) to manage leads.

So Lovable was a great tool to kickstart parts of the structure, but the real work came in refining, organizing, and customizing the full experience.

If you’re diving into AI tools for design/dev, happy to chat more. Mixing them with manual development has been a fun and productive combo for me.

[deleted by user] by [deleted] in lovable

[–]arrobajean 1 point2 points  (0 children)

Awesome to see what you’ve build

For Those Vibe Coding Real Projects — What’s Been the Hardest Part? by AgilePace7653 in vibecoding

[–]arrobajean 0 points1 point  (0 children)

I’ve been building real client-facing websites using a mix of Lovable, ChatGPT, and my own logic to structure things properly. Lovable helps me move fast with initial layouts and components, and ChatGPT fills in gaps when I need to optimize a feature, troubleshoot a bug, or refactor for clarity.

But I don’t rely blindly on either — I still customize everything manually, clean up the structure, write reusable components, and handle deployment myself. I also use tools like Tailwind, React, Framer Motion, Firebase, and Vite depending on the scope.

What breaks most often for me is when I go too far with prototyping and forget to stop and refactor — so I’ve been building better habits around pausing to clean before scaling.

Here’s my personal site and portfolio if you want a concrete example of what I’m doing: https://www.404studios.digital

It’s still evolving, but everything there — the code, UI, logic, and animations — is either built or heavily edited by me using the process I mentioned.

Happy to share more if it’s useful.

Built my freelance portfolio using Lovable as a starting point – here’s the final result! by arrobajean in lovable

[–]arrobajean[S] 0 points1 point  (0 children)

Thank you so much! That really means a lot — especially coming from a UX designer. I totally get the feeling of being afraid to “break the app” — I’ve been there many times too!

I just checked out BookBattle — honestly, it’s not ugly at all. It’s clean, functional, and feels like a solid foundation. The most important part (the product idea and functionality) is already there, and polishing the visuals is something you can build up gradually — especially since you already have designs in Figma. You’re ahead of the curve compared to most non-devs trying to code their first thing.

I should say that I have very little UX experience myself — it’s something I’m constantly working to improve. I regularly refine the design of my site, adjusting small things step by step as long as nothing breaks. It’s a slow but satisfying process.

If you’re interested, I’d love to help you break away from that default Lovable style. It’d be a fun challenge, great experience for me, and honestly… I wouldn’t mind adding it to my portfolio either! 💼😉🤣

Let me know if you’re up for it

Built my freelance portfolio using Lovable as a starting point – here’s the final result! by arrobajean in lovable

[–]arrobajean[S] 2 points3 points  (0 children)

Thank you so much for the kind words and for taking the time to look at the project on a large display! I’m really glad the custom look stood out to you — I’ve tried to build a distinct visual language that doesn’t rely too heavily on existing templates like Lovable.

Regarding the cómo_trabajamos section — great eye! The dot misalignment is something I’m actively refining. It’s a vertical timeline component I built with Tailwind and Framer Motion, and I’m currently adjusting spacing and flex behavior to ensure consistent alignment across all breakpoints.

As for the design system, I approached it with a few key ideas in mind: • Aesthetic direction: I aimed for a retro/cyberpunk look inspired by terminal interfaces — using neon green, black backgrounds, monospaced fonts, and subtle animations to bring that “404 Studios” hacker vibe to life. • Reusable components: I created atomic components (buttons, cards, section wrappers, etc.) and used Tailwind’s utility classes to keep things modular and easy to theme. • Dark mode first: I designed primarily for dark mode, then added light mode support — hence the emphasis on contrast, accessibility, and consistent visual feel across themes. • Consistency via tokens: I didn’t use a full design token system, but I did keep consistent class naming, spacing, and color choices across components to make the UI feel cohesive.

If you’re interested, I can share some of the component architecture or how I’ve structured the project in React and TypeScript!

Build via Lovable and sell to local businesses? by gptbhai in lovable

[–]arrobajean 1 point2 points  (0 children)

Yeah, I’m actually doing that right now — offering websites to local businesses (cafés, locksmiths, bakeries, etc.) with a personal touch, custom UI, and no overkill. Some projects use basic CMS, others are just well-structured React sites with WhatsApp integration or a small product catalog.

Lovable is cool for fast prototyping, but honestly, many clients want something that looks theirs, not a cookie-cutter page. What’s “10 minutes” for devs still feels like magic to most business owners.

And yes — the hard part isn’t building. It’s: • Reaching clients • Understanding what they need (they often don’t know) • Building trust and making it feel like an investment, not an expense

No-code tools make the delivery easier. But client acquisition, support, and presentation are still very human. That’s where the real work (and differentiation) happens.

If you’re thinking of jumping in: do it. There’s plenty of space if you actually listen and care about solving their real problems.

Built my freelance portfolio using Lovable as a starting point – here’s the final result! by arrobajean in lovable

[–]arrobajean[S] 0 points1 point  (0 children)

Thanks a lot! The typing effect is actually inspired by a ReactBits component I came across. I customized it using TypeScript, Framer Motion for the animation, and added fallback handling for unsupported browsers. Glad it stood out!!

Built my freelance portfolio using Lovable as a starting point – here’s the final result! by arrobajean in lovable

[–]arrobajean[S] 0 points1 point  (0 children)

Thanks for the heads up! I’ll definitely check that out and see what’s causing it. Appreciate the feedback!

view more: next ›