Faculty Page Layout Design

[STAR-173]

Hey Rahul,

Firstly, Amazing job.
I was going through you new modified classpro application. Have to say really impressed by what you've build.

• Amazing UI
• Great UX considerations
• Added additional official links and support links which are always useful throughout the semesters
• Great SGPA Calculator, no hassle of manually putting your subject credits

And not to mention the one of the actual working and up to date resources list.

You have got it absolutely right to absolute details.

One thing which was bothering me when I went to the faculty page was its layout choices. Its better recommended when you have such vast amount of data (2000+ faculties) and specifically person data, to order them into some kind of Card layout for easy accessibility and improved visibility. But you have opted for a list kind view (to be honest, its UI is also great).

Can you provide some insight if this was a carefully taken decision or just something which you'll working upon later down the road.

Anyways, Amazing job once again. Keep up the good deed.

[STAR-173]

Also while going through the code. I saw you're storing all these data inside the application itself with image URL already there in it. wouldn't it be good practice to store these data in some database and retrieve it from there ? So to reduce the size of your final build.

[Rahuletto]

It will definitely reduce the size of the build but the issue is, when used in database that increased our egress or send/receive calls, we were on free tier of the supabase and while we are making Faculty page we already reached the free tier limits, so we opted into adding it into the application itself

[Rahuletto]

But still database is not that a good practice as u are not going to update it very often, so using local file will be faster to retrieve so for such case i would say locally storing the data could be a better practice.

[Rahuletto]

Also retrieving faculty data for your Courses page should also be taken into count, as that increases database requests and our bandwidth (sharing data between).

[STAR-173]

If that's a free tier limit issue, it probably fine only.
And the page loading times are not compromised for now bcs of the lazy loading, So i think this solution works for now.

[Rahuletto]

List and Card view hmm, ClassPro was meant to be designed mostly for mobile devices. Using a card layout might make it better for the desktop device but we intended the use for mobiles mostly, using a card layout in mobile is useless as it takes unwanted padding space instead. And users always tend to lose interest when they see repeated elements such as a grid of cards due to the repetition. This is a big headache to choose one reliable way especially for UX as both has its drawbacks, so list would be a safer choice as most will not scroll down rather search it up to get the faculty instead.

[STAR-173]

Cool, Thanks for the clarification