Closed elv-haoyu closed 1 day ago
I put up a design punch list at here
1.
@elv-joe I'm not sure this loading state makes sense when generating hashtags. These skeleton views only make sense when the API returns X amount of results, then the app makes calls for each to get more data.
But for the summary api, the app has no idea how many results are getting returned until the response comes in, in which case, we can just show the normal view. The highlights API(s) are TBD so I can't speak to that.
@elv-joe Would you add a way for the user to select a start and end time for the clip for the Create Summary page? To my understanding, the summarize api cannot create a summary for the full-length video. https://www.figma.com/design/MkBARe4Ld0iSEhChDdeDhq/Video-Editor-App?node-id=673-81856&m=dev
Hashtag - We can take the skeleton off from the hashtags, just keep the loading circle
Highlight - if it turns out that we can't use the skeleton for highlight, we can always use the loading circle instead
Clip start and end time - will add!
All fixed/added.
Adjust the widths of the search index and search input boxes. The search input box should be wider than the search index box to better accommodate longer query terms and improve usability.
Please ensure that only non-empty tag tracks are displayed. The
shot detection
andshot tags
tracks should be excluded, as the former represents the start and end times of the clip, and the latter is the aggregated result of all other tracks.Add a
Generate Summary
button that triggers the summary API when clicked @elv-joe.