Creating a to do list in an app for easy to describe tasks

I want to make a to do list for simple items to add to an existing app. Ideally, I do not want each item in the list to link to a details screen. I can use the list component to display the items as a basic list, and not link to a detail screen. That is OK.

But I would like a check box or some other way to mark tasks as completed without leaving the screen. Even if I link the list to a detail screen so that there is the option to add / modify details for more complex tasks, I would still like users to be able to mark completed (or another status) without leaving the main tab where the list of the day’s tasks is displayed.

I think this is not possible, and any change in status would have to be made on a detail page linked to the list item.

Am I correct or not?


Paul Winterbottom

no, you can add another list in the detail view of that list

If your project is an App project, then there is a Checklist Style layout option for inline lists.

If your project is a Page project, then you can add a Custom Collection, which let’s you place a text component as well as a switch component on each list item.

Both options don’t require you to leave the screen.

1 Like

Thanks. But when I use the checklist option - even when I select “none” for the action when someone selects the list item - there is still an arrow on the right as though it is linked to a detail screen (which it is not). This doesn’t happen in ordinary list view, but then there is no checklist box.


You could use a tiles layout, and then configure the list action so that tapping an item toggles the status.

The below example is not exactly what I mean, but should give you a picture of what I’m getting at:


Checklist will be coming to Pages very soon! Keep your eyes peeled!


That’s a good idea - I will have a go.

I have never tried Pages (because I am only interested in mobile apps). I now know that it is going to replace Apps in the future (even for mobiles) - is it easy to get used to?

very hard… but… doable :wink:

For the most part, it’s pretty much the same. The Data Editor is exactly the same - you get the same computed column choices and they all work exactly the same as they do in Apps.

Actions work the same as they do in Apps. But you have a lot more flexibility with Actions in Pages. For example, many components allow you to configure multiple actions.

The layout builder is essentially the same. The only difference is that you have some different component choices in Pages. Things like Containers and Custom Collections. But these are easy to get used to and and actually make it much easier (and faster) to build. If you’re building for mobile, you can view your Pages project in the builder as it would appear on mobile.

There are a few Apps components that haven’t yet been made available with Pages, but I wouldn’t be too concerned about that. Glide have made it very clear that all of their effort is now going into Pages, and so we can expect to see lots of new and improved components landing in the coming months.

I think you’ll find that most people* that have been building with Pages for a while will tell you that they find it much more enjoyable than Apps.

* perhaps with one notable exception :wink:


I strongly disagree with @Darren_Murphy, Mobile look is horrible! elements are way too big, just the header and buttons block takes almost the whole view, without being an expert in HTML and good in math and logic… you won’t make it look good.
It takes me 3 times more time to make a Page than an App.

Ps… the desktop view is also limited with big margins! that makes no sense… Pages should be designed for desktops… not tablets or small laptops.