<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Adem İŞLER</title>
    <description>The latest articles on DEV Community by Adem İŞLER (@ademisler).</description>
    <link>https://dev.to/ademisler</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3906784%2F4cdcc8bc-99f5-45bb-8696-6748452b1581.png</url>
      <title>DEV Community: Adem İŞLER</title>
      <link>https://dev.to/ademisler</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ademisler"/>
    <language>en</language>
    <item>
      <title>I built an Android app to solve my own “what should I cook?” problem</title>
      <dc:creator>Adem İŞLER</dc:creator>
      <pubDate>Thu, 30 Apr 2026 22:59:48 +0000</pubDate>
      <link>https://dev.to/ademisler/i-built-an-android-app-to-solve-my-own-what-should-i-cook-problem-43nj</link>
      <guid>https://dev.to/ademisler/i-built-an-android-app-to-solve-my-own-what-should-i-cook-problem-43nj</guid>
      <description>&lt;p&gt;I just launched &lt;strong&gt;Chefrise&lt;/strong&gt; on Android.&lt;/p&gt;

&lt;p&gt;The original problem was simple: I would look at the ingredients I already had and still not know what to cook.&lt;/p&gt;

&lt;p&gt;So I built a small product around that moment.&lt;/p&gt;

&lt;p&gt;Chefrise lets you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;add or scan pantry items&lt;/li&gt;
&lt;li&gt;ask an AI chef for recipe ideas based on your pantry&lt;/li&gt;
&lt;li&gt;save recipes&lt;/li&gt;
&lt;li&gt;turn missing ingredients into a shopping list&lt;/li&gt;
&lt;li&gt;complete recipes and build cooking streaks&lt;/li&gt;
&lt;li&gt;see XP and league progress&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The interesting part was not just the AI.&lt;/p&gt;

&lt;p&gt;The harder product question was retention.&lt;/p&gt;

&lt;p&gt;A recipe app can easily become something people open once, generate a recipe, and forget. I wanted the loop to feel more like Duolingo: small progress, streaks, XP, leagues, and a reason to come back tomorrow.&lt;/p&gt;

&lt;p&gt;The stack is Expo React Native, Supabase, Edge Functions, and AI recipe generation. Codex helped me move quickly on implementation, but the product psychology took the most thought.&lt;/p&gt;

&lt;p&gt;A few things I learned:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI is only useful when it starts from real user context.&lt;/li&gt;
&lt;li&gt;Pantry state matters more than a generic recipe prompt.&lt;/li&gt;
&lt;li&gt;Streaks should reward meaningful action, not just opening the app.&lt;/li&gt;
&lt;li&gt;Mobile UX details like haptics, keyboard behavior, push routing, and fast session restore matter a lot.&lt;/li&gt;
&lt;li&gt;“Generate recipe” is not the product; the habit loop around cooking is the product.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Android is live now:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://play.google.com/store/apps/details?id=com.chefrise.mobile" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.chefrise.mobile&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The landing page is here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://chefrise.app" rel="noopener noreferrer"&gt;https://chefrise.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m still improving the loop and would value feedback from people who cook at home or build consumer apps.&lt;/p&gt;

</description>
      <category>reactnative</category>
      <category>ai</category>
      <category>mobile</category>
      <category>buildinpublic</category>
    </item>
  </channel>
</rss>
