We have created an app that allows you to list the drinks and food menus of major cafe chains such as Starbucks and Doutor by store.
The product name and price of each size will be displayed, and tapping the line will take you to the official details page.
At a so-called "coffee shop", you can see the menu slowly from the seat, but with Starbucks, you may have to make an immediate decision in front of the cashier **.
People are lined up behind me, and there is a clerk in front of me ...
In this situation, you can't see the whole menu ** and you tend to make the same safe orders as before **.
** I wish I could scrutinize it slowly while lining up **, so I made it.
URL
All configured on AWS.
(The arrow is the flow of data requested by the user)
Hosted on S3 with SPA by React.
I think the static site hosting function of S3 is enough, but I am going through Cloudfront to support https.
I used Material-UI for the UI framework.
From React, through API Gateway-> Lambda function, json is returned for the menu data stored on S3.
The data is scraped only once a day from the official website of each cafe chain.
The language is Python and I used a library called requests-html.
Speaking of Python, requests and Beautiful soup are famous, but requests-html seems to be a collection of libraries around that and made easy to use.
In fact, it's recommended because it's fairly intuitive to use.
It was my first React app, so I was often confused.
I would like to study more about the dependencies and responsibilities of each component, including redux.
If you set an appropriate ideal, you can make as many web services as you like, but products that can be used by many people are rare.
This app was created as a result of devising ideas with the aim of "** surely meeting someone's needs, whether it's shabby or dull **".
However, I think it is unavoidable that ** no matter how much you think about it, you will not come up with a definite idea **.
Anyway, I will lighten the footwork and accumulate small verifications.
Recommended Posts