Suggestion for AEM Product Team - Pagination in Assets Folder

[#1]

Request for Feature Enhancement (RFE) Summary:	I have a suggestion that I believe would greatly enhance the user experience within the Assets Folder. My idea is to implement pagination within the Assets Folder UI, especially for users with a large number of files. Currently, scrolling through an extensive collection of assets can become cumbersome and time-consuming. With pagination, users can easily navigate through pages of assets, making it more efficient to find and manage their files. I believe that implementing pagination in the Assets Folder UI as a feature would be a valuable addition to the Adobe product suite and further enhance the overall user experience.
Use-case:	Manage files in Assets folder for better user experience
Current/Experienced Behavior:	Currently, scrolling through an extensive collection of assets can become cumbersome and time-consuming for loading assets.
Improved/Expected Behavior:	With pagination, users can easily navigate through pages of assets, making it more efficient to find and manage their files. Also this would help in finding the total number of assets in folder.
Environment Details (AEM version/service pack, any other specifics if applicable):	6.5
Customer-name/Organization name:
Screenshot (if applicable):
Code package (if applicable):

[#2]

 @kautuk_sahni  - Any thoughts about this idea?

[#3]

currently, aem uses lazy loading for assets in assets ui. i am wondering if you are looking for any assets in aem dam then i believe without visualizing it you won't be able to find on which page you will find your assets. so for your use case lazy loading and pagination makes no difference for user experience.

And also to make user experience same for list, card and column view lazy loading makes more sense.

[#4]

@girishb83316758 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference ASSETS-28237. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#5]

@DPrakashRaj agree with your points. Also @girishb83316758 we've discussed internally a bit more and the feeling is that pagination is most useful when you can predict where the desired content will be base on sorting. It would be great to hear more about your search use-cases where you are not finding the "right" asset without a lot of scrolling

[#6]

As the comment form @alext79299363, closing this ticket as of now. 

[#7]

@alext79299363 I ran into a use case for this just this week. I have a folder with hundreds of images (bad decision at the time but it's what we have). I need to edit several images whose names start with "Q". I open the folder, scroll, wait, scroll, wait, etc. until eventually I get to the Qs. When I edit the image, the editor replaces the list. When I finish editing and close the editor, the list is displayed... starting at the top again! I have to spend several minutes lazy loading again and again and again and again and again and again until I get to the Qs.... If I had pagination, I could use a binary search to find the Qs in 3 or 4 clicks, note the page where they appear, and then get to the next image by requesting that page of the list directly.

I shouldn't have to "search" for the Qs, I just want to browse to them, page by page. 

Lazy loading/infinite scrolling is appropriate for scrolling images in a social media feed -- for managing data in an enterprise data management platform, not so much.