Aquela Receita

Opening the App and the First Thing You See

The app loads. A splash screen appears. Then the main interface shows a grid of recipe thumbnails. Each thumbnail has a photo and a title. The design is clean. The colors are warm. It looks inviting. But then the ads start. A banner at the bottom. A pop-up after a few seconds. A video ad that autoplays. The experience shifts from cooking to dodging interruptions. The app promises simplicity. The ads make it complicated. This is the reality of Aquela Receita today. The core functionality is there. Recipes are well-organized. Each one has a list of ingredients, step-by-step instructions, and a video. The videos are short and clear. They show the process from start to finish. The production quality is decent. It is not professional-grade, but it gets the job done.

The app is designed for home cooks. People who want to make something quick and tasty. The recipes are mostly Brazilian. Feijoada. Brigadeiro. Pão de queijo. The app does not pretend to be global. It is local. It is practical. The instructions are in Portuguese. The measurements are in grams and milliliters. The temperature is in Celsius. This is an app for Brazilians, by Brazilians. The developer is based in Sertãozinho, São Paulo. The address is listed on the Play Store. This level of transparency is uncommon. Most apps hide behind a PO box. Aquela Receita does not. The developer's email is also provided. [email protected]. Users can reach out directly. Some do. The reviews show a mix of praise and frustration. The praise is for the recipes. The frustration is for the ads and the bugs.

The Clash Between the Promise and the Reality

The app's description says it offers a "more practical, easy and delicious way of cooking." The reality is different. The ads are intrusive. They do not disappear. Users have reported this repeatedly. One review on the Apple App Store says: "O aplicativo era ótimo, agora tem propagandas que não somem de jeito nenhum e não funciona off-line." (The app was great, now it has ads that do not disappear at all and it does not work offline.) Another user says: "Baixei o app há mais de um mês e até hj não consigo usar pois só mostra carregando." (I downloaded the app over a month ago and still cannot use it because it only shows loading.) These are not isolated incidents. They are consistent patterns. The app's core feature — the recipes — is solid. But the delivery mechanism is broken. The ads are not just annoying. They are disruptive. They make the app feel cheap. They undermine the trust that users place in the app. A cooking app should be a tool, not a billboard. Aquela Receita blurs that line.

The premium subscription is supposed to fix this. For R$ 2,90 per month (approximately USD 0.49), users can remove ads and access additional features. The subscription is available on the iOS version. It is not clear if it is available on Android. The Play Store page does not mention it. This is a missed opportunity. Users who are frustrated with ads would pay to remove them. But the app does not make this option clear. The result is a user base that is angry and unwilling to pay. The app's revenue model is broken. It relies on ads that drive users away. It offers a subscription that users do not know about. This is a classic case of a good product with a bad business model. The recipes are excellent. The execution is poor. The app has over 1 million downloads on Android. It has a loyal following. But that following is eroding. The reviews are getting worse. The complaints are piling up. The app is at a crossroads.

The Technical Performance and the Developer's Approach

The app's technical performance is inconsistent. Some users report smooth operation. Others report crashes and freezes. The loading screen issue is particularly concerning. A user downloaded the app over a month ago and still cannot use it. The app only shows a loading spinner. This suggests a problem with the initial data fetch. The app likely downloads recipe data from a server on first launch. If that server is slow or unresponsive, the app gets stuck. The app does not handle this gracefully. There is no timeout. There is no error message. There is just a spinning wheel. This is a basic UX failure. A simple fix would be to add a retry button or a fallback to cached data. But the app does not have this. The offline mode is also broken. Users have reported that the app does not work offline. This contradicts the app's description. The description implies that recipes are available offline. But the reality is different. The app likely requires an internet connection to load images and videos. This is a design choice, not a bug. But it is a choice that alienates users. Many people cook in areas with poor internet. They need offline access. The app does not provide it.

The developer, Murilo Henrique de Araujo, is a solo developer. The app is a one-person project. This explains the inconsistent quality. Solo developers often struggle with testing and support. The app has 35 reviews on the Play Store. That is a small number for an app with 1 million downloads. This suggests that most users do not leave reviews. The ones who do are either very happy or very angry. The happy ones praise the recipes. The angry ones complain about the ads and bugs. The developer's response is mixed. Some reviews get a reply. Others do not. The app's update history is sparse. The changelog for version 2.2.2 says "Ajustes para uma melhor experiência do usuário." (Adjustments for a better user experience.) This is a generic phrase. It does not specify what was fixed. It does not inspire confidence. Users want transparency. They want to know what changed. The developer does not provide that. This is a missed opportunity to build trust.

A Specific Technical Detail About the APK and Its Permissions

The APK file for Aquela Receita is available on multiple third-party sites. The latest version is 2.2.2. The file size is 35.41 MB. It requires Android 6.0 or higher. The architecture is arm64-v8a and armeabi-v7a. The app does not request any dangerous permissions. It does not ask for location, camera, or contacts. This is a positive. The app only needs storage to cache recipes and images. The app's data safety section on the Play Store states that no data is shared with third parties. However, it also states that data is not encrypted. This is a concern. User data, such as recipe preferences and search history, is stored in plain text. The app does not collect personal information, but it does collect "Personal information, Financial information, and 2 other types of data." The exact nature of this data is not specified. The developer's privacy policy is available on the website. It is a standard policy. It covers the basics. It does not go into detail about data retention or deletion. Users can request data deletion, but the process is not clearly outlined. The app's security is average. It is not a banking app. It does not handle sensitive data. But it could be better. The lack of encryption is a missed opportunity. It would take minimal effort to enable encryption. But the developer has not done so. This is a technical detail that most users will not notice. But it matters. It matters for trust. It matters for long-term retention. The app is free. It has a loyal user base. But it is not living up to its potential. The technical issues are solvable. The business model is fixable. The question is whether the developer will take action.