Logiak Approach
The aim of Logiak is to help people be
pragmatic
efficient
agile
Pragmatism and detail
Everything is a trade-off, and Logiak embodies one particular trade-off. Which is it?
Many No Code systems focus on presentation and lack logical power. They may look exciting initially, but you can’t achieve the processing you need. You can link screens, but there is often not much more to it than that.
Logiak is the counter to this. It offers components which are not low-level UI components but high-level packets of functionality, from which Apps can be assembled in no time.
And, importantly, one of those Components is there to include Processes in the mix, and in a Logiak Process one is able to do very fine grained processing and updating of data.
In a Process, you can achieve logial complexity in a scaleable and maintainable way. It has been demonstrated that analytically minded non-programming experts can fashion their knowledge into useful interactive applications by developing Logiak Processes.
We think that Logiak is appropriate for organization-internal Applications.
Logiak is for programmers and non-programmers alike. Programmers will be aware of what time this saves them. Programmers will be aware not only of costs saved in building a system, but in maintaining one.
Logiak has two main user categories:
- Those who want to create data handling Apps rapidly, robustly, flexibly
- Those who want to create knowledge-based Apps, for example embodying regulatory or diagnostic knowledge and who need non-programming experts to be involved in their construction.
Logiak is for you if you need logically expressive and presentationally pragmatic.
Logically expressive
What we mean by this is: with Logiak, in particular with Processes, you can do a lot of the logical computation and numerical calculation you might want to do with code.
Logiak is expressive in that sense.
The Logic Just Flows
Process Logic is fine-grained, but there are logical possibilities not only in the Processes, but also in the Components and in their Flow .
-
So you can configure field conditions for Lists and Data Tables.
-
You can use switches in Actions components to enable and disable options for the user.
-
You can display/hide elements with Custom Layouts, based again on Switches.
-
You can also use Switches to make the Component Flow itself adaptive to the state of the data.
Software is hard
Logiak is offered with keen awareness of just how difficult building software is.
While programming languages and techniques are involving and improving all the time, programming remains, quite frankly, humbling.
No programming language which makes it easy. Some languages make it incrementally, marginally, easier.
At the same time, the demands for software are in a permanent exponential increase.
Logiak makes things easier
Logiak eases some of the complexity by removing coding from the equation.
-
Apps running on iPhone without having to deal with XCode, or Swift.
-
Apps running on Android without having to encounter Gradle, or JetPack, or Kotlin.
-
Apps running on the web without knowing anything about JavaScript, CSS, Apache, Tomcat, Java, React, Angular whatever.
Logiak doesn’t make your problem easier
Having said this, its important to say that Logiak doesn’t make the actual problem you are addressing simpler though.
You still need to be pretty analytically minded in order to successfully tackle problems of any complexity.
What does 100% NO CODE mean?
No code means you do NOT have to learn:
- JavaScript
- CSS
- Python
- React
- Java
… or whatever
If you know some HTML you can use it, but you don’t need to.
If you know some Markdown, you can use it, but you don’t need to.
Logiak is a Lightweight SaaS
What we mean by this is Logiak seeks to keep out of your way.
It doesn’t want to be a burden for you, nor a chain around your neck.
Logiak seeks to help you to be pragmatic, agile, efficient.
Minimal UI actions for maximal results
We don’t think it is a great thing to have lots of components. It sounds good, but less is more can be an important principle.
We aim at minimalism in the sense of reducing to a minimum what you need to know, and to look at, in order to address your problem.
So we don’t want you to be paging through hundreds of components to find the one which might change your life.
For the same reason we have tried to minimise the concepts within the configuration UI.
Just for one example: selecting which users to send mail to uses the same UI as does filtering a list.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.