I spent time with מתכונית - מתכונים מבלוגים as a food and drink app, and its appeal is easy to understand: it brings recipes from favorite blogs into one place instead of making me jump between separate sites. That sounds simple, but it addresses a very familiar cooking problem. I may remember a recipe from a blog, lose it among browser tabs, and then struggle to find it again when I am already standing in the kitchen.
The app is developed by Chewed Carrot and is free to install. Its store summary describes a collection of recipes from favorite blogs, while the short description is simply “מתכונית.” The app is aimed at Everyone, runs on devices using iOS 11 or later, and the current version is 1.9.4. It has passed the early discovery stage with over 10 thousand installs, which gives it the feel of a focused, established niche tool rather than a large general-purpose cooking platform.
How the app fits into everyday cooking
My first impression is that מתכונית is less about teaching cooking from scratch and more about organizing recipe discovery. It is useful when the source matters to me: perhaps I follow several food bloggers, prefer their writing style, or trust their approach to home cooking. Instead of treating every recipe as an isolated web page, the app gives that scattered reading habit a more central place.
That distinction matters when comparing it with the usual alternatives. A normal browser is more flexible and can reach any recipe site, but it also leaves me with open tabs, repeated searches, and pages designed around advertising or unrelated content. A general recipe app may offer a larger, more uniform database, but its recipes can feel detached from the bloggers I actually enjoy reading. מתכונית sits between those choices: it is more focused than a browser and potentially more personal than a broad recipe catalog.
I would not describe it as a replacement for every cooking resource. Someone looking for highly structured nutrition filters, detailed meal planning, shopping-list automation, or a huge international database may prefer a larger recipe service. The value here is narrower and more practical: bringing blog-based recipes together so that the discovery process feels less scattered.
What I would use it for first
My most realistic use case is weekday planning. On a quiet evening, I can browse for ideas without deciding immediately what to cook. Then, when I have a free half hour the next day, I already have a starting point instead of searching from zero. This is especially useful for people who cook by mood but still want a reliable place to return to.
Another useful situation is ingredient-led cooking. If I have vegetables, grains, or a particular cut of meat that needs using, a blog-centered collection can help me find inspiration without opening several unrelated search results. The app becomes a starting shelf of ideas rather than just a one-time recipe viewer.
There is also a difference between saving a recipe because it looks attractive and saving it because I could realistically make it. I found the app most helpful when I treated browsing as a short selection process: choose a few recipes that match the time and ingredients available, then keep the most practical one in view. That approach reduces the common problem of collecting endless recipes that never reach the kitchen.
Cost and what “free” means here
The app itself is free, so trying it does not require an upfront purchase. That makes the decision straightforward for a curious cook: install it, explore its recipe approach, and see whether the collection matches your tastes before spending anything.
There are in-app purchases ranging from $0.49 to $5.99 per item. I would therefore separate the free access from any optional paid value rather than assuming that every part of the experience costs money or that every feature is included without charge. The practical question is whether the free portion already solves your main problem—finding and revisiting blog recipes. If it does, paid items become an optional enhancement rather than a requirement for basic experimentation.
For me, that pricing structure makes the app easier to recommend to occasional cooks than to someone who wants to commit immediately to a full cooking subscription. A free starting point lowers the risk, while the small-to-moderate purchase range leaves room for users to decide whether extra value is worth paying for on an individual basis.
I would still approach purchases deliberately. Before paying for anything, I would use the free experience long enough to understand how often I return to the app and whether it changes what I cook. A recipe organizer only earns its keep when it becomes part of a real routine; a purchase is less convincing if I merely enjoy browsing but never use the recipes.
Where the experience saves time
The strongest time-saving idea is centralization. When recipes come from multiple blogs, the normal workflow can involve remembering a site name, searching through a blog, opening the correct post, and navigating around the page until the actual instructions appear. A dedicated app can make that journey feel more intentional and reduce the mental overhead around discovery.
There is a second, less obvious benefit: it can help me separate recipe discovery from recipe execution. I can browse when I am relaxed and cook later, rather than trying to search while handling ingredients. That small separation is valuable for anyone who finds kitchen multitasking frustrating.
For a busy household, I would use it as a shared idea bank rather than as a formal meal planner. One person could browse and suggest a dish, while the actual shopping decisions remain based on the recipe and what is already at home. This keeps expectations realistic: the app can support planning, but I would not treat it as a complete household logistics system.
The tradeoffs I noticed
The blog-based focus is also the main limitation. A blog recipe can be engaging and personal, but it may not be presented in the standardized format found in specialist cooking databases. Instructions, ingredient measurements, preparation times, and serving information may vary in how they are written. That means I still need to read carefully instead of assuming that every recipe follows the same structure.
This matters most when I am in a hurry. A highly standardized recipe app may be better when I want to scan ingredients quickly, apply dietary filters, or compare several versions of the same dish. מתכונית is more attractive when I value the source and the variety of blog voices, not when I need every recipe reduced to identical fields.
Another tradeoff is dependence on the quality of the underlying recipe collection. A central place is only useful if the blogs represented there match my interests. If my favorite cooking styles are not well represented, the app may feel less relevant than a browser search aimed directly at those creators. I would judge it by the usefulness of the recipes I actually encounter, not merely by the promise of collecting many sources.
I also would not use it as my only reference for specialist cooking needs. If I need strict allergen control, medically precise dietary management, or carefully calculated nutrition, I would verify everything independently and probably choose a service designed around those requirements. A blog recipe collection can inspire meals, but inspiration is not the same as clinical or technical guidance.
Three practical ways to get more from it
I would browse before shopping, not after arriving at the supermarket. Choosing recipes first gives me a better chance of building a coherent ingredient list instead of buying attractive items without a plan.
I would keep a short personal shortlist of recipes that fit my actual week. The useful collection is not the largest one; it is the group of dishes I can make with my available time, equipment, and confidence.
I would read the complete recipe before starting. Blog-style instructions can include important context in the surrounding text, and a quick scan helps reveal preparation steps that are easy to overlook when I begin cooking immediately.
These habits also clarify whether the app is genuinely helping. If it leads me from browsing to a practical meal, it is doing its job. If I only scroll through appealing dishes and then return to a browser for every decision, its role may be less valuable for me.
Who is most likely to enjoy it?
I think מתכונית is a good fit for home cooks who already follow food blogs or want blog-style inspiration without managing many separate websites. It should also suit people who dislike rigid meal plans but still want a reliable place to discover dishes. The free entry point makes it approachable for students, occasional cooks, and anyone testing whether a recipe app belongs in their routine.
It may be particularly useful for cooks who enjoy the personality behind a recipe. Blog writing often gives more context than a bare ingredient list: why a dish works, what occasion inspired it, or how the author approaches substitutions. If that human element motivates me to cook, a blog-centered app can feel more inviting than a purely database-driven alternative.
I would recommend looking elsewhere if my priority is precision filtering. People managing several allergies, following a strict calorie target, or organizing a large family menu may need tools built specifically for those tasks. Likewise, someone who wants video-led instruction, automatic pantry tracking, or a complete shopping workflow should compare it with a more feature-heavy cooking platform before settling here.
The app is also not the obvious choice for a person who rarely tries new recipes. If I already have a small set of dependable meals and never browse for ideas, a dedicated collection may add little. Its value grows with curiosity and repetition: the more I discover, revisit, and cook from it, the more useful the centralization becomes.
Device expectations and long-term value
Support for iOS 11 or later means the app is intended for a range of devices that are not necessarily the newest. That is helpful for people who keep an older phone or tablet in the kitchen. I would still make sure my device is updated enough for the app before planning to rely on it during cooking.
The current version is 1.9.4, so I would install the latest available release rather than judging the experience from an old copy. Updates matter more in a recipe app than they might seem: browsing, text display, and returning to a recipe all need to remain dependable when my hands are busy and my attention is divided.
Long-term value comes from repeated usefulness, not from the number of recipes I can browse in one sitting. I would give it a fair trial across several cooking occasions: one quick weekday meal, one slower weekend dish, and one situation where I need to use ingredients already at home. That test reveals more than a short browsing session because it shows whether the app fits different kinds of cooking.
My buy-or-skip verdict
I would try מתכונית if I wanted a free, focused way to bring recipes from food blogs into one cooking-oriented place. Its strongest argument is convenience without forcing me into a large, formal meal-planning system. The app is specific enough to feel purposeful, yet the free starting point makes experimentation easy.
I would not pay for optional items immediately. I would first confirm that the available recipe experience fits my tastes and that I return to it when planning meals. Because purchases range from $0.49 to $5.99 per item, the sensible approach is to connect any spending to a clear personal benefit rather than treating payment as part of the basic requirement.
My final view is positive but targeted. This is not the universal answer for nutrition management, advanced planning, or perfectly standardized instructions. It is better understood as a practical bridge between favorite food blogs and everyday home cooking. If your real problem is scattered recipe discovery, the app is worth trying; if your problem is detailed meal administration, another tool will probably serve you better.
For the right reader, that is enough of a reason to install it. I would recommend it to a friend who enjoys discovering recipes online but wants less searching and fewer disconnected tabs. I would suggest skipping it only when the blog-centered approach does not match the way that person cooks, or when specialized planning and dietary controls matter more than browsing and inspiration.
