I’m planning to hire two separate developers through freelance platforms for my web application project. One will handle the frontend design and user interface, while the other will work on the server-side logic and database integration.
For the backend development, I’m considering technologies like Spring Boot, Java, MyBatis, and PostgreSQL. The frontend will likely use modern JavaScript frameworks and responsive design approaches.
What are the recommended strategies for organizing this type of split development approach? I need advice on how to structure the project requirements so both developers can work efficiently without integration issues later. Should I create detailed API specifications upfront, or are there other coordination methods that work better for distributed web development teams?
totally! clear API specs r crucial. i’ve had issues b4 when frontend and backend don’t match up. swagger can rlly help, make things smoother in the long run!
Interesting setup! How are you planning to handle auth and security between the two parts? Also curious why you went with MyBatis instead of Hibernate? Might be worth having one person own the overall architecture to avoid any gaps between teams.
I’ve managed similar projects before - you need a shared development environment from day one. Set up a staging server where both developers can deploy and test continuously. I’ve seen everything work perfectly in isolation, then completely break during integration. Nail down your data models and API contracts upfront, but be open to adjustments as necessary. Weekly sync meetings between your developers can greatly reduce miscommunications later, even short 15-minute check-ins. Start with API versioning to ensure the frontend developer can continue working while backend changes are made. Let the backend developer create mock endpoints first, allowing frontend development to begin immediately while the actual backend is under construction. This parallel approach can significantly reduce your timeline.