Skip to content
dvnt.io

Resources · glossary

Framework

A ready-made skeleton you build an application on, instead of writing from scratch things that have been written a thousand times. Choosing a framework is a decision for years, not for one project.

Also called
  • framework
  • software framework
  • web framework
  • application framework
  1. 01

    Why it is a business decision

    Because the framework determines who you will be able to hire to develop the product. A popular one means more developers on the market and lower rates. A niche one can be technically better and at the same time more expensive over the whole life of the project.

  2. 02

    What it gives you

    Solved problems you do not have to think about: form security, session handling, performance, code structure. The team starts with business features, not with foundations.

  3. 03

    The price

    Imposed conventions. Doing something against the framework can be harder than writing it from scratch — which is why matching the tool to the type of project matters more than its popularity in rankings.

  4. 04

    How to check before you choose

    Ask how many people in Poland work with the technology and when its last major version came out. A project with no activity for two years is a maintenance risk, not a saving.

In practice

Related terms

  • CMS (content management system)A panel in which a non-technical person changes a website's content without touching the code. The difference between a good and a bad CMS is the difference between independence and depending on your vendor.
  • Vendor lock-inDependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.