Contact Nimi

Software projects technical support

Before requesting software projects related technical support please ensure that:

Invalid requests might be discarded without notice.


The information above is non-binding and intended for general information purposes only and has been provided in good faith. All trademarks and registered trademarks are the property of their respective owners.

Google is a registered trademark of Google Inc. Google+™ social service is a trademark of Google Inc.

Frequently asked questions


How quick is response to received messages?

Messages are replied ​on a daily basis.

Quicker reply with social media

Social media have shorter propaga­tion delay as being ​on the same network, thus can be replied sooner.

What if did not receive any reply?

In case you did not receive an reply:

  • If message is a part of already start­ed corr­espondence ​or addr­esses complex matter — it might require additional process­ing time.
  • If you choose e-mail as con­tact mean — then we might be unable to reply, as reply is being reject­ed by the mail server.
  • Your message might have been dis­card­ed as being invalid.
What should software project related technical support request consist of?

When requesting technical support - please provide clear ​and detailed descrip­tion of issue you are writing about:

  • Include follow­ing details:

    • Full project name ​or its abbrevia­tion e.g:

      • Incorrect ✗:
      • Accept­able:
      • Correct ✓:
        Nimi Places
    • Project version e.g:

      • Incorrect ✗:
      • Accept­able:
        from last week
      • Correct ✓:
    • Name, version ​and architecture of used operational system.
    • If applic­able — receiv­ed error details e.g:

      • Incorrect ✗:
        desc. large screenshot of received error message box
      • Accept­able:
        Module XYZ could not be initialized
      • Correct ✓:
    • Steps to reproduce issue e.g:

      • Incorrect ✗:
        clicked Y
      • Correct ✓:
        enabled X, Y and Z, then clicked Y
  • Avoid:

    • Using acronyms, jargon, non-standard abbrevia­tions.
    • File attachments.

Properly composed request will help us to provide quicker ​and better response.