Feedback/suggestions

Some feedback/suggestions:

  • It would be nice to have the projects ordered by last build time on the website.
  • A slightly more compact start page/projects page design would help to get a better overview. Right now I see only two projects in a maximized browser window. And because of the previous point, the first two projects are not the ones I’m currently working on.
  • It would be good to see the last build time on the mobile website, so I know if the latest changes are included.
  • I don’t need notifications for every build, but I’d be interested in having notifications on error.

Is any of this planned?

Also, the website is sometimes a bit slow/unresponsive, especially when looking at logfiles. It’s not a big issue, but this (and the long build times) makes it a bit harder to debug build problems.

Thanks, great suggestions. I will make sure Nate and the UCB team review them for future sprints.

1 Like

Hi @any_user ! This is great stuff, thanks for sharing.

Project view: ordered by ‘recently built’ would indeed be very useful. We also think a tighter design is the right direction for that page. Just curious: Would you say you visit that page more frequently on mobile device or on a desktop machine?

Build time stamp on mobile: definitely.

Notifications: Yes, we have a lot of feedback in this area. I’m interested to hear your thoughts: Which of these options sounds the most useful:

  • Per project notification on / off
  • Global notifications on / off for both success / fail
  • More collaborator / team member roles, with non-developer roles not getting any notifications at all

Site speed: OK, good to know. If you notice it bogging down frequently and impacting your work, please file a support ticket, and we’ll use that to follow up.

I visit the page more often on mobile as soon as a project is set up properly. I set up a project on the computer, but as soon everything is working I have not often a reason to go to the website except for downloading builds, which I normally do on mobiles. If UCB would support standalone builds, it would probably be a bit different.

On mobile I think it’s not a big issue that the page doesn’t give a good overview, because the only thing I do there is downloading the most recent build. Just on a computer browser I’d love to have a better overview.

I personally only would activate global notfications for failed builds, but I can imagine per project overrides for these settings could be useful.

What would be the use case for a non-developer user? If I understand right, we anyway can send builds to testers without login with the sharing functionality, which seems a good solution. If you ask me, I’d rather put time into support of more platforms to make UCB a fast an powerful build platform instead of starting to rebuild testflight sharing mechanisms.

1 Like

@any_user - excellent, thanks for the detailed follow-up! Much appreciated.

A few more:

  • Counter for the number of times a build has been installed (devices) / played (webplayer)?

  • Local timestamps!

  • A flag or enum dropdown we can populate with states, i.e. so we can flag “Last Good Build”, “Serious Issues”. We had a bug recently which caused all sorts of problems and was present in several builds…with no way to distinguish those builds, and if you want to look at a working historic build you have to go through them all to find which are affected (and there’s no way to hide or remove the bad ones from the list).

1 Like

+1

1 Like

Great! Keep the ideas & feedback coming!

On the web-linked Install landing pages, could we have the first few lines (or even just the opening line) of the Change log displayed; just enough for an at-a-glance summary?