[General] App State Beta

[Chanceium]

I like this app, although the UI isn’t intuitive at all. There are missed opportunities everywhere (deleting places, settings only shows up in the map view... etc..) while the UI looks nice, it doesn’t feel nice to use. The beta looks better, but it’s missing a lot of features from the old version. I’d love to see where this can go.

Right now, the beta doesn’t work on mobile, even though the old UI does. Are you planning to create a separate branch for the new beta UI so it can be developed further?

Additional Context

No response

[itskovacs]

Hi @Chanceium 👋!

Sorry for the delay, I've been and currently am on holiday, which explains why TRIP has been a bit unmaintained lately. I'll get back to it as soon as I'm home.

The BETA Trip UI is meant to replace the legacy version (or at least become the default while keeping a legacy option) in the next couple of months. I'm still finishing up features and ironing out issues, which takes some time. Under the hood, there's also a migration from legacy Angular to Angular Signals, which takes extra time since I'm learning it as I go.

I might create a new branch for this feature later, but for now I prefer keeping everything in one place to ensure consistency, even if it's not the ideal workflow. Still learning from mistakes 👍

I was also thinking about creating a poll to gather feedback on the features and UX improvements people would like in the new Trip UI, to make development more collaborative.

Hope it makes it clearer! 🤝

[Chanceium]

Sweet I have a trip coming July and was trying this out!

[Chanceium]

Hi @Chanceium 👋!

Sorry for the delay, I've been and currently am on holiday, which explains why TRIP has been a bit unmaintained lately. I'll get back to it as soon as I'm home.

The BETA Trip UI is meant to replace the legacy version (or at least become the default while keeping a legacy option) in the next couple of months. I'm still finishing up features and ironing out issues, which takes some time. Under the hood, there's also a migration from legacy Angular to Angular Signals, which takes extra time since I'm learning it as I go.

I might create a new branch for this feature later, but for now I prefer keeping everything in one place to ensure consistency, even if it's not the ideal workflow. Still learning from mistakes 👍

I was also thinking about creating a poll to gather feedback on the features and UX improvements people would like in the new Trip UI, to make development more collaborative.

Hope it makes it clearer! 🤝

Can you make a contributing.md and a roadmap and steps to remove the old UI in place for new UI.

[itskovacs]

I'm working alone on the project so I'd rather work instead of doing project management in my spare time too 😓. I like to keep things simple, contributing is easy as contributing. Though I'd rather not have contributions yet on the BETA UI considering I'm still changing and refining the logic and a contribution would probably be integrated to be refacto afterwards.

I'm still thinking about what to implement and how to do it in the BETA UI, and when I talk about the next couple of months I do talk about multiple months. Legacy will still be available for many months if not for ever 👍

Steps are pretty easy as well: finish up the BETA UI to a state where I'm fully satisfied using it then make it the default UI for trips

[itskovacs]

1.36.0 includes several weeks of updates and improvements. I'd love your feedback!

[sjorge]

I wanted to start a discussion for general feedback, not necessarily new feature requests or bug reports, and came across this one that somewhat fits the bill.

This are just some random thought/experience from my end, for now I still find the legacy UI nicer for editing / data overview. But I find the BETA UI nicer for exploring a day or showing it to someone to talk about it/ask for input.

High level BETA feedback

While messing around in the BETA UI without paying attention, I ended up back in the legacy one and forgot I was actually trying to give the BETA UI a try for my quick planning session. I wanted to revise an already planned day for a trip later this year.

The switch to BETA is not persistent, not even within the same session. Navigating back to a different trip will drop you back to legacy, for example. It would be nice if this were persistent within the session or if there were a toggle in the settings.

Plans UI

Clicking on the day header opens the summary at the bottom (nice!), but it doesn't toggle the highlight or even try to focus the map around the POIs for that day.

I was expecting it to perform both the summary and highlight actions, which would also bring the map to the correct location.

Instead, I need to click the ... and select Highlight.

I do like that these can be toggle individually but I think both should happen when clicking the header.

Maybe also move the Summary and Highlight action out of the ... menu and have them near the top as a 'default state toggle'

Where you can toggle summary/highlight and then it just does that when clicking the header?

This is nice, but it would be great if we could drag it to resize too. Depending if I am editing on my desktop or laptop I might want it to be as is width wise or a bit wider so I can read a but more text. Especially on winder monitors that is nice. I think the current size is fine for a minimal/initial size. But being able to drag it a bit wider would be nice.

Item UI

I plan in great detail, probably too much tbh but whatever. e.g. I might have something like this:

Day1:

• 15:00 Check-in (Place = Hotel 1)
• 16:00 Leave Hotel (Place = Hotel 1)
• 17:00 Early Dinner (Place = Some Restaurant)
• 18:30 Walk through park X back to hotel (Place = Park X)
• 19:30 Return to Hotel (Place = Hotel 1)

Day 2:

• 8:00 Leave Hotel (Place = Hotel 1)
• ...
• 20:00 Return to Hotel (Place = Hotel 1)

Day 3:

• 8:00 Check-out (Place = Hotel 1)
• 15:00 Check-in (Place = Hotel 2)
• ...

1. It's not very clear which one I have selected in the screenshot (Hint: Tokyo 2 8:00)

2a. Coordinates stay the same as they are linked to the place, so only show it when in the 'Place Detail' tab to have more room for Text fiend maybe?

2b. Somewhat related, perhaps have the fly to place icon next to the navigate icon to focus on the place on the map.

3. It also shows a 'distance' entry sometimes but it's not readable (truncated) and I'm not 100% sure what is is,... distance to next item? but if so which one as in this view it's not super clear anymore as you lose your place in the UI compared to legacy where it's a nice broken down list.

vs

4. the the "edit pen" icon does something different if you are on the "Place Detail" tab vs an planned item tab in this modal, this is confusing and not very intuitive.

I wonder for 1 + 3 if it's better to just only show the info for the item selected + a button and new window to show all other planned items this place is associated with in the trip. That frees up some of the space in the UI to maybe have a next/prev button to move to the next or previous item in the planning for that day. (That way the distance, if it's to the next place, also makes more sense)

Or alternatively with regard to 2a. this could just be a 2 tabs:

• place details (as now already exists)
• items tables: tab with a table (what are now the individual tabs before place details) that list the day, time, text (and distance to next item?), the 'active' item could then have a slightly different color.

Not really sure here, I have some idea but not sure if any of them are good but I find the current little item dialog to be mix of messy (if the place is used a lot) and a bit confusing. Tables are pretty good sometimes at breaking down info and I find them overall lacking in the BETA UI.

[sjorge]

While on my lunchtime walk I had an idea for the plan ui. I will try to scrible a mock on paper after work if I remember.

[itskovacs]

Just a FYI, I will it carefully this weekend when I am at home, thanks for your feedback 🙌!

[sjorge]

I didn't get arround to it yesterday but something like this:

I was also thinking how this could work better on mobile too. This eliminate the horizontal scrolling and should bring in a bit more structure I think. Just an idea though.

Another thing I hit while playing around this morning to create the little silly mockup/idea image..

Since I like to plan in great detail, the list is rather long which is fine but sometimes annoying if you're reworking a set of days (e.g. shuffling stuff between days at the same location).

In legacy UI I would use the group function and just collapse the days I am currently not actively editing to keep everything compact. In Beta UI I cannot do this:

It would be nice if there is a icon or something to compact it to just the header and maybe summarize it like

"[6] Tokyo 1 (5 Places)" or something.

Edit more feedback, I switched back to legacy UI for now:

Shows the comment not the plan text field, I think it would be better to show the plan text here as that is always (I think) filled in but comment is not. Comments (given text area vs text field) also for me at least tend to be a lot longer and info rich.

I know I can uncheck the comment field but there is no way to check the plan text field. (Well it shows up if I uncheck everything but I would like the place to be there too and that doesn't seem possible. (Maybe this can be a setting in the account dialog to set a default filter. Maybe have text field be above place and comment below. The user can then set his preference in the account dialog. Although I think in general text field + place would be a better default.

Edit 4: I just realized why you default to place + comment as the default plan text field gets copied from the place name!
I think keeping it as place + comment for default is probably OK but I do think it should be possible to configure plan text field to show before or above the place too.

I often edit the plan text to describe something like a train route, checkin/checkout of a hotel (place)....

For me at least it would be great if I can have both the plan text field and place visible, in legacy UI this is not an issue as it shows all three.

If that makes sense.

Edit (forgot how often now):
If you enable the status field, the little colored dot should probably be removed from the text as it's extra clutter and makes the text harder to read.