PC Soft

If you require a broad hiring pool and want to avoid proprietary ecosystems

• WLanguage and WinDev-specific expertise are less common globally than Java/.NET/JavaScript ecosystems.

If your enterprise procurement requires SOC 2 / ISO 27001 certificates to be publicly documented

• Such certificates were not found in the publicly accessible materials reviewed; buyers should plan for extended security reviews or require vendor attestations.

If vendor licensing model stability is a top risk factor

• Changes toward subscription/SaaS licensing and perceived reductions in prior license rights are recurring customer concerns.

If you need deep cloud-native and DevOps composability

• Teams requiring best-of-breed open tooling (Git-native workflows, standard CI/CD stacks, large third-party package ecosystems) may prefer mainstream stacks.

Licensing / subscription transition risk

• User reports describe perceived loss of access to versions previously paid for when transitioning to subscription models; this represents a business continuity risk for long-lived codebases.

Platform-specific mobile limitations and deployment issues

• Community posts indicate recurring issues with iOS deployment workflows, Android compatibility, and SDK/tooling synchronization. These items may be version-specific but reflect potential friction in mobile toolchains. (https://forum.pcsoft.fr/fr-FR/pcsoft.us.windevmobile/3232-issues-regarding-android/read.awp)

Ecosystem "closedness" perception

• Community commentary indicates a perception of limited interoperability with mainstream workflows; this is sentiment-based but relevant to hiring and integration decisions. (https://news.ycombinator.com/item?id=21352508)

Roadmap / future features

• No consolidated public roadmap was identified in the reviewed sources. Forum announcements indicate periodic version releases. (https://forum.pcsoft.fr/en-US/pcsoft.fr.windevmobile/50962-pcsoft-version-2025-disponible-finale-windev-webdev-windev/read.awp)

Integrated suite for rapid delivery

• The WINDEV/WEBDEV/WINDEV Mobile documentation describes a comprehensive environment with shared tooling across the suite. (https://doc.pcsoft.fr/en-us/?1410086964=&name=windev_mobile_concepts)

Built-in database and configurable encryption features

• HFSQL documents encryption options (AES and connection encryption) that can be relevant for teams seeking an embedded database approach with vendor-supported security options. (https://blogs.pcsoft.fr/fr/chiffrement-donnees-hfsql-aes-privilegier-securite-maximale-egalement-performances-optimales/281474976710761/read.awp)

Cross-platform targeting from a unified environment

• WINDEV Mobile is presented as an environment to build Android and iOS applications from a single development environment. (https://doc.pcsoft.fr/en-US/?1410086964=&name=windev_mobile_concepts)

Caveat on unique selling point claims

• Some vendor or partner claims (for example, large development speed improvements) are not independently validated in the reviewed sources and should be verified through pilot projects or benchmarks.

Review-platform summary (G2)

• PC Soft vendor page on G2 indicates an overall rating in the mid-range across available reviews covering WinDev / WinDev Mobile / HFSQL listings under the vendor. (G2 vendor and product pages)
• HFSQL on G2 has few reviews, limiting robustness for that specific product. (G2 product page)

Positive feedback (examples)

• G2 (positive themes)
  • Users note multi-platform capabilities and the ability to target multiple mobile OSes via WinDev Mobile in some contexts. (G2 vendor and product pages)
  • HFSQL reviewers cite straightforward database control/management and useful built-in functionality. (G2 product page)
• Reddit / community (positive/neutral)
  • Some developers report that starting with WinDev helped them deliver business applications; several users characterize the training materials as clear and structured. (Developer community threads)

Negative feedback / complaints (examples)

• Trustpilot (windev.com)
  • Trustpilot contains several recent low-rated reviews; some reviewers report dissatisfaction with licensing changes associated with subscription/SaaS transitions. (Trustpilot listing and user reviews)
• G2 (negative)
  • Reviews cite licensing issues and occasional stability concerns. (G2 vendor pages and reviews)
• Hacker News (critical discussion)
  • In community discussions about non-English programming ecosystems, some participants describe WinDev as closed and report interoperability concerns; these are anecdotal but indicate perceived lock-in risks. (Hacker News thread)
• Reddit (French dev communities)
  • Threads discuss changes to licensing models, the acquisition, and concerns about vendor lock-in; some posters mention porting codebases to mainstream stacks such as C# in response. (Community forum threads)

Why customers chose this product over alternatives (common patterns)

• Rapid delivery for CRUD-heavy business apps, integrated tooling, and familiarity with the WLanguage ecosystem.
• Long-time users often remain due to accumulated codebase and organizational familiarity.

Why some customers left for competitors (churn reasons)

• Licensing model changes (perpetual to subscription/SaaS) and concerns about perceived reductions in previously purchased rights.
• Vendor lock-in concerns and a desire to move to mainstream, more widely supported stacks (e.g., C#/.NET).

Specific outcomes customers achieved (with metrics when available)

• Third-party case study (Kertios): reports time savings after building a new ERP in WinDev on SQL Server; quantitative KPIs were not disclosed in the partner-written case study. (Partner case study / vendor partner materials)

• Kertios describes rebuilding an ERP for an art/wine security and storage provider using WinDev with SQL Server and reports time savings and workflow improvements.

• This is a partner-produced case study and may be subject to selection bias toward a successful outcome.
• No quantified KPIs are provided, limiting comparability and independent validation. (Published on the partner/consultancy website)

Company sizes

• Likely best fit:
  • 20–500 employee organizations building internal business applications.
  • 500–5,000 employee organizations with a centralized IT team that standardizes on the PC Soft suite for multiple apps.

Industries and verticals where adoption is strongest (with customer examples)

• Common fits include business operations/management, industrial applications, medical administration, and other operations-heavy verticals based on documentation focus and community use cases. (Official product documentation and tutorials)
• Example case: an ERP for an art/wine security/storage provider built with WinDev (partner case study on a vendor partner site).

Roles and personas: decision makers AND end users

• Decision makers
  • Head of Software Development / IT Director
  • CTO (SMB)
  • Application development manager in industrial/operational organizations
• End users
  • Business operations staff using custom internal apps (customer service, logistics, field operations)
  • Developer teams delivering and maintaining line-of-business applications

Pain points and challenges the product addresses

• The need to build database-backed applications rapidly with reduced toolchain complexity.
• The desire for a single suite that covers UI design, reporting, the data layer, and deployment.

Qualification criteria: what makes a GOOD fit

• Strong preference for a single-vendor integrated suite rather than a composable toolchain.
• Applications are mainly internal, line-of-business, and CRUD/reporting heavy.
• The organization accepts a proprietary language/tooling trade-off in exchange for faster delivery.

Deal disqualifiers: what makes a POOR fit

• A strict requirement for open standards and open-source tooling only.
• Procurement requirements for publicly documented SOC2/ISO 27001 certificates.
• Need to hire large numbers of developers globally in mainstream languages.

• WINDEV (desktop / client-server business apps)
• WEBDEV (web applications)
• WINDEV Mobile (mobile apps)
• HFSQL (the vendor’s embedded and client/server database engine)

• SMB to mid-market organizations building internal tools, line-of-business apps, and vertical/industry solutions.
• IT consultancies and integrators delivering custom ERP/CRM-style applications.
• Teams that prefer fast UI/data app construction and tight coupling to built-in tooling over an open ecosystem development approach.

• RAD / 4GL tooling
• Low-code / rapid enterprise app development (developer-centric)
• Database-backed business app platforms