Blog

Question: when building large web apps what are things to take into consideration to prevent hassles in the future?

  1. Use stable, widely used technologies, don’t let hype convince you (in a month from now there will be some newer, better framework/database/etc). Look for libraries/frameworks with great adoption and large open source following and support.
  2. Don’t jump straight into coding – think and plan before.
  3. Convention over configuration and strict rules for every team member to follow from Day 1.
  4. Unit and Integration Tests for all features.
  5. Code Reviews and Gitflow.
  6. If you’re using SQL databases like PostgreSQL or MySQL – remember to design the tables in a good way (indexes, foreign keys) – data inconsistency is the biggest problem of large applications.

Check out our CTO as a service offering to design your product development strategy.

No comments
Damian LegawiecQuestion: when building large web apps what are things to take into consideration to prevent hassles in the future?

Related Posts

How much should your MVP cost?

How much should your MVP cost?

You want to build the Next Big Thing. And you have a pretty good idea how it should work, look & feel. Great, now it’s time to find a dev team to build your MVP. But how much should your MVP cost? A freelancer will tell you it should cost $5,000 to $15,000. An experienced

MVP dilemma: fat vs. lean, lovable vs. laughable?

MVP dilemma: fat vs. lean, lovable vs. laughable?

How much should a Minimum Viable Product cost? How much time should an MVP take to build and launch? These are the questions our clients ask us and every time answering these questions comes down to one simple conclusion – we understand and define MVP differently. 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *