Knack Poll đź“Š

Ask the Community Get Answers
1

Our good friend @Steve Palmer just posted a poll on LinkedIn.

Your input may help highlight what’s challenging so we can make Knack even better.

Please share your thoughts! :thinking:

1 Like
2

I knew I was not a normal Knack Builder :wink: LOL

For UI, I just had 1h ago a great example. Various times in the past I tried to target an image in a grid view and the CSS code would not work. This time I gave Perplexity a screeshot of the App and the image, and the inspection console opened beneath. Giving it also the working code to do that in a details view.

BOOM! At the first anser it gave me the solution! oh myyyyy. That is the fastest code resolution I ever had with IA. Amazing…

The most time for me is to create various views in a scene for the diferent roles, and testing them. That is the way I structure my apps. Login users pages, and pages rules for roles. I know that the Builders Pages is structured for login per roles. But I don’t see the lean way of copying most of all pages as many roles I have.
And maybe it is not the best way.

imagen
imagen802Ă—736 48.9 KB

3

I answered to your pool with the “User/role” permission because it was not possible to rank the anwers, my second choice it would be “Workflow/automation”
But as far as I know the permission argument is a recurring issue on a lot of low-code platforms. The majority of them address this needs as Knack do: pushing to develop differents UI pieces for each role. The results are:
PRO (for Knack)

  1. the infrastructure supporting the data models is easier to define and scale because is not overwhelmed with complexity of applications

CONS (for Knack developers)

  1. Apps are developed with an hardcoded role-structure. If you have to add a role you need to build new pieces of UI.
  2. Apps are more complex to mantain and update. If you need to introduce a change in a view, you must remember (or keep trace yourself) where else such view is used for others roles.

In summary, it would be better to have a way to handle permissions at a data level instead of acting at UI level. But we can’t complain too much with this, because I am aware that addressing this kind of work it means a total different kind of low-code platforms with an associate total different price… and the ratio price/functionality is still a plus for Knack.

1 Like