Software architecture · PC SOFT · Web & SaaS

Extend existing software. Build what comes next.

My WINDEV, WEBDEV and WINDEV Mobile experience now helps me design architectures, maintain and connect business applications, and plan a move to the web when it serves the need.

PC SOFT and architecture

Understand the existing system before changing it

WINDEV remains useful for some installed business software; WEBDEV and WINDEV Mobile address web and mobile uses. The goal is to choose an architecture and an evolution path that fit, without assuming a rewrite.

Assessment and takeover

Understand a WINDEV application

Map WLanguage processes, classes, HFSQL data and exchanges with other systems. Identify dependencies, risks and functions that must be preserved.

Design and integration

Connect applications

Define interfaces between desktop software, mobile apps, WEBDEV portals and web services. Plan access, synchronisation and controls around consistent data.

Gradual evolution

Connect WINDEV to a SaaS product

Separate business functions, expose or consume APIs, then gradually move selected journeys to PHP, Python or JavaScript where the project calls for it.

Maintenance

Stabilise before migrating

Document critical processes, repair fragile integrations and plan migration stages with checks on both data and behaviour.

The approach is chosen after reviewing the application, licences, source code, data and operating constraints.

Solution examples

What the PC SOFT ecosystem can support

These are examples of possible assignments. They are not presented as client applications already delivered by GLOBALTECH.

WINDEV · desktop

Operations management

Software to track cases, quotes or interventions, connected to HFSQL and existing office or management tools.

WINDEV Mobile · field

Mobile capture and access

An app for field teams, with authentication, case access and data exchange through a web service.

WEBDEV · browser

Business portal

An extranet for staff or partners: activity tracking, information submission, roles and journeys connected to the central system.

PC SOFT documents the creation of REST services and their use by applications in this ecosystem. A specific architecture must always be validated for the project.

Experience

Earlier work that remains useful

My career includes development with WINDEV, WEBDEV and WINDEV Mobile across several generations of PC SOFT tools, as well as integration with HFSQL, Access, ERP, CRM and office tools.

Business software

Healthcare and management

Experience including MEDTRA and management projects where processes, data and continuity of service mattered.

Interoperability

ERP and CRM

Earlier work involving ADONIX and Sage CRM, with connections to existing systems and formats.

WLanguage

Beyond screens

Use of classes, threads, sockets, HFSQL and Office automation in professional applications.

These career references are shown without client logos, performance figures or demonstrations of confidential applications.

Current technologies

Web, SaaS and integration work

Web applications and SaaS products are now my main focus. I choose tools according to the need and the level of expertise I can genuinely bring.

PHP · MySQL

Business applications, APIs, data management and SaaS platforms.

Primary practice
JavaScript · Node.js

Web interfaces, browser interactions and services as needed.

Development practice
Python

APIs, data processing, automation and AI experiments.

Development practice
C# · .NET

Basic C# knowledge and currently learning the .NET ecosystem. A request would be scoped with further learning and, depending on complexity, specialist technical support. AI can assist code exploration and checks; the result still requires review and testing.

Learning
n8n · MCP · AI agents

Actively exploring workflows, tool connections and the integration of agents in companies and SaaS products.

Exploring
Technical references

Grounding technical choices

Official resources on the capabilities discussed here:

Your project

Maintain, connect or modernise?

Describe the application's role, its users, data and current difficulty. The first step is to identify a realistic path forward.

Prepare an enquiry