search

SENG480a-NutriDine / mobile

The mobile app
Apache License 2.0
0 stars 0 forks source link

Homepage #29

Closed salamf closed 9 months ago

salamf commented 9 months ago

General overview of homepage with sample data for placeholders.

Screenshot 2024-02-11 at 2 47 31 PM
salamf commented 9 months ago

Overall looks great! Couple high-level questions for ya

  1. What is the search bar going to do once it gets hooked up? Wondering how it will work from a user and a developer POV. (child components filtering parent data is never an easy implementation). Also wondering if this 'home page' will be for scrolling by menus/restaurants and finding ideas, while another page will offer dedicated macronutrient filters or something??
  2. What is the down-caret in the layout footer doing? Where does it take you?

  1. I was thinking it can either be used to search for food items (e.g. spaghetti) and then wed have another page where you could search for specific restaurants (like we had in the original mock up) OR we could make it such that you can search for food and restaurants on that search bar and then just skip the page for searching for restaurants, does that make sense?

And yes, homepage mostly for browsing and stuff, and then another page for a dedicated macronutrient filter search. Also if you have better ideas then we can definitely go with those!

2. The carrot in the navbar was there before I changed anything, and I'm pretty sure it's supposed to represent the absence of a specified icon in a page. Clicking it now will lead to the test database page you originally created. I'll get rid of it on my next update.

johnmck95 commented 9 months ago

I was thinking it can either be used to search for food items (e.g. spaghetti) and then wed have another page where you could search for specific restaurants (like we had in the original mock up) OR we could make it such that you can search for food and restaurants on that search bar and then just skip the page for searching for restaurants, does that make sense?

And yes, homepage mostly for browsing and stuff, and then another page for a dedicated macronutrient filter search. Also if you have better ideas then we can definitely go with those!

The carrot in the navbar was there before I changed anything, and I'm pretty sure it's supposed to represent the absence of a specified icon in a page. Clicking it now will lead to the test database page you originally created. I'll get rid of it on my next update.

  1. Might be worth thinking about how we want to hook up the search bar carefully for milestone 2 if it's not going to be used to filter by macros (our main use case). I think it might be worth pitching the idea to the mentors that the home page is mainly for revenue - users can filter by foods/restaurants which drive advertisements, and restaurants can pay to be near the top of the home page. The search bar is only for filtering restaurants and food items. Then we have a totally separate macronutrient filtration page which is the core reason people come to the app. If we don't have our main use case on the home page, i think we'll need to be able to explain why not

  2. Perfect!