If the student really wants this app to save information over time, then she will need to use a database to store the information about the entries. That means that the database will need to be set up ahead of time in the "data" portion of App Lab.
There are a few complicated things about this problem, problems that the unit wasn't really intended to address because this is more about prototyping than about making a functional app.
First, a user should only be able to access his or her own entries, not those of other users, so the database will need to hold information about which user owns each entry. When the app reads this information from the database, it should only read the information from the current user.
Second, there needs to be a way to update the display of entries after something is added to the database. That means that the App will probably need to delete any text displays of entries that are still on the screen, then read the relevant entries and display them all from scratch. Otherwise, the displays will be on top of each other. In order to delete them, we need to keep track of them.
Take a look at this sample app: https://studio.code.org/projects/applab/FitPcvICezmmWKPRjlI6NKs-wQHTEu0-0CVakraOw7o
This is far beyond what we would expect students to do in this course, but it is possible with App Lab.