Comparing the Norsync platform to competitors

This table indicates the cost of creating a simple app using the Norsynch platform, vs. using a competitor.

Task Norsync Other
Developing the GUI 10 10
Defining the database 2 3
Defining synchronization rules/conflict resolving algorithms 1 8
Defining segmentation rules/filtering or data retrieval 1 4
Data handling layer in SQL (Norsync) or proprietary API (competition) 6 10
Adding encryption 0 3
Adding client admin 0 2
Testing of sync and filter 0 12
Testing of actual app 5 8
Total 15 50

As these numbers indicate, apart from GUI development, the Norsync platform slashes costs by more than two thirds. And as Norsync uses industry standard SQL, there is no need for developers to learn a new API, which would be the case for other sync technologies. Filters and conflict resolving is defined using an intuitive GUI.

This means no cost for competence building, and no problem swapping developers.

Application Life Cycle Cost (ALCC)

Maintenance cost is also significantly reduced, ensuring that the application life cycle cost is far less for the Norsync platform. The ALCC includes costs to keep APIs compatible with the total environment, including iOS, Android, Windows, Cordova, JQuery etc. In addition there are costs related to maintain competence on specific APIs.

The ALCC using the Norsync platform will be less than 1/3 of cost incurred when using any of the competitors’ platforms.

Task Norsync Other
Developing the GUI 8 8
Altering the database structure 1 3
Altering synchornization rules/conflict resolving algorithms 0.5 6
Altering segmentation rules/filtering or data retrieval 0.5 3
Altering handling layer in SQL (Norsync) or proprierary API (Other) 1 8
Testing of sync and filter 0 12
Testing of actual app 4 6
Total 7 38

A main difference is however that Norsync uses standard components wherever possible, while the competitors all have defined their own proprietary APIs. Using Norsync’s approach you may even develop an app using industry standard tools, and then add synchronization afterwards, because synch rules are not expressed within the app, but as part of the data definition.

This boosts efficiency and keeps maintenance cost at an amazingly low level.