Tips + Tricks

Best Practices for Developing in Logi Info Studio

By Jason Murray
Share on LinkedIn Tweet about this on Twitter Share on Facebook

Google defines best practices as the “commercial or professional procedures that are accepted or prescribed as being correct most.” But what exactly does that mean when talking about developing an application in Logi Info Studio?

Turns out, that question isn’t so easy to answer. The power of Logi Info Studio lies in the extreme flexibility it provides the developer in creating web-based applications. Therein lies the issue: The flexibility of the tool often prevents a simple answer when considering best practices.

>> Developer Resource: 7+ Graphics Libraries to Enhance Your Embedded Analytics <<

If we were to ask multiple Logi developers to solve a problem, they would each be successful. But it’s very likely that each of them would utilize a different design to do so.

This is why, when presented with the question of best practices, the Logi Professional Services team relies on the following criteria to evaluate the solution: Does it work? Does it perform? Do you understand it?

Does It Work?

First and foremost, does the solution do what the user requires? Obviously any design that fails this very basic test will not work. This is, of course, also the reason that it is extremely important to both involve your users in your requirements sessions, but also regularly invite them back to iterate through your designs.

Does It Perform?

Second, if what you’ve designed isn’t operating within some form of performance guidelines, you might have an issue. We say “might” because sometimes even the most efficient design will be unable to overcome the limitations of the request. There are instances in which the performance requirement is unreasonable. If, however, the request is reasonable, then any solution falling outside those guidelines should be re-evaluated.

Do You Understand It?

Finally, and this is by far the most critical question to answer, do you understand it? If, at the end of the day, those responsible for maintenance don’t understand the solution, its benefits and limitations, and how to work with it, then it will be a long day indeed when it comes to working on that solution. This is especially important when taking on work that has been performed by outside parties (such as partners or Logi consultants).

If you keep these three tenets in mind when developing in Logi Info Studio, then most—if not all—of the solutions you develop will be successful.

Good luck! And if you need help, don’t hesitate to contact the Logi support team.


Originally published March 14, 2017; updated on August 9th, 2017

About the Author

Jason Murray has spent over 20 years as a software engineer and solutions architect.