Haplo is best for developing applications where the built-in database and user interface forms the basis of your application.
Here’s how it compares to some alternatives.
While Haplo contains a complete application framework which allows you to do anything you can do with a web browser, it’s best used to build something around a collection of information.
|Almost infinite flexibility of functionality||Best for applications which manage semi-structured information.|
|Appearance and UI completely defined by developer||Appearance and UI largely fixed with defined extension points|
|Simple application takes a week to get going, coding required||Simple application can be built in a matter of hours, no coding required|
|Huge ecosystem of components available to support wide range of uses||Small set of well-integrated and consistent components, focused on solving information management problems|
|Choice of relational and NoSQL databases, full access to all database features||Integrated non-relational object store blending graph database and search engine features, constrained relational database API|
Like Haplo, WordPress provides an extensive out-of-the box configurable web application, from the database to the user interface. On top of this platform, plugins provide specific functionality.
|Blogging engine and CMS||Universal content repository|
|Public publishing of information with ability to manage private information||Primarily designed for working inside a closed team, with a subset of the information publicly available|
|Very simple permissions system||Advanced permissions, able to support rules required by complex organisations|
|MySQL||Built in object store based on PostgreSQL and Xapian|
|Themes to completely customise appearance||Change the colours, add header and footer, insert HTML into extension points, but otherwise fixed UI|
|Hosted commercial version available from WordPress developers||Hosted commercial version available from Haplo developers|
Haplo is often more appropriate than SharePoint for applications involving information management. Features common to both Haplo and SharePoint include:
SharePoint is optimised for enforcing standardised processes. Haplo works best where you require a more flexible approach to information management and are supporting collaboration within professional teams.
|Closed source Microsoft product||Open source with commercial support and hosting available|
|Integrates tightly with other Microsoft products||Supports Internet Explorer from v6 upwards|
|Best used in Internet Explorer||Best used in any standards compliant web browser|
|Authentication via Active Directory||Authentication via internal user database, or pluggable authentication mechanisms including Active Directory LDAP|
|Positional approach: Organised as hierarchical collections of document libraries||Descriptive approach: One namespace with automatic sub-setting based on permissions and metadata|
|Complex information architecture||Easily understood information architecture, with advanced features through simple concepts applied consistently|
|Focus on collaboration||Focus on managing information effectively, as a by-product of working together efficiently|
|Heavy and slow web interface||Lightweight web interface, responds as quickly as a desktop application even on low bandwidth connections|
|Training required||Typical deployment has 100% user engagement, no training required|
|Upgrading customised SharePoint installations between versions is painful||API and data structures designed to allow easy upgrades — we have 6 year old code running on the latest version|
Corrections and clarifications are welcomed.