VersionshinweiseWas ist neu in ¡Qué rico!Jede Version der App, die neueste zuerst — was sich auf iOS, Android und im Web geändert hat. Der Text einer Version ist derselbe, der in die Store-Versionshinweise kommt.
Als NächstesProbier aus, woran wir arbeitenEine klickbare Vorschau der App mit Ansichten und Ideen, die noch nicht veröffentlicht sind. Sie läuft mit Beispielrezepten: Nichts, was du dort tust, wird gespeichert oder landet in deinem Konto.
Vorschau öffnen
Öffnet eine neue Seite auf claude.ai. Was die Vorschau zeigt, kann sich noch ändern oder nie erscheinen.
1.28.2
Update ohne Store
15. November 2026
A screen, translations and the version only.Behoben
Editors now see the ingredient names of every handed-in recipe. A recipe handed in through an AI assistant showed only amounts ("— 150 g") in the review, because such a draft stores its ingredients by catalogue id. The review now looks the names up, in the language the recipe is written in.
1.28.1
Update ohne Store
15. November 2026
Pipeline and the version only; the app itself is unchanged.Geändert
The build pipeline no longer uploads a 310 MB package cache that was never reused, and its small jobs run on separate machines so they stop waiting behind the builds. Nothing you can see.
1.28.0
Update ohne Store
15. November 2026
Texts, translations, four icons and the version only.Geändert
The landing page says what ¡Qué rico! is now: a free cookbook that works out the nutrition of every recipe from official European food data. It no longer speaks of dietologists who write the recipes or sell diet plans.
We are not building a calorie tracker. The landing page and the mission board on "About us" say so, and what comes instead: sending the nutrition of a meal you cooked to Apple Health or Google Health Connect.
The mission board on "About us" has a new order of what comes next: cooking with your AI assistant, the connection to health apps, restaurants with their nutrition, cooking with friends, and, later and only if it proves useful, nutritionists and supermarket ordering. The food diary and the nutrition chat are no longer planned.
1.27.0
Update ohne Store
15. November 2026
A screen, translations and the version only.Neu
A look ahead on the "What's new" page. Above the release notes, a card opens a clickable preview of where the app is heading, including screens that are not released yet. It runs on sample recipes, so nothing you do there is saved or reaches your account.
1.26.1
Update ohne Store
15. November 2026
Text, translations and the version only.Geändert
Privacy notice: a new section, "Sending a shopping list to other apps". It says what "Add to Bring!" sends (the recipe's web address and the servings, only on your tap, no account data) and that a list added to Apple Reminders stays on your device.
Entfernt
Code and translations nothing used any more after the recipe wizard and the approval process were reworked. Nothing you can see changes.
1.26.0
Update ohne Store
15. November 2026
Screens, translations and the version only. Reminders uses the access the app already asks for, Bring! is reached over the network and through a link, and the chosen list is remembered with the storage the app already has: no new native module, no new permission.Neu
Add the shopping list to Bring! (iOS, Android, Web). "Add to Bring!" on the Shopping list tab opens Bring! with the recipe's ingredients for the servings you chose; you pick the list there, shared lists included. Bring! reads the recipe's public page, so it takes the whole recipe as its author wrote it: what you ticked as "at home" is still on it, and an adapted version is not. Only the recipe's address and the two servings numbers are sent, and only when you tap.
Choose the Reminders list (iOS). The first time, you choose one of your Reminders lists or a new list named after the recipe; a shared list stays shared, and the others see the new items. "Use this list next time without asking" remembers the choice on this device, and "Change" picks another one.
Share the list from the browser (Web). Where the browser has a share menu, "Share…" hands it the list.
Geändert
Nothing is added twice (iOS). Before adding, the app looks at the open reminders of the list and leaves out every ingredient that is already there. It tells you how many were added and which were already there. Afterwards the button names the list ("On Groceries") until you change the servings, the version, a tick or the list, and you can open Reminders or add to another list.
Reminders name the recipe (iOS). Each reminder carries the amount and the recipe's name as its second line, for example "300 g · Adas Polo".
Plain text for other list apps. "Share…" on Android, "Share as text" on iOS and "Copy list" on the web now give one ingredient per line, such as "300 g Basmati rice", without checkbox signs, heading or link, so an app that turns lines into items gets ingredients only. A label says that only the items still to buy are in it. The e-mail keeps the heading and the link to the recipe.
1.25.0
Update ohne Store
15. November 2026
Goes with backend 0.10.0 (reports and takedowns of published recipes). Merge and promote the backend first: the report dialog, the editors' second list and the "Taken down" section call routes that exist from 0.10.0 on.Neu
Report a recipe in the app. Signed in, the flag on a recipe opens a short dialog instead of an e-mail: choose what is wrong, add one sentence if you like, send. You get a thank-you; what the editors decide is not reported back. At most 10 reports a day. Signed out, the flag still opens an e-mail.
Taken-down recipes in My Area. A recipe of yours that was taken down is listed with the reason, the editors' note if there is one, and whether the automatic check or an editor decided. It is no longer visible to others and is deleted after 30 days. After an automatic decision you can ask an editor to look again, once.
Editors: published recipes that need a decision. The Review section lists reported recipes (still public) with their reports and what the automatic check found, to keep or to take down with a reason; and recipes the automatic check took down whose author asks for a second look, to restore or to uphold. The count on the Editor tab includes them.
Geändert
A new photo for a published recipe can be refused. While recipes are published by approval the photo is checked before it replaces the old one. If it is not accepted the app says why, or that it could not be checked right now; the old photo stays.
1.24.0
Update ohne Store
15. November 2026
Goes with backend 0.9.0 (the automatic check). Nothing in the app changes until the backend's check is switched on. Merge together with switching the check on, not before: the privacy notice below describes processing that must be happening when it is published.Neu
Privacy notice: "Automatic Check of Recipes". What is checked and why; that the photo and the text of a handed-in recipe are sent to Mistral AI (France) for this check and for nothing else; that no name, e-mail address or account data is sent and nothing is used to train AI; that private drafts are never sent; that a person decides whenever the check is not sure and can be asked to look again. Mistral AI is listed among the processors. In English, German and Spanish.
Ask an editor to look again. A recipe that the automatic check did not accept says so ("Checked automatically") and offers one request for a person to look at it, unchanged.
Editors see what the automatic check left on each waiting recipe: still running, not sure, found a problem (with the rule and its sentence), did not work, not checked because the limit was reached, or a second look requested.
1.23.0
Update ohne Store
15. November 2026
Nothing changes for anyone until the backend switch is turned on (reviewRequired in GET /v1/app/policy, backend 0.8.0). With the switch off the app publishes as before.Neu
Hand in for review. While recipes are published by approval, the last step of the recipe wizard says "Hand in for review" and explains what happens: an editor looks at the photo and the text before the recipe appears in the cookbook. The same checks as before hold the button back until the recipe is complete and in your profile language.
My Area shows where a recipe stands. A handed-in recipe carries "In review" and can be taken back to change it. One that was sent back carries "Needs changes" with the reason in your language and the editor's sentence, and opens in the wizard as usual.
Editors: a Review section in the editor workspace, in front of the catalogues. It lists the handed-in recipes, the one waiting longest first, and opens on them while any is waiting; the Editor tab and link show how many. The review screen shows the photo and the recipe as its author wrote it, and offers "Approve and publish" and "Send back" with a reason and a sentence.
Every refusal of the approval process has its own sentence in English, German and Spanish.
Behoben
One text in another language no longer slips through. A recipe whose description was in the profile language but with a single instruction in another language showed no warning and could be sent. Now every text of 30 characters or more must read as the profile language: the warning stays, and the button stays held back, until the last such text is changed. The recipe name is still free.
The wizard's button looks held back when it is. It ignored presses but kept its full colour, so it read as available.
Geändert
A handed-in recipe opened by its link shows that it is in review and offers to take it back, instead of a wizard whose saves the server would refuse.
1.22.0
Store-Release
14. November 2026
Neu
A draft opens where it still needs you. A draft that is complete except for its photo opens on the photo step; one that is complete opens on the review.
Jump between steps. The progress bars at the top of the recipe wizard are buttons, and a skip-ahead button takes you past the steps that are already filled. A step can be opened as soon as every step before it has its required values; a value that is filled in but flagged, or the language warning, does not hold you back.
Web: drop a picture onto the photo step, or paste one.
The progress bars show what is filled. A step that has everything it needs stays marked as filled when you jump back to an earlier one; before, only the steps left of the current one were marked. A step with a warning is amber, and the current step is the thick bar.
Closing the wizard with unsaved changes asks before it discards them.
A recipe that cannot be published is not offered for publishing. The publish button on the review, and on a draft card in My Area, waits until every step has what it needs, the server's check lists no problems and the text is in your profile language. The review says in one line what is still in the way and takes you to the step.
Errors in plain words. A refused or failed publish no longer shows the server's technical text as the message: it says whether the connection failed, something went wrong on our side, the photo is too large, or the recipe was not accepted.
Ingredients on one line each. An ingredient is now a single line with its amount, unit and name, so a whole recipe fits on the screen. Tap a line to open its kind, note, alternatives and the other details; one line is open at a time. Every line keeps its handle for changing the order.
Times are typed. Preparation and cooking time take the minutes directly, with the usual values one tap away. A recipe needs one of the two, not both: together they must be more than 0 minutes, and the message now says so.
Behoben
The wizard no longer rejects a step text that names two ingredients of the same food (Skyr and cream cheese, or paprika and cayenne). Drafts written through the AI connector were stopped by this although the server had accepted them.
"Add another recipe" after publishing showed an empty screen.
The amount of an alternative ingredient lost a decimal point while it was being typed.
Publishing a draft from its card in My Area now says why the server refused it (the language, an ingredient, a step that does not account for everything) instead of only "try again".
After a publish that the server refused, going back to fix something and returning to the review showed the same error again instead of the recipe and its checklist.
The language check now speaks up on the first step: a description of 30 characters or more in another language than your profile's shows the warning right away. It used to wait until a second text (an ingredient note, an instruction) was written in that language too.
Geändert
The app is built with the React Compiler, which keeps a screen from redrawing parts that did not change. Nothing looks different; typing and scrolling should feel lighter everywhere.
Typing in the wizard is lighter: the checks that read the whole recipe no longer run on every keystroke, an ingredient row redraws only when it changes, and search thumbnails load a small picture instead of the full photo.
1.21.6
Update ohne Store
14. November 2026
Geändert
Web, for search engines: the About page, the recipe list, the privacy notice, the imprint and the changelog each have their own description in English, German and Spanish — the text a search result shows under the link. Until now the About page and the recipe list repeated the home page's description and the other three had none. Nothing changes in the native apps.
1.21.5
Store-Release
14. November 2026
Geändert
Expo SDK 58 patch level: expo 58.0.25 (was 58.0.23) with the matching module patches, and react-native-auth0 6.2.1, lucide-react-native 1.73.0 and postcss 8.5.33. Nothing visible changes in the app.
Security
Expo's command-line tools no longer use glob; the package with the open advisory is now only part of the test tooling, not of what ships. The advisory itself stays open until Jest moves on.
1.21.4
Update ohne Store
13. November 2026
Geändert
Documents and comments name the compose files by their new names, compose.<env>.yml (que-rico 0.7.0). Nothing changes in the app.
1.21.3
Update ohne Store
11. November 2026
Geändert
Build pipeline only: a newer SonarQube scan action (8.4.1). Nothing changes in the app.
1.21.2
Update ohne Store
11. November 2026
Geändert
Internal, nothing visible changes: the colour rules for an explicit light or dark choice on the web moved out of the shared stylesheet into a web-only one. Native never used them, and the next version of the styling library refuses to compile them for native. The colours are identical; the native fingerprint is unchanged (measured for iOS and Android). (Web; iOS and Android unaffected)
1.21.1
Store-Release
10. November 2026
Behoben
The iOS build of 1.21.0 failed before compiling: since Expo SDK 58 the build tooling and the project disagree on how an accented app name becomes the Xcode target name ("Qurico" vs "Querico"), and the build signed a target that does not exist. The projects are now named without the accent; the name under the icon stays "¡Qué rico!". Nothing visible changes. (iOS; the Android project name changes with it)
1.21.0
Store-Release
10. November 2026
Behoben
The app starts on iOS 27 again. Builds made with the iOS 27 SDK closed immediately at launch, because iOS 27 requires an app life cycle the previous Expo SDK did not provide. (iOS)
Geändert
Internal: the app moves to Expo SDK 58 — React Native 0.88, React 19.3 and every native module of that set — and to version 6 of the sign-in library. Nothing visible is meant to change. (iOS, Android, Web)
Android 8.0 is now the oldest supported Android version (was 7.0): the new sign-in library requires it. Devices on Android 7 keep the version they have. (Android)
Android release builds are now minified by default. (Android)
Dependency refresh closes known security advisories in the build and server tooling (node-forge, body-parser, qs, zod). (Web, build pipeline)
1.20.3
Update ohne Store
10. November 2026
Geändert
Dependency refresh (Dependabot): @tanstack/react-query 5.105.1, i18next 26.7.1, react-i18next 17.1.11, lucide-react-native 1.66.0, postcss 8.5.32 and a newer SonarQube scan action in the build pipeline — JavaScript packages only, the native fingerprint is unchanged (measured for iOS and Android). Nothing visible changes. (iOS, Android, Web)
1.20.2
Update ohne Store
9. November 2026
Geändert
Documentation only: the FoodEx2 catalogue, ingredient substitution and fingerprint plans are archived with a note on what shipped; CLAUDE.md points at the one remaining plan and at the cross-repo follow-ups list. Nothing changes in the app.
1.20.1
Update ohne Store
2. November 2026
Behoben
The release tag job on the self-hosted runner, which has no gh CLI: the GitHub release and its tag are created through the REST API. The previous version got no tag and no image because of it.
1.20.0
Update ohne Store
2. November 2026
Neu
The shopping list in the share sheet is a checklist: tick what you already have at home and it stays off the shared list — and off the Reminders list.
Geändert
On iOS the shopping list's share button adds the list to Reminders: a list named after the recipe, each ingredient a reminder with its quantity as the detail line and the recipe link. Sharing the list as text moved to the quiet line beneath the button. (iOS)
Behoben
The language pill in the footer centres its codes. (Web)
1.19.4
Update ohne Store
2. November 2026
Geändert
Every workflow runs on the self-hosted que-rico-runners (the release tag, the pull-request conventions, the issue-to-project step); the staging deploy keeps the Mac mini's macOS runner for the local native builds. Nothing changes in the app.
1.19.3
Update ohne Store
2. November 2026
Geändert
Workflow actions refreshed (Dependabot): add-to-project 2.0.0, expo-github-action 9.0.1, setup-java 6, docker/login-action 4.7.0. Nothing changes in the app.
1.19.2
Update ohne Store
2. November 2026
Geändert
The web image builds on Node 24.22.1 (Dependabot). (Web)
1.19.1
Update ohne Store
2. November 2026
Geändert
Dependency refresh (Dependabot): @tanstack/react-query 5.104.4, i18next 26.5.2, react-i18next 17.1.0, lucide-react-native 1.59.0, react-native-auth0 5.11.2, ts-pattern 5.9.2, postcss 8.5.31 — JavaScript packages only, the native fingerprint is unchanged.
1.19.0
Store-Release
1. November 2026
Neu
A shared recipe link (que-rico.net/…/recipes/…) opens the app when it is installed — the website otherwise. (iOS, Android)
The share sheet's "Image" format: save the recipe card to Photos or the gallery, and on iOS hand it to the share sheet. (iOS, Android)
The share sheet's "Shopping list" format adds the list to Reminders: a list named after the recipe, one reminder per ingredient, the recipe link on each. (iOS)
Geändert
Recipe photos load through a disk cache with a short fade-in and no longer fetch the full-size master for a tile. (iOS, Android)
The language links in the footer are a quiet outlined pill with a globe (EN · DE · ES, the current one lit). (Web)
1.18.0
Update ohne Store
1. November 2026
Neu
Share a recipe as an image: the share dialog's new "Image" format shows a 4:5 card — photo, name, time, calories and rating — to download or copy for stories and chats. (Web; the app's share sheet gets it with the next store release, which adds saving to Photos.)
1.17.0
Update ohne Store
1. November 2026
Neu
Every page of the cookbook has its own address (?page=2) and the arrows are real links, so a page can be shared and search engines reach every recipe from the cookbook. (Web)
1.16.1
Update ohne Store
1. November 2026
Behoben
Links shared from the recipe page point at the recipe in your language again (/de/recipes/…); since 1.15.0 they opened the "not found" page. (iOS, Android, Web)
1.16.0
Update ohne Store
1. November 2026
Neu
The start page shows 16 featured recipes — the best-rated ones with enough votes, filled up with our dietologists' picks — and a link to the whole cookbook. (Web)
"More like this" at the end of every recipe: four related recipes, same cuisine and course first. (iOS, Android, Web)
Link previews for every public page (a default image where the page has none), the recipe's rating in its structured data, a breadcrumb trail on recipe pages and an item list on the cookbook, for search engines and chat previews. (Web)
1.15.1
Update ohne Store
1. November 2026
Behoben
The start page's redirect to your language is cacheable per language, so the edge cache replaces the page it held under / before 1.15.0 instead of serving it stale forever. (Web)
1.15.0
Update ohne Store
1. November 2026
Geändert
Every public web page now carries its language in the address: /en/…, /de/…, /es/… for the landing page, the cookbook, recipes, about, imprint, privacy, the changelog and the integration guides. The old addresses without a language answer "not found"; the start page sends you to your language. Each page links its two other languages in the footer, and search engines see every language version. (Web)
Links shared from the app open the recipe in the language it was shared in. (iOS, Android)
1.14.7
Update ohne Store
28. Oktober 2026
Geändert
CI runs on the ARC runner on the Mac mini (que-rico-runners) again instead of the Raspberry Pi runners, which were too slow: checks, the web image build, the promotion, the EAS deployment and the EAS environment push, with their earlier time limits and four Jest workers. Nothing changes in the app. (iOS, Android, Web)
The Sonar analysis in CI goes to the local SonarQube on the Mac mini instead of SonarCloud, for pull requests and for main. The quality gate still fails the job; the result appears in the job summary and as one comment on the pull request that later pushes update. (iOS, Android, Web)
1.14.6
Update ohne Store
27. Oktober 2026
Geändert
CI runs on the organisation's six Raspberry Pi runners (que-rico-pi-runners) instead of the ARC runner on the Mac mini: checks, the web image build, the promotion, the EAS deployment and the EAS environment push. Nothing changes in the app. (iOS, Android, Web)
1.14.5
Update ohne Store
28. Oktober 2026
Behoben
The "Development process" link on the new-issue page and in the feature form points at the note's new location in the vault (process/development-process.md).
1.14.4
Update ohne Store
26. Oktober 2026
Geändert
Repository housekeeping: GitHub issue forms for features and user stories, and new issues land on the organisation project automatically. Nothing changes in the app. (iOS, Android, Web)
1.14.3
Update ohne Store
19. Oktober 2026
Geändert
Pages now carry real headings for search engines and screen readers: the recipe name, the recipe sections, the landing page titles and the cookbook. Nothing looks different. (iOS, Android, Web)
1.14.2
Update ohne Store
18. Oktober 2026
Behoben
The share and filter sheets now dim the page behind them on the phone, like the ingredient details. (iOS, Android)
Geändert
The ingredient details show how much of the ingredient this recipe uses, and the substitutes section is called "Alternatives". (iOS, Android, Web)
1.14.1
Update ohne Store
18. Oktober 2026
Behoben
"For me" in "Adapt this recipe" now starts sign-in when you are not signed in, instead of doing nothing. (iOS, Android, Web)
1.14.0
Update ohne Store
18. Oktober 2026
Neu
On the website, the address of a recipe now follows the servings and the vegan, vegetarian or pescetarian version you choose, so copying the address or reloading the page keeps them. The browser's Back button still leaves the recipe in one step. (Web)
Geändert
Shared links on the website point at the site you are on. (Web)
The ingredient details show the name above the photo, next to the close button. (iOS, Android, Web)
1.13.2
Update ohne Store
18. Oktober 2026
Behoben
The ingredient details now dim the recipe behind them, and the close button in the top-right corner is easier to hit. On the phone you can also swipe the sheet down by its handle to close it. (iOS, Android, Web)
1.13.1
Update ohne Store
17. Oktober 2026
Behoben
A recipe link with extra parameters, such as a shared link with servings or a campaign link, now arrives as a complete page instead of a loading placeholder, so search engines and link previews see the recipe. (Web)
1.13.0
Update ohne Store
17. Oktober 2026
Neu
Share a recipe from the new share button on the recipe photo. Send the link, or a shopping list as plain text that pastes into notes or a chat. On the phone it opens the system share menu; on the website you can copy the link or list, send it by WhatsApp or email, or print the page. (iOS, Android, Web)
When you have scaled the servings or switched to a vegan, vegetarian or pescetarian version, you can share it that way: the link opens the recipe at your servings and in that version, marked as adapted. (iOS, Android, Web)
Behoben
The rating line under the recipe name no longer disappears while a recipe is shown in an adapted version. (iOS, Android, Web)
1.12.0
Update ohne Store
17. Oktober 2026
Geändert
Recipe photos on the website load at the size the screen needs instead of the full original: smaller files for the cookbook tiles, a sharp large photo on the recipe page. Each photo stays behind a soft placeholder until it has fully loaded, then fades in, instead of drawing line by line. (Web)
Recipe photos are now part of the page itself, so search engines can find them, and the recipe page photo starts loading before the page becomes interactive. Link previews use a 1200 px photo. (Web)
1.11.1
Update ohne Store
17. Oktober 2026
Behoben
"Top rated" in the cookbook sort now actually sorts by rating; the choice was selected in the filters but never sent, so the list kept its default order. (iOS, Android, Web)
1.11.0
Update ohne Store
17. Oktober 2026
Neu
Rate recipes you have cooked: "I cooked this" on the recipe page unlocks one to five stars, which you can change or remove at any time. Your own recipes can be marked as cooked but not rated. Ratings only come from people who cooked the recipe.
Recipe pages show how often a recipe was cooked and its average rating; recipe tiles show the rating once a recipe has votes.
"Top rated" sort in the cookbook filters: vote count and average together, so one 5-star vote never beats many good ones.
1.10.19
Store-Release
17. Oktober 2026
Geändert
Internal only, nothing visible changes: dependency updates — sign-in library, Expo SDK 57 patch releases, data fetching, translations, icons and the build and test tooling — plus a newer Node.js base image for the web server and newer build-pipeline actions. Closes known security advisories in the build and test tooling. (iOS, Android, Web)
Internal only: dependency update proposals now arrive once a week (Monday 02:00) instead of daily. (iOS, Android, Web)
1.10.18
Update ohne Store
17. Oktober 2026
Geändert
Internal only, nothing visible changes: outdated dependencies are now proposed daily (03:00) as update pull requests, leaving out the packages pinned by the Expo SDK. (iOS, Android, Web)
1.10.17
Update ohne Store
17. Oktober 2026
Geändert
Internal only, nothing visible changes: the code-quality analysis no longer counts generated and tooling files (the bundled gluestack config in .gluestack/, .claude/, .agents/), which only used up the analysed-lines allowance. (iOS, Android, Web)
1.10.16
Update ohne Store
17. Oktober 2026
Geändert
Whether a recipe is yours is now decided by your public user id, the same id the recipe names as its author — no longer by the sign-in provider's identifier, which the backend stops publishing with its next release (public-author fix, que-rico plan 2026-10-17_seo-preparation.md §1.1). Edit and delete on your own recipes keep working across that release; nothing visible changes. (iOS, Android, Web)
1.10.15
Update ohne Store
16. Oktober 2026
Behoben
The native build environment (env/*.env) now actually reaches EAS: the workflow that pushes it had never succeeded because it ran the EAS CLI without installed dependencies, so the staging Play link added in 1.10.14 never arrived in the staging app. It installs them first now and uses the pinned CLI instead of downloading a new one per run. No visible change beyond the staging Play badge working once the environment is pushed. (iOS, Android)
1.10.14
Update ohne Store
16. Oktober 2026
Geändert
Staging: the Play badge links to the staging app's internal-testing opt-in page instead of reading "coming soon". Production is unchanged. (Web, Android)
1.10.13
Update ohne Store
16. Oktober 2026
Behoben
Staging builds on the Mac mini run Gradle without a daemon and clean up after themselves even when a build fails or is stopped, so nothing lingers on the runner. No visible change. (iOS, Android)
1.10.12
Update ohne Store
16. Oktober 2026
Behoben
Staging rollout on the Mac mini: a running deploy is no longer cancelled by the next merge (later ones queue instead), and stale Gradle and Kotlin daemons are stopped before a build — a build cancelled halfway had left the runner unable to start any job. No visible change. (iOS, Android)
1.10.11
Update ohne Store
16. Oktober 2026
Geändert
iOS, Android: the installed version is shown under the About links on the profile screen also when signed out, and on every signed-out view that carries those links. It used to appear only for a signed-in profile.
1.10.10
Update ohne Store
16. Oktober 2026
Neu
iOS, Android: when an update has downloaded in the background, a small banner at the top says which version is ready and offers "Restart", which applies it at once. Before, the new version only showed up on the second launch, which looked like the app being stuck on the old one. "Later" hides the banner for this launch; the update applies on the next one anyway.
1.10.9
Update ohne Store
15. Oktober 2026
Behoben
Staging builds on the Mac mini: Gradle gets enough Metaspace (the first Android build ran out, the compile died and the build hung), and leftovers of a cancelled build are removed before the next one so the small disk stays usable. No visible change. (Android)
1.10.8
Update ohne Store
15. Oktober 2026
Geändert
The staging rollout's GitHub run page records version, build number and fingerprint per platform, names the kept binaries with the version and annotates the fingerprint tags — the Expo dashboard shows no version for a submission of a locally built file. No visible change. (iOS, Android)
1.10.7
Update ohne Store
15. Oktober 2026
Geändert
Staging builds are made on the Mac mini (eas build --local, both platforms) and submitted through EAS to TestFlight and the Play internal track, instead of in the EAS cloud; they no longer appear under Builds on expo.dev and cost no build quota. Production builds stay in the EAS cloud. No visible change. (iOS, Android)
1.10.6
Update ohne Store
15. Oktober 2026
Geändert
The GitHub-side rollout runs on the organisation's regular runners instead of a dedicated Mac: it only decides and starts EAS builds and updates, nothing is compiled on it. No visible change. (iOS, Android)
1.10.5
Update ohne Store
15. Oktober 2026
Behoben
The GitHub-side rollout installs the EAS CLI with npm; its first run on the Mac mini stopped looking for yarn. No visible change. (iOS, Android)
1.10.4
Update ohne Store
15. Oktober 2026
Geändert
The native rollout is orchestrated by GitHub Actions on the Mac mini instead of EAS Workflows, whose minutes ran out: a merge into main still reaches the staging app, a push to release still reaches the stores, as an over-the-air update or a build plus submission. Builds, submissions and updates run on EAS as before. No visible change. (iOS, Android)
1.10.3
Update ohne Store
15. Oktober 2026
Behoben
iOS, Android: "Clear search" in the no-results state now also empties the search field in the header. It reloaded the recipes but left the typed text in the field.
Web on phones: more room between the navigation row and the opened search field. (Web)
1.10.2
Update ohne Store
15. Oktober 2026
Behoben
Web on iPhone: opening the search no longer zooms the page in. Safari zooms into any text field whose font is smaller than 16 px; text fields on phones now use 16 px on the web (tablets and desktops keep their size, native is unchanged). (Web)
Cookbook and My Recipes: moving to another page of results starts that page at the top instead of where the previous page was scrolled to. (iOS, Android, Web)
1.10.1
Update ohne Store
15. Oktober 2026
Behoben
Web on phones: the header's navigation (Cookbook, My Area, Editor) has its own row under the logo and the icons, with equal widths and the underline centred, so no label breaks into two lines; on tablets and desktops the layout is unchanged. The footer stacks and centres its copyright line and links on phones instead of wrapping them unevenly. (Web)
1.10.0
Store-Release
15. Oktober 2026
Neu
Web: the store badges on the landing page link to the app of the environment: on production the App Store and Google Play listings as before, on staging the staging app's TestFlight page (and the Play internal-testing link once it is configured; until then the Play badge reads "coming soon"). (Web)
Geändert
The native build environment is versioned in the repository (env/local.env, env/staging.env, env/production.env) and pushed to EAS; builds, fingerprints and updates read it there. No visible change. (iOS, Android)
1.9.2
Store-Release
15. Oktober 2026
Geändert
iOS: the export-compliance answer ("uses only exempt encryption", standard HTTPS) is part of the build. App Store Connect no longer asks it for every TestFlight and store upload; a build is available for testing or review the moment it is processed. No visible change. (iOS)
1.9.1
Store-Release
15. Oktober 2026
Geändert
Expo SDK 57 patch updates as npx expo doctor recommends them; no visible change. (iOS, Android, Web)
1.9.0
Update ohne Store
15. Oktober 2026
Neu
"What's new": every version of the app with its release notes, newest first, rendered from this changelog. Linked from About us (under the shipped milestones), from the footer on the web, and from the About section of the profile on iOS and Android, also when signed out. Each version has a copy button that gives the store-ready text — the same text that goes into App Store Connect and the Play Console. (iOS, Android, Web)
Behoben
iOS, Android: the filter button in the cookbook stayed in place while typing a search, but jumped to the top of the screen the moment the search had no results, and back with the next keystroke. The no-results state now renders inside the same list as the results.
1.8.0
Store-Release
14. Oktober 2026
Neu
A staging app next to the store app, from the same code (iOS, Android): "¡Qué rico! Staging", net.que-rico.app.staging / net.querico.app.staging, built against the staging host and the staging Auth0 tenant. Every merge into main reaches it through TestFlight internal testing and the Play internal track when native code changed, and as an over-the-air update on the preview channel otherwise (.eas/workflows/deploy-staging.yml, replacing the preview-channel update). Store users are untouched. One-time store registration: docs/staging-app-runbook.md.
Geändert
Local prebuilds and the EAS development profile produce the staging app, so a development install no longer shares the store app's identity. The Universal Links entry for the Auth0 callback follows the tenant the build authenticates against (it was fixed to production, which left builds against the staging tenant unable to verify their callback on iOS).
1.7.0
Store-Release
14. Oktober 2026
Rolled out together with backend 0.5.0 and MCP server 1.1.1; the backend is promoted first.Geändert
Every ingredient and every tool a recipe lists must be placed in one of its steps, and the steps may only mark things the recipe lists. The wizard already placed chips and warned; it now stops before "Next" and before publishing until the lists and the steps agree, and the review step says so. A recipe without any placed chips used to publish regardless — the backend now rejects it the same way, naming what is missing, so an older app version sees that message at publish. (iOS, Android, Web)
The MCP address shown in the assistant setup guides (Claude, ChatGPT, Le Chat) is the address of the environment the app runs in: staging shows the staging server, production the production server. It used to be the production address everywhere, including on staging. On the web it is read from the host's container environment (QUE_RICO_MCP_SERVER_URL); native builds carry it per EAS profile. (iOS, Android, Web)
1.6.0
Update ohne Store
14. Oktober 2026
Ingredient substitution, food photos and "what I have at home" — one release (needs backend 0.4.0; contracts ../que-rico/.claude/plans/2026-10-10_ingredient-substitution-graph-contract.md and ../que-rico/.claude/plans/2026-10-11_substitute-swaps-and-pantry-search-contract.md). Three sources of a substitute, always labelled, in this order: reviewed alternatives from the catalogue, the recipe author's own, and suggestions from an automatic mapping that are always marked as estimates. (iOS, Android, Web)
Every ingredient's detail sheet lists its substitutes: reviewed rules with the converted amount, role, where the swap holds and a note; the author's alternatives; then, apart under the estimate notice, the suggestions with the reasons they were found. Signed in, entries that do not fit your allergens, diet or never-list stay listed, greyed, with the reason.
"Adapt this recipe": vegan, vegetarian, pescetarian or for your profile — the recipe is shown with the swaps in place and nutrition, labels and claims recomputed; what could not be swapped is listed; nothing is stored. The steps follow the swaps: "Die Eier (120 g) halbieren" becomes "Tofu (120 g) halbieren", by its short name and without the original's article, and the same word elsewhere in the steps ("das Hähnchen wenden") changes with it.
Every substitute in an ingredient's sheet has Verwenden: the recipe switches to that exact swap. Own picks stack with a diet chip and stay when you change it; "Original" undoes everything. A swapped-in suggestion reads as an estimate in the ingredient list too ("≈ 300 g").
Cookbook filter Habe ich: pick foods you have at home. The cookbook then also shows recipes where a reviewed swap or the author lets your food replace an ingredient, with the swap on the photo ("Rapsöl → Olivenöl"). Opening such a recipe shows it already adapted with that swap.
Food photos: most foods in the catalogue now come with a photo of the food as bought — in the wizard's ingredient search, at the top of the ingredient detail sheet and in the editor's food list. Replacing or removing a food's photo keeps the editors' choice for good.
Recipe steps name the amount after each ingredient ("die Kartoffeln (300 g) schälen"), scaled with the servings, the same as the ingredient list — at its first mention, and not where the author already says how much ("eine Prise Safran", "die Hälfte der Butter"). While writing a recipe, steps still show the name alone. A food listed twice in one recipe keeps the plain name in the steps. Units read in the plural where the language has one ("2 Prisen"), and swaps show short names ("Rapsöl" rather than "Rapsöl, zum Verzehr geeignet") in the steps, the adapt banner and the "Habe ich" badge.
Recipe wizard: each ingredient shows the catalogue's alternatives and lets the author add up to three of their own for the special case, with an optional amount and note; drafts keep them. An alternative is narrowed like the ingredient itself: its kind and bought-as chips pick "Olivenöl nativ" rather than just "Olivenöl".
Editor: a kind's substitution rules — own and inherited — can be added, changed and hidden, and a suggestion promoted to a reviewed rule; the rule being edited opens in place under its row, and "Kontext" explains that no selection means everywhere. A food's photo sits above its name, and deleting a food uses the same destructive button as the profile.
Behoben
The wizard's header (back, step name, save draft, close, progress) stays at the top while a long step scrolls, like the Back/Next bar at the bottom. It used to scroll away with the content.
"Alternative hinzufügen" in the wizard works again: its search results lay under the note field, so a tap landed there, and on iOS the first tap on a result only closed the keyboard. The same first tap now also picks a food in the cookbook's "Habe ich" search, and on iOS both result lists scroll up above the keyboard instead of opening behind it. Editing a published recipe keeps its alternatives: they load into the wizard, and saving sends them back instead of removing them.
iOS and Android: the app no longer falls back to the privacy page when it rebuilds its screens (for example after a reload); the cookbook is the base screen, and a page opened from a link has the cookbook to go back to.
Web: a visitor who is not signed in keeps the language the page was served in (the cookie or the browser's preference). The client used to switch to the browser locale after the HTML arrived, which flipped the text and raised a hydration error whenever the two differed.
1.5.1
Update ohne Store
13. Oktober 2026
Internal: one web image for every environment. The image no longer bakes the backend, the Auth0 tenant or the origin: the compose file of each host sets them as QUE_RICO_* container variables, the server writes them into the page per request and the browser bundle reads them from there. The same image is :next on staging and, re-tagged on promotion, :latest on production — as the backend and MCP images already were. The second export that 1.5.0 added to release.yml is gone; its :next image had in fact still carried the production values, because Metro's cache served the first export's modules. Requires the matching compose change in que-rico on the hosts before this version is promoted. Fallbacks without any configuration are the staging environment throughout (constants/api.ts, constants/site.ts included). (Web)
1.5.0
Update ohne Store
13. Oktober 2026
Internal: every build that is not a production artefact now runs against the staging environment — the staging backend and the staging Auth0 tenant: local development (the fallbacks in the code), the EAS development and preview profiles, the over-the-air updates on the preview channel, and the web image tagged :next, which release.yml now exports a second time with staging values. Production builds, the production channel and the web image tagged :<version> / :latest are unchanged: their values come from the workflows, which now also set the web client id explicitly. Background: the production Auth0 tenant loses its localhost callbacks (que-rico, Auth0 as code, 2026-10-03). Existing preview and development builds must be rebuilt once — their Auth0 domain, part of the native build, changed to staging. (iOS, Android, Web)
1.4.3
Update ohne Store
13. Oktober 2026
Geändert
Internal, documentation only: the web deployment runbook describes the current pipeline (GHCR image built on merge, promoted on release, served by the Node server behind the edge cache) instead of the retired static export on Docker Hub; the Claude agent briefs (.claude/agents/) describe the current styling, navigation, data and auth setup; CLAUDE.md records that the Auth0 configuration for the native HTTPS callbacks is done. No change to the app.
1.4.2
Update ohne Store
10. Oktober 2026
The profile screen shows which version this installation runs: the version always, the store build once an over-the-air update has moved past it, and the short id of the running update — so "which version do you have?" has one answer even when the store listing shows an older number. Web shows the version alone, and also in the footer of every page, without login. (iOS, Android, Web)
1.4.1
Store-Release
10. Oktober 2026
time (the version fields leave it); every later release without native changes is an over-the-air update.
Releases without native changes reach installed apps as over-the-air updates again instead of a store build: the native fingerprint no longer includes the version fields (version, build number, version code), which change with every pull request. (iOS, Android)
Every changelog section now opens with its delivery path — Delivery: over-the-air or Delivery: store release — <native change> — so the store steps (App Store Connect "What's New", Play Console rollout) are decided per change, not discovered at promotion time. The pull-request check enforces the line.
1.4.0
4. Oktober 2026
The ingredient catalogue is now EFSA's FoodEx2 food classification, with nutrition from the German BLS 4.0 and USDA. Needs backend 0.3.0.Neu
Pick the kind and the form of an ingredient (iOS, Android, Web). Below each ingredient in the recipe wizard you choose the kind ("Pink salmon", "Wholemeal rye flour") and how it was bought (raw, frozen, smoked …); the "cooked as" menu offers only the ways that food is actually cooked. Search also finds a kind directly ("Canned fish › Canned salmon") and marks foods without nutrition data.
Skip whole food groups in the cookbook (iOS, Android, Web). "No fish", "No pork", "No nuts" … hide every recipe containing any food of the group, including what is made from it. Your profile's never-foods show as standing rules.
Ingredient details (iOS, Android, Web). Tap an ingredient in a recipe for its allergens, traces, diet label, density and nutrition per 100 g, with the data source.
Editor: FoodEx2 food items (Web). Browse by FoodEx2 category, edit a food's kinds and forms (allergens, diet tier, density, piece weight), create foods, kinds and forms FoodEx2 does not name, and see each food's FoodEx2 classification path with its codes and each kind's FoodEx2 code.
Editor: nutrition values on every form (iOS, Android, Web). Editors enter or correct the nutrition of any form, also where the catalogue has no data (Baklava). The eight core values are required; minerals, vitamins, fats, carbohydrate detail and amino acids each have their own section, and a note says where the values come from. The editor's values replace the source values in recipes; "Reset to BLS" brings the source back.
Geändert
Ingredient names come from the FoodEx2 catalogue; German and Spanish names are machine-translated until reviewed.
Behoben
The +/− steppers (servings, times) now react to a single click on the web; holding still repeats. (Web)
German filter chips keep nouns capitalised ("Kein Fisch", not "Kein fisch").
Liquids can be entered in ml as well as g (iOS, Android, Web). A food whose form has a density (milk, oil, juice, broth) now offers g, kg, ml and l in the recipe wizard, with ml as the default; solids keep g, kg, Prise and Stück. This matches what the backend accepts, so "Prise" on a liquid can no longer fail at publish.
The keyboard no longer covers the field being typed in — in the editor ("Add kind"), the recipe wizard (video link, steps, notes), the profile and My Area; the screen scrolls it into view. (iOS)
Names of cuisines, recipe types, tools, food groups and ingredients start with a capital letter everywhere — wizard, filters, profile, recipe page, editor — and keep the rest as written ("Brühe (Würfel oder Pulver)", not "Würfel Oder Pulver"; "Deutsch", not "deutsch").
Recipe wizard: the ingredients, preparation and step lists scroll with a swipe anywhere on a row, not only beside the list. Reordering starts on the ⋮⋮ grip, as before. (iOS, Android; the web keeps its plain lists)
Internal: Argent (native UI testing by Claude) is registered in the repo; the German/Spanish chip, search and editor behaviour above were verified on all three platforms.
1.3.5
28. September 2026
Geändert
Internal: the logic modules (API clients, utilities, constants, types, i18n bootstrap) are now covered by unit tests — 869 tests, 99.9 % of lines and 97.8 % of branches, up from 66 % / 76 %. No change to the app.
1.3.4
27. September 2026
Behoben
My Area: the "Published" count in the kitchen summary no longer changes when the Favourites tab is selected — it counts published recipes only.
Android: a resumed draft's photo now shows in the photo step, the review and the draft card. The private draft image is downloaded with the account token into the app cache and shown from there (iOS and web unchanged in behaviour).
Geändert
Internal: dependency updates from npm audit fix (25 advisories → 14; the rest are inside Expo SDK 57's own dependency tree and wait for upstream). CI installs with --ignore-scripts and runs the tools through package scripts instead of npx.
Internal: every pull request is analysed by SonarCloud and its quality gate (coverage on new code, new issues) fails the CI job. Coverage is measured on the logic modules (api, utils, types, constants); the React tree is analysed but not coverage-gated, as the project has no component tests.
1.3.3
27. September 2026
Geändert
Internal: the code base is lint-clean under the React Compiler rules, and the CI lint now fails on any warning. Lists reset to page 1 and URL-requested tabs are derived during render instead of in an effect, so the first frame after a new search or a deep link already shows the right page and tab (all platforms; no visible change otherwise).
1.3.2
27. September 2026
Geändert
CI only: the web image is built in minutes again. The bundle is exported natively on the ARM build runner and only copied into the amd64 image; running the export inside the image build meant Metro under emulation and the release job hit its 30-minute timeout. The Dockerfile is unchanged for a self-contained build (the local stack).
1.3.1
27. September 2026
Geändert
CI only, nothing in the app: the GitHub Actions the workflows use are moved to their Node 24 releases (actions/checkout@v7, actions/setup-node@v7, docker/setup-buildx-action@v4, docker/build-push-action@v7). Every run had been warning that GitHub is retiring Node 20 for actions.
1.3.0
27. September 2026
Neu
Update required screen (iOS, Android). The app now asks the backend for the oldest supported version on launch and when it returns to the foreground. A build older than that shows a full-screen prompt with an "Update now" button to the App Store or Google Play; an available over-the-air update is applied first. Nothing changes while the check is loading or unreachable. From the next store release on, older builds are asked to update once the new one is live in both stores.
1.2.1
27. September 2026
Geändert
The display name of a new account is no longer set by the app. The backend now gives every account "Chef Incognito" on first contact, whichever client that is, and the profile screen shows it right away; you still choose your own name on the profile screen as before. New accounts no longer start with the name from the sign-in provider — a pseudonym until you decide is the safer default for a name that appears on public recipes. Existing accounts keep their names. (iOS, Android, Web)
1.2.0
26. September 2026
Neu
The web app remembers an explicit light or dark choice in a cookie and renders it on the server, so a page never flashes the wrong theme (Web).
This changelog, bumped together with the version in every pull request into main, and pr-checks.yml to check it.
release.yml (git tag, GitHub Release, web image :x.y.z + :next) on every merge into main, promote.yml (:latest) on a push to release, and an OTA update on the preview channel on every merge into main (iOS, Android).
Geändert
The app talks to the backend's versioned API (/v1/...), so future breaking API changes can ship next to the old routes without breaking installed builds.
The assistant setup guides show the new MCP address https://mcp.que-rico.net/mcp (Web).
Upgraded to Expo SDK 57 (React Native 0.86) on all three platforms. New store builds are required; older installs stop receiving over-the-air updates.
Over-the-air compatibility now follows the native code fingerprint instead of the version number, so the version can be bumped for every release without orphaning the update channel (iOS, Android).
Gluestack core and utils moved from alpha tags to the stable 5.0.15 / 5.0.6, and every local customisation in the vendored components is marked.
Behoben
The server address on the assistant setup guides no longer logs a React warning: the web text component now maps selectable to CSS instead of passing it to the DOM (Web).
The profile menu on the web uses a fixed trigger id, so the menu stays attached to its button across server render and hydration (Web).
## [1.1.0] and earlierReleased before this changelog existed; see the git history and the merged pull requests.
© 2026 ¡Qué rico!