DEV Community

Cover image for Building a Car Classified Script: Dev Notes, Trade-offs & Questions
Viktoria Holikova
Viktoria Holikova

Posted on

Building a Car Classified Script: Dev Notes, Trade-offs & Questions

Over the past few weeks, I’ve been experimenting with building a car classified script — something like a small-scale version of Autotrader or Cars.com, but with a focus on simplicity and adaptability.
Instead of just listing the "features," I wanted to document a few developer-side trade-offs I ran into and hear how others have solved them.

Core Features I Focused On

• Car Listings with Deep Filters
(Make, Model, Year, Price Range, Fuel Type, Transmission, Location)
• Dealer vs Individual Seller Roles
(Single dashboard but different permissions)
• Responsive & Mobile-First
Most car buyers search from mobile.
• Favorites + Compare Cars
Users almost always compare before deciding.
• Contact Seller (Call / WhatsApp / Email)

Tech Stack Decisions

• Backend: PHP + Codeignitor (for modularity)
• Frontend: Bootstrap + Vanilla JS
• Database: MySQL with some heavy indexing
• APIs: Google Maps for location-based search, Twilio for SMS alerts
• Admin Panel: Role-based with ad moderation + payments

Challenges That Surprised Me

  1. Search Speed on Large Data Filtering by make, model, location, and price killed performance after ~50k entries. Index tuning + caching helped, but I feel there’s a smarter approach.
  2. Image Uploads & Compression Car sellers love uploading 10+ high-res images. Handling auto-resize + CDN storage without killing speed was tricky.
  3. Dynamic Taxonomies Brands, Models, Variants, Years — keeping this flexible but not overly complex was harder than real estate listings.
  4. Payments for Featured Ads Simple integration with Stripe/PayPal works, but what’s the best way to keep it modular for regional gateways (PayU, Razorpay, etc.)?

Open Questions for the Dev Community

• How would you handle fast search + filtering at scale (Elasticsearch? Algolia? Something else?)
• For mobile app sync, would you go with a dedicated API layer from day one or build once the product grows?
• Anyone here experimented with Flutter + Laravel APIs for classified-style apps?

Next Steps

I’m experimenting with a mobile app integration where listings update in real-time between the web + app. Also exploring a plugin system so small dealers can white-label their own version.
Would love to hear from others who’ve tackled classified or marketplace apps:
• What dev shortcuts saved you time?
• What mistakes should I avoid scaling this?

Top comments (0)