Known Issues

• "Exceeded Macros" alert on eatery page only displays when following link from the list of dishes, not from the map. If you arrive at the eatery page by following the link from the map view, or by entering the URL directly in the browser, exceeding your selected macros will not trigger a warning.
• Find Meals page only displays top 20 matching meals from seeded eateries within 5km of user location. This is not so much a bug as an a conscious decision not to overengineer a minimum viable product. All the fake eateries (100 total) are in Singapore, so visitors who are not physically in Singapore, or who are in a location without available eateries within 5km, will not be able to find any meals. Sorry!
• Stripe webhook not firing? Upon making a test payment, you'll be redirected back to the Order page, but the order status does not update from "pending" to "paid".

About Macrotery

Macrotery is a project that originated as a final project at Le Wagon batch #454 (Singapore), by Allen Chung (allenchungtw), Stephen Das (steevesd), Grace Teng (pelicularities — that's me!) and Zack Xu (konfs). The idea is simple: what if you could search for food at eateries near you based on their protein, carbohydrate and fat content?

Many people track the macros of the food they eat in order to meet their health and fitness goals. Those who are looking to lose weight might aim to keep their overall caloric intake low. Bodybuilders generally want high protein, low fat meals. Endurance athletes fuel their training with lots of carbohydrates. Unfortunately, this makes it difficult for individuals tracking their macros to eat out, since it can be hard to find food that fits their macro targets in eateries.

Macrotery is a minimum viable product / proof of concept aimed at solving this problem. Users enter their macro targets, and can then search for meals at nearby eateries that match their macro targets.

Macrotery Redux

After our Le Wagon bootcamp ended, I decided I wanted to continue working on Macrotery for a little bit more, so I forked the Github project and continued working on it as Macrotery Redux. I had two main goals with the Redux version:

• Completing the "unhappy path": all the work on Macrotery was directed at completing the happy path for our bootcamp demo. There were multiple niggling bugs and UI issues that would have resulted in a sub-par user experience for a real user, which I wanted to reduce.
• Fixing layout issues: Macrotery is a Progressive Web App (PWA), meaning it can be used on desktops, laptops, tablets and mobile phones. However, our bootcamp demo was optimised for mobile only, and was barely usable on any device larger than a mobile phone. Macrotery Redux is not truly responsive in that it does not make use of most of the screen space available on larger devices, but I wanted to make it look more presentable on non-mobile screens.

Status

No further work is being done on Macrotery Redux, as I've moved on to other projects. You can check out what I'm up to here.