A quotation starts before the PDF
Preparing a commercial proposal means organising company details, describing the work and keeping a version that can be found later. Exporting is the final step in a workflow that also needs editing and storage.
BudgetApp brings these tasks into a desktop application built with Python and PySide6. Its documentation describes creating and editing quotations, storing company fiscal details, listing saved documents and exporting PDFs. The interface includes Spanish and English.
What the documented workflow covers
Three tasks form the core of the application:
- Maintain the company details used in quotations.
- Create, edit and consult saved quotations.
- Export a proposal to PDF for review or delivery.
The code separates models for quotations, quotation lines and companies. For someone adapting the project, this provides a concrete starting point: business entities, data access and document generation already exist.
Local SQLite and remote MySQL are different choices
BudgetApp supports local SQLite storage and remote MySQL storage. The choice affects where data lives and what infrastructure is needed.
Local storage may fit a workflow centred on one computer. Remote storage introduces an external database whose configuration and access need review. MySQL support alone does not establish automatic synchronisation, concurrent collaboration or conflict resolution. Those behaviours need checking before planning shared work.
It would also be inaccurate to describe the whole application as exclusively offline: configuration matters. Our article on local-first storage explains why this distinction helps when evaluating privacy.
An exported PDF has its own lifecycle
Exporting lets someone read a quotation without having BudgetApp. Once created, the file can be sent, duplicated or left in a shared folder.
Before sending it, review the recipient details, contents and file location. Access to the source code does not control what happens to a copy that has already been exported.
What to review before adapting it
The project remains in development. Its README describes a Clean Architecture-inspired structure and acknowledges outstanding limitations, including mixed responsibilities in some classes and dependencies on concrete implementations.
Start an adaptation with sample data and check the complete create, edit, save and PDF workflow. Then review the database configuration and the requirements of the intended activity.
See the BudgetApp overview for a summary and the repository README for project instructions. This article summarises available documentation; it does not validate a particular installation.