So my app is kinda a diary where you can talk about what stresses you and how you overcome them. I have to use cloud DB to keep the data after you login and Ive been having issues with that and the day tracker at the end and having what they type save so when they lg out and log back in they can see the list of what they wrote.
Destress_1.aia (524.2 KB)
The app is up there.
In the day tracker screen, you used the wrong clock Now block, in several places.
This one is draggable.
In the Day tracker screen, you are misusing the incoming tag when a value arrives from CloudDB.
You should not change it.
It is there for you to examine it, to decide what to do with the incoming value.
Likewise with the value returned. You should not be changing it, but putting it to work in your app.
Unfortunately, I don't know what you track.
Is it a list of days, or a count?
If it is a list of days, what would you track for each day?
In Screen1, you have a signup button and a Login button.
Both of them need nonblank name and password, but you only tested in the signup button.
You need to use the tag/value you request right.
Instead of what you did
instead,
(draggable)
I'm looking at the StressTalk screen, and I have a question.
How many stressor lists are there?
- One list for everyone, or
- One list per user?
Your current tag structure is set up for One list for everyone all together.
One list per user
and its supposed to track how many days you login into the app
If you are going to store multiple pieces of data under user IDs in CloudDB, then you would have to either store a dictionary under each user name, or extend the CloudDB tags with JOINed suffixes, like /password, /loginHistory, /stressorList.
That would require changing the login and register code a little, in the tag generation and checking.
Also, I recommend pulling in TinyDB in every Screen, and use tag USERNAME to pass around the user name, once the user has passed login or registration.
You current scheme of passing it around at screen open block time depends on every screen doing that in all its screen opens, and would not work for screen close operations.
Pull this into every screen that needs the user name:
Okay, thank you so much i'll try it out!