Login/Signup Platform works correctly on the emulator and on AI companion, but not on my mobile

[palaiologouiason]

I want to see only this after logged out the list, not to see it only after logging out, to remain logged out even after restarting
I noticed that if I use it without the list I added, it works as intended

[palaiologouiason]

Now it worked perfectly.
If I can make it so that if there is a second person who registers, he does not have access to the list data of the first one.
Thanks again for your help

[palaiologouiason]

But now the registration feature is disabled

[palaiologouiason]

Ok now works so I wanted.

[Ramon]

ok...now, have you tested what happen if you try to register two different users? or what happens if you register user1/password1 and then try to login with user2/password2?

[palaiologouiason]

If I register as a second user, the first one is no longer valid.
Every time I register a new user, the previous one is deactivated.
I want all registrants to remain active and if possible not have access to each other's list data

[Ramon]

yes...you have two ways in my opinion...first one, when storing a new user, add a new element to the list stored under the tag "userCreds" and, maybe the best for your case, user the username like a tag and the password like the value. Maybe this very simple example of the second option can help you:

LoginExample.aia (4.1 KB)

[palaiologouiason]

Based on your example of making changes to the application I am more confused.
I don't understand at what point I have to intervene and make the changes

[Ramon]

ok. I'm sorry I created more confusion than help....The important thing is that you understand what is happening and how you can solve it.

The point is that you have only one tag "userCreds" and when user1 registers, then you store the username/passwd in tag "userCred":

• At this point you have only one tag "userCreds" = user1/passwd1

Now a second user is registered. You are storing it in the tag "userCred" the username/passwd of user 2:

• At this point you have only one tag "userCreds" = user2/passwd2

Why? Because you are overwriting the tag. You are nor adding a new item into the tag, but you are writing a new value.

So, you can use the username like the tag so, when user1 registers, then you store the passwd1 in tag "user1":

• At this point you have only one tag "user1" = passwd1

Now a second user is registered. You are storing it in the tag "user2" the passwd2:

• At this point you have two different tags:
  "user1" = passwd1
  "user2" = passwd2

So now, you don't overwrite the tags because you use a different one for each user.

That is what I tried to illustrate with the example. Additionally, in the example, the login username/passwd are validated with the stored ones to check if the user/passwd has been registered before.

[palaiologouiason]

From what I could understand, I made these changes but the problem remains.
Sorry, I'm still very clueless

[Ramon]

I have made some modifications on your aia. Check if you understand it better:

paradeigma_mod.aia (22.0 KB)

[palaiologouiason]

This helped me understand much better.
Thank you

[palaiologouiason]

When we want to make virtual screens, can we use any Arrangement we want, or does each one have a difference in element placement and appearance?
Except: TableArrangement, that I understand its difference and its use, the others require specific elements to be placed in them?

[Ramon]

I'm not sure if I understand you....virtual screens are based on hide and show arrangements. In general, it does not matter what type of arrangement, nor its layout or its content....even a TableArrangement...you can also hide or show it.

Inside of each Arrangement (regardless of type) you design your virtual screen, placing the element however you want. Then you only have to hide/show each arrangement when "changing" of screen.

[palaiologouiason]

Your answer covers me.
It remains to practice on it

[palaiologouiason]

If I use AI2U on localhost, is there a limitation of creating an app with multiple real screens?

[Ramon]

General Tips and Tricks for App Inventor

This list was made by @Taifun Use different screens wisely Before starting to create another screen, first you should think about is it really necessary? See also Building apps with many screens and SteveJG's post about advantages/disadvantages, because in only one screen you also can use vertical arrangements to simulate different screens, just set the arrangements to visible = true/false as needed... If you decided to use different screens, then you should switch them correctly, else you …

Are App Inventor Projects Limited to 10 Screens?

The App Inventor limit is only 10 screens, so you'll have to limit your app to only so many. Also, we'll need more information about your app (what will it do; what information will it contain; and such).

[palaiologouiason]

Of course I'll look to do with just one real screen, since now I know it's possible.
But on my PC I have AI2U and it opens on localhost, in this case can I use more monitors without the mentioned limitation?

[Ramon]

As far as I know, with AI2U you can create apps larger in size. In any case, I have no information about the number of screens and if there are any restrictions on working with AI2U.

[nishyanthkumar]

This is the AI2 community, not the AI2U community.
Also, see (in the same topic @Ramon posted in post #50):

Are App Inventor Projects Limited to 10 Screens?

There isn't a hard limit on the number of Screens in an app. When used properly, multiple screens are a perfectly reasonable way to organize your app. For example, in a app for finding restaurants you may have a main screen with a map, a second screen that shows restaurant data, a third that shows menu contents, a forth that shows pictures of food, a fifth that shows reviews, etc. In this design each screen is a view over some model (cf. model-view-controller design pattern). The wrong way to u…