What @boomdaba1232rbid states is that something that used to look in a certain way no longer looks that way without him changing anything in his app. You need to appreciate the fact that he spent time designing a beautiful app the way he has and now that something has changed, it is messing up his app and his relationship with his customer. The reason why he used the List Viewer is irrelevant. He used the List Viewer because he used the List Viewer and that is the end of the story. It is not his fault he used the List Viewer because when he decided to do so, it was working well for him and it is nobody’s business why he did what he did. Now, if something changed in the platform which changes the way the List Viewer looks, that is not his mistake. There might be numerous reasons why he does not want to use a Data List Viewer and the bottom line is that nobody can dictate how an application should change because something in the platform changed. We all need to understand that some of us are trying to build serious apps which we will then try to make money off of and at some point we need to be very very very careful when it comes to change management. Since @boomdaba1232rbid can prove with before-after screenshots that the List Viewer looks different than before, it is a bug and that is the end of the discussion. If on every single platform update things “change” without prior notice then I am sorry to say but this is not a characteristic of a reliable platform. We have seen this before multiple times with the most recent example being the default font color on Android which switched overnight from black to grey! When this was reported, the response was along the lines of “You are doing it wrong” and “Deal with it”.
The thing is that nothing compares to Thunkable when it comes to how easy it is to build apps with it; really, nothing comes even close. But what is really killing the platform is the lack of change management and user-oriented support and service. Oftentimes, in similar cases with something not working as before, the responses range from “you are wrong”, “why are you doing what you are doing the way you are doing it?”, “what is the app you are trying to build about?” (even if that’s irrelevant to the problem or its solution), “you have to find a new way to do it” to “you need to live with it”. I am so, so sorry but everyone needs to understand if Thunkable is a platform for experimentation or if it is a platform for serious business. I hope it is the latter.
So coming back to this specific issue, he is using the List Viewer because when he built his app it was working in an acceptable way and no longer does, without him changing anything. Period. This is a bug, it needs to be fixed in the backend and it should be a priority vs. other initiatives like building the Drag’n’Drop interface which imho, it is as wrong as enabling the Web app interface was.
Bugs impacting pre-existing components should be the developers’ top priority as they are braking things which are already in use by tens, if not hundreds of apps built on Thunkable and are pending new releases. It is really worrying that there is a looooooooong bug backlog on GitHub to the point of people losing their incentive to report new bugs there and instead trying to find someone from the Thunkable staff in the forum to help them out. Luckily, there are a couple of good guys out there who are willing to help and we are very grateful they are there for us. But this needs to become the norm and not the exception. I am still waiting since 5 months already to release an app update because of the Status Bar color bug on iOS and I have gotten used to be embarrassed in front of my client (a government organization btw) with the multiple-start bug while seeing resources being assigned on releasing new features when old ones are broken. This is just plain wrong!
I am looking forward for your pov and I am sorry if the above sounds too emotional but at some point, the fact-based truth has to be said.