Air Show

From an in-house WinDev ERP to a rewrite with Lovable

An in-house WinDev ERP that became a tool shared with other companies: technology choices, rewrite method and support to rebuild booking management with Lovable.

20 years

of evolution of the business application

4 months

to rewrite and go live

Context

About twenty years ago, Air Show’s managing director could not find any software able to handle the constraints of his hot-air balloon flight business. So he built his own: first with Access, then with WinDev.

Season after season, the application kept pace with the business. What started as simple schedule management became a real in-house ERP, with everything that implies: a tool perfectly suited to the way people work, but one that was gradually turning into a monster.

The turning point came when several fellow operators started using it. An internal tool can live with its historical shortcuts; a tool distributed to other companies cannot. It had to become robust, readable, maintainable and secure.

The choice: rewrite, not convert

The core of the business - managing appointments, bookings and cancellations - ran in the WinDev back end. The managing director chose to rebuild it with Lovable.

This is not a conversion. You do not transpose WLanguage line by line: you start again from the business rules, formalize them, then rebuild them in an environment that has its own logic. It is a chance to leave behind what was a legacy habit rather than a real need. It is also the main risk: forgetting an implicit rule that only existed in the code.

What we did

The developer is the managing director. Our role was to help him make the right decisions and carry out the rewrite methodically, not to do it for him.

  • Technology choices: advice on the target and what it implies for hosting, security and long-term maintenance.
  • Rewrite method: extraction and formalization of the business rules in the WinDev back end (appointments, bookings, cancellations), breakdown of the scope, rebuild order.
  • Clean-up: removal of duplicates, clarification of “legacy” areas, harmonization of practices to start again on a sound basis.
  • Architecture: module breakdown and consistency, so that each addition no longer makes the whole more complex.
  • Reliability and security: identification of sensitive points and risk reduction, a prerequisite for use beyond the company itself.
  • Working procedures: more rigorous methods to evolve the tool without a domino effect.

Results

  • Live in production in 4 months.
  • WinDev application rewritten with Lovable, with code that is more readable, more maintainable and more secure.
“An internal tool can afford to be just “practical”, but a tool meant to be distributed must be robust, readable, maintainable and secure. It was no longer just a matter of making it work: it had to last, and be able to evolve cleanly.”
— Managing director, Air Show
“An available, competent and reliable team that explains things clearly, offers pragmatic solutions and works with a real focus on results.”
— Managing director, Air Show

Does your in-house tool need to go beyond your walls?

Before choosing a technology, let’s work out together what should be kept, rewritten or dropped.

Contact us