© 2019 by Kirkness Associate Ltd

Before you can Submit an App

Before submitting your app to us, you will need a Publisher account. The simplest way to request this is to click on the button on the Search for Templates page. Please provide us with sufficient information from which to decide whether we can approve your application.

Submitting a Ninox App

Ninox databases can be exported from your Ninox account as a file and this can then be uploaded to this site. My expectation is that you will know how to do this is you are intending on providing Ninox solutions to clients.

On this site, we do not distinguish between free or chargeable apps - that's entirely down to your choice as a publisher. However, in considering published my own Ninox solutions on this site here are some observations and hints:

  1. You can use the 'Protect this database' option to secure your solution which will mean that your users will not be able to make any changes to it. You can then charge a fee to provide a password with which they can unprotect the database if you wish.

  2. If your solution is protected, you can use the following functions to also make certain features of your solution only available to unlocked installations:

    isDatabaseProtected() -- true if a protection password is set
    isDatabaseLocked() -- true if protected and not in admin mode (password not provided by user)
    isAdminMode() -- true if admin mode has been activated (never true on server-side code, e.g. triggers)

    In the case of my own apps I am going to use this approach to limit just a few useful features (such as sending emails for example).

  3. Make sure in your product information to make it clear what the template is used for, what services, if any, you will provide with it etc.

  4. I would recommend that you provide some help within your app. All of my own apps so far include a help table covering each part of the application.

  5. Remember that your app file will include any data you may have within it - so make sure that you either provide an empty database or provide a simple means for a user to delete all the demonstration data the app is supplied with - I take the latter approach: