About MenuScouter
Opening the app: the onboarding reality
You download the app, open it, and immediately face a sign-up screen. No guest mode. No browsing without an account. You must create a profile or log in. The process asks for a name, email, and password. It is straightforward but mandatory. Once you are in, the home screen appears. It shows a feed of food recommendations from people you follow. But you follow no one yet. The feed is empty. That is the first reality check. The app is useless without friends. You have to find people to follow. You can search for friends by name or username, but the app does not suggest anyone. You are on your own. This is a significant barrier. The app relies entirely on your social network. If your friends are not on the app, you have no recommendations. The app does not have a public feed of popular dishes. It does not show you trending items. It is a closed loop. Your experience depends on your network. That is a limitation from the start.
The design is clean but basic. White backgrounds, blue accents, simple icons. It looks like a prototype. The navigation is simple: a feed, a search bar, a profile tab, and a plus button to add a recommendation. The app does not overwhelm you with options. It keeps things minimal. That is good for usability, but it also feels sparse. There is no tutorial or onboarding tour. You have to figure out how to add a dish, follow a friend, and find recommendations. The app assumes you know what to do. That is not always true. New users may feel lost. They may not know how to find friends or add dishes. The app could benefit from a simple guide. But it does not have one. You are left to explore on your own.
How the recommendation feed and notifications work together
The core of the app is the recommendation feed. You follow friends, and their dish recommendations appear in your feed. Each post includes a photo of the dish, a rating out of 10, and a short note about why it is worth ordering. The feed is chronological. The most recent recommendations appear first. The notification system alerts you when a friend recommends something new. You get a push notification or an in-app alert. That brings you back to the app. You check the feed, see what your friend liked, and decide if you want to try it. This workflow is simple but effective. It creates a loop: friend posts, you get notified, you check the feed, you engage. The app encourages regular use. The notifications are the key driver. Without them, you might forget to check the app. The notifications keep you engaged. But they can also be annoying. If you have many active friends, you might get too many notifications. The app does not have granular notification settings. You cannot choose which friends to get notifications from. It is all or nothing. That is a limitation.
The interaction between the feed and notifications is the app's main strength. It turns food recommendations into a social activity. You are not just reading reviews. You are seeing what your friends are eating. That is more personal and trustworthy. The app leverages social proof. You are more likely to try a dish that a friend recommends than a stranger's review. The app understands this. It focuses on the social aspect. The recommendations are not anonymous. They are tied to real people. That builds trust. But it also limits the app's reach. If you do not have friends on the app, the feed is empty. The app does not have a way to discover new people or popular dishes outside your network. That is a significant weakness. The app is a closed social network. It works well for groups of friends, but it is not a discovery platform for the general public.
Real-world performance: what actually happens
The app is stable but not fast. It loads the feed, search results, and profiles without crashing. But the response time is noticeable. Each action takes one to two seconds. That is acceptable but not great. The app does not use much data. It syncs recommendations and notifications efficiently. The battery drain is minimal. The app runs in the background without issues. The notifications work. You get alerts for new recommendations. The notification settings are basic. You can turn them on or off. The app does not spam you with promotions. That is a positive. Many social apps flood users with notifications. MenuScouter is more restrained. It respects your attention. The photo upload feature is where problems arise. Multiple users report that uploading photos does not work. The app gets stuck. It "just sits there and thinks about it." That is a serious issue. The app's core function is sharing food photos. If that does not work, the app is useless. The developer has acknowledged this in reviews but has not fixed it. The changelog mentions "upgrade android target version" and "updates to how categories work," but no specific fix for the upload issue. That is concerning. The app works for basic browsing, but the upload feature is unreliable. That limits its usefulness.
The app does not have ads. That is a positive. The experience is clean and focused. There are no pop-ups, banners, or video ads. The app is free, so the lack of ads is surprising. The developer may be relying on future monetization or funding. The app does not have in-app purchases. It is completely free. That is rare for a social app. The app is simple, but it works for its intended purpose: sharing food recommendations with friends. The upload issue is the biggest flaw. If that is fixed, the app could be useful. But as it stands, it is unreliable. Users cannot rely on it to share their food experiences. That reduces its value. The app is a good idea with poor execution. The developer needs to prioritize fixing the upload feature. Otherwise, users will leave. The app has only 3 ratings on the App Store. That is a sign of low adoption. The app is not widely used. That is another limitation. The network effect is weak. If few people use the app, it is not valuable. The app needs more users to be useful. The developer needs to market the app and attract a larger audience. Without that, the app will remain niche.
What happens when you try to upload a photo
You tap the plus button to add a recommendation. You select a restaurant, enter the dish name, and take a photo. You add a rating and a short note. You tap post. The app shows a loading spinner. It spins for a few seconds. Then it stops. The photo does not upload. The app does not give an error message. It just stops. You try again. The same thing happens. You restart the app. You try a different photo. Nothing works. The upload feature is broken. This is a critical flaw. The app is built around sharing food photos. If that does not work, the app is useless. The developer has not fixed this issue despite multiple user reports. The changelog mentions updates to categories, but not the upload problem. That suggests the developer is not prioritizing the core feature. Users have reported this issue on multiple platforms. It is a known problem. The app is not reliable for sharing content. That is a dealbreaker for many users. The app works for browsing recommendations, but not for contributing. That limits its usefulness. The app is a one-way street. You can consume content, but you cannot create it. That reduces its value. The app needs a working upload feature to be useful. Without it, the app is a ghost town.
Get File
App Specifications
| Latest Version | 2.0.87 |
| Uploaded by | Ben Warren |
| Requires Android | Android 7.0+ |
| Category | Social |
| Content Rating | Rated for 12+ |
Technical Details
| Package Name | io.ratemyfood |
| Languages | English |
| Architecture | arm64-v8a |
| Signature | 15b9ef3e3f90eedbf9dbe7450d3d8076a5aac0f1145c6a89d8ab1315ca7a9c16 |
Security & Additional Info
| Scan Result | Secure |
| Package Name | io.ratemyfood |
| SHA‑256 | 15b9ef3e3f90eedbf9dbe7450d3d8076a5aac0f1145c6a89d8ab1315ca7a9c16 |
| SHA‑1 | e187adebf230279b94ec3ac7dddc4fad8efb6e3e |
| App Permissions | 0 |