At the very beginning of the project, you may face the question of choosing a framework.Perhaps the most important requirements for the framework may be the following:

  • How soon can the first release of the application be released?
  • How much will be available in the first release?
  • How convenient can the application be?
  • How soon can the next releases come out?

If you need as soon as possible the first release of the application, Bitrix will probably suit you.

Ready-made template solutions will allow you to start your online business quickly, sometimes it is enough just to enter data about your store and fill it with goods. If you need a non-standard solution, the question is: how non-standard? Sometimes it is enough to change styles, and sometimes you need more intervention.

Bitrix is not very friendly to expanding the standardized database structure, but on the other hand you immediately get the administrative part of the site and the ability to change a lot on the site without involving developers.

There is also a database, sharpened by work with product catalogs. There are users, products, sales offers, orders, delivery services, payment systems, they are all customizable, but with some restrictions

A large number of modules will allow you to expand the functionality of your site, but onlywith the functionality of modules, sometimes a developer is required for their integration. If the functionality you need is not in the box or in the available modules, you will definitely need a developer, but it is not always convenient to add the functionality you need to Bitrix. Subsequent releases will depend on this.

If it turns out that your idea assumes a non-standard database structure, perhaps you better pay attention to open source frameworks, the most convenient and extensible of which are Laravel, Symfony and Yii2.

he first release of the application depends on the complexity of the project and can take from a week or two to several months. The first release will be what you yourself want to see there, and a large number of various stable components and modules for development, which are constantly evolving like the frameworks themselves, will help speed up the project implementation process.

The database structure in this case is completely controlled by the developer or the development team, which means there are no hard boundaries for the database, but still he / they should have very clear ideas about your needs, since the database structure is determined at the beginning of the implementation and then it is very inconvenient to make edits to it.

Properly written, the foundation of the application can serve as an excellent base for expansion. Here, frameworks show their advantage over CMS, including Bitrix, because For extensions, you can allocate places in advance and implement them with the least delay. When subsequent releases come out - again, it depends on your needs, but if you design the application correctly, releases will not take long to wait.

The frameworks are most convenient for writing an API. They also usually use template engines such as Twig, Blade and others, unlike Bitrix, which uses PHP as an output template engine. This makes it much easier to make changes to the client side.

As for the client side, the application can use various JavaScript libraries and frameworks. Libraries allow you to create functionality faster, but lose in scalability, so extending and making changes to the JS code of your site may be much more difficult in the future. Usually, libraries, such as jQuery, are used to solve specific narrow problems, while the framework can be fully responsible for the behavior of the entire web site, as well as interact everywhere with the API. The framework will allow you to conveniently extend the application, which will allow you to save time and money on future releases. A good example of a JS framework is Vue.JS, with which you can quickly make an application functional without losing scalability.

Projects like "Booking" are characterized by the fact that several types of interacting persons coexist at once, for example, "customer" and "performer", in contrast to "shop", where usually only one type of user exists, "buyer".
Some projects require not only the implementation of the client side, such as a web site, a mobile application, with which users will explicitly interact, but also a special program interface of the application, API.
If you work in the field of sales and deliveries, you will inevitably encounter the need to automate your routine tasks. In this case, the correct solution would be to develop an accounting system specifically for your needs.
Online trading has long become the norm throughout the world. Creating your online store you need to go through several stages of development: the creation of structure, design, page layout and programming.
Online exchanger
As part of the creation of the exchanger, you can implement the following subtasks
Ask us
* - required fields

Feedback about us