<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Utku Glsvn on Medium]]></title>
        <description><![CDATA[Stories by Utku Glsvn on Medium]]></description>
        <link>https://medium.com/@utkuglsvn?source=rss-ca23c9f3bc77------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yeoFsBfVuriPj5UeVoa-OQ.png</url>
            <title>Stories by Utku Glsvn on Medium</title>
            <link>https://medium.com/@utkuglsvn?source=rss-ca23c9f3bc77------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:25:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@utkuglsvn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Açık Kaynaklı Uygulama Yorum Analizi Aracı “Review Matrix”]]></title>
            <link>https://utkuglsvn.medium.com/a%C3%A7%C4%B1k-kaynakl%C4%B1-uygulama-yorum-analizi-arac%C4%B1-review-matrix-f5c8d7ccfe81?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5c8d7ccfe81</guid>
            <category><![CDATA[app-store-optimizasyonu]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[flask]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 17:05:39 GMT</pubDate>
            <atom:updated>2026-10-24T17:05:39.939Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Flask, pandas tabanlı, Play Store ve App Store’daki yorum ve puan analiz toolu.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pUwPaQXkgOzXrtbU.png" /><figcaption><a href="https://appreviewmetrix.onrender.com/analyze">https://appreviewmetrix.onrender.com/analyze</a></figcaption></figure><h3>Problem</h3><p>ReviewMetrix iki mağazadan yorumları çekip şu sorulara cevap veriyor: Kullanıcılar neden şikâyet ediyor? Önce hangisini düzeltmeliyiz? Uygulama iyiye mi gidiyor, kötüye mi? Hangi sürüm işleri bozdu? Mağaza sayfamızda hangi kelimeler eksik?</p><blockquote><em>GitHub: </em><a href="https://github.com/UtkuGlsvn/ReviewMetrix"><em>github.com/UtkuGlsvn/ReviewMetrix</em></a><em> (MIT lisanslı)</em></blockquote><blockquote>Demo:<a href="https://appreviewmetrix.onrender.com/">https://appreviewmetrix.onrender.com/</a></blockquote><h3>Teknoloji</h3><p>Flask, pandas, NLTK, TextBlob ve ApexCharts.</p><h3>Öne Çıkan Özellikler ve Tasarım Kararları</h3><p><strong>1. Gerçek Önceliklendirme (Fix First)</strong> Şikayetleri sadece kaç kişinin yazdığına göre sıralamak genelde yanlış yere odaklanmanıza sebep olur. Uygulamanızın çöktüğünü söyleyen 1 yıldızlı 2 yorum ve bunlara gelen 8 beğeni (yani “bende de aynısı oluyor” diyen 8 kişi), arayüzün kalabalık olduğunu söyleyen 3 yıldızlı 7 yorumdan çok daha acildir.</p><p>Bunu çözmek için önceliği etkiye göre hesaplayan bir formül kullandım: Öncelik = (Şikayet + Beğeni) × (5 - Ortalama Puan). Bu sayede gerçekten can yakan sorunlar her zaman listenin en tepesine çıkıyor.</p><p><strong>2. Puan Momentumu ve Regresyon Avı</strong> Mağazadaki genel puanınız bugünü yansıtmaz, geçmişin birikimidir. ReviewMetrix, mağazadaki genel puanı son yorumların ortalamasıyla kıyaslayarak gidişatın düşüşte mi yoksa yükselişte mi (±0.3 eşiğiyle) olduğunu söyler. Ayrıca yorumları eskiye ve yeniye bölerek, yeni dönemde aniden artış gösteren kelimeleri yakalarız. Bu, sürüm kırılımlarıyla birleştiğinde <em>“Bu sorun tam olarak 4.12.0 sürümünde başladı”</em> diyebilmemizi sağlıyor.</p><p><strong>3. ASO Kelime Boşluğu ve NLP:</strong> Kullanıcılarınızın yorumlarda sıkça kullandığı ama sizin mağaza açıklamanızda hiç geçirmediğiniz kelimeler var (Örneğin Spotify yorumlarında <em>Apple Music</em> kelimesinin sıkça geçmesi gibi). Bu harika bir ASO (Uygulama Mağazası Optimizasyonu) fırsatıdır.</p><h3>Hemen Deneyin</h3><p>Açık kaynaklı projemi bilgisayarınızda ayağa kaldırmak çok kolay:</p><pre>git clone https://github.com/UtkuGlsvn/ReviewMetrix.git<br>cd ReviewMetrix<br>python3 -m venv venv &amp;&amp; source venv/bin/activate<br>pip install -r requirements.txt<br>pip install --no-deps app-store-scraper==0.3.5<br>python run.py</pre><p>Sonrasında [http://127.0.0.1:4999](http://127.0.0.1:4999) adresini açıp, örneğin com.spotify.music yazarak ilk analizinizi hemen başlatabilirsiniz.</p><p><a href="https://github.com/UtkuGlsvn/ReviewMetrix">github.com/UtkuGlsvn/ReviewMetrix</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5c8d7ccfe81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Turn App Reviews into a Prioritized To-Do List with an Open-Source Tool]]></title>
            <link>https://utkuglsvn.medium.com/how-to-turn-app-reviews-into-a-prioritized-to-do-list-open-source-building-review-intelligence-2d35c22cf7ce?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d35c22cf7ce</guid>
            <category><![CDATA[app-store-optimization]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[nlp]]></category>
            <category><![CDATA[flask]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 16:57:09 GMT</pubDate>
            <atom:updated>2026-10-24T17:14:29.694Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How I turned thousands of raw Play Store and App Store reviews into a prioritized to-do list, using Flask, pandas, NLTK, and a handful of carefully chosen formulas.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fQaye0F4vAwDZ665.png" /><figcaption><a href="https://appreviewmetrix.onrender.com/analyze">https://appreviewmetrix.onrender.com/analyze</a></figcaption></figure><h3>The problem: reviews are data, but nobody treats them that way</h3><p>If you ship a mobile app, your users are sending you a free, continuous stream of product feedback. It lives in the Google Play Store and the Apple App Store, and for most teams it’s handled in one of two ways: someone scrolls through it now and then, or nobody looks at all.</p><p>Scrolling doesn’t scale. Read the latest fifty reviews and you’ll remember the angriest three, not the most common one. You can’t tell whether “login is broken” is a pattern or one person’s bad day. And the number everyone actually watches, the star rating on the store page, is close to useless for spotting what’s happening <em>now</em>.</p><p>Here’s why. The store shows a lifetime average. An app with ten million historical ratings can lose a lot of goodwill this month and the headline number will barely move. When I ran Spotify through the tool I’m about to describe, the store said 4.34, while its last 200 reviews averaged 3.81. That gap is the real signal, and the store page hides it.</p><p>So I built ReviewMetrix, an open-source Flask app that scrapes reviews from both stores and turns them into a dashboard built around a few practical questions:</p><ul><li>What are users complaining about, grouped into themes rather than individual rants?</li><li>Which problem should we fix first, weighted by how many people it hurts and how badly?</li><li>Is the app getting better or worse right now?</li><li>Which release broke things?</li><li>Which words do users use that our store listing never mentions? (That’s an ASO opportunity.)</li><li>How do we compare to a competitor, or to ourselves in another country?</li></ul><p>The rest of this post covers how it works, the design decisions behind it, and a few lessons that turned out to matter more than I expected.</p><blockquote><em>Demo: </em><a href="https://appreviewmetrix.onrender.com/">https://appreviewmetrix.onrender.com</a></blockquote><blockquote><em>GitHub: </em><a href="https://github.com/UtkuGlsvn/ReviewMetrix"><em>github.com/UtkuGlsvn/ReviewMetrix</em></a></blockquote><h3>Architecture at a glance</h3><p>ReviewMetrix is intentionally boring in shape: one Python process, server-rendered HTML, no database.</p><pre>reviewMetrix/</pre><pre>├── __init__.py         # Application factory, NLTK bootstrap</pre><pre>├── routes.py           # /, /analyze, /compare, /compare-countries, /prompts</pre><pre>├── analyzer.py         # Scraping, caching, analysis, ASO</pre><pre>├── ratelimit.py        # Per-IP scrape budget</pre><pre>├── prompt_library.py   # Loads SEO/ASO/AIO prompt templates from Markdown</pre><pre>├── prompts/            # Prompt files, by category</pre><pre>└── templates/          # Jinja2 + ApexCharts dashboards</pre><p>The request flow is a straight line:</p><ol><li>Fetch. Scrape reviews from Google Play and/or the App Store, plus listing metadata (title, description, lifetime rating).</li><li>Normalize. Merge both sources into a single pandas DataFrame with a platform column.</li><li>Analyze. Run a set of independent analysis functions over that frame.</li><li>Render. Pass the results to a Jinja template that splits them into four tabs: Overview, Issues, ASO, and Trends &amp; Reviews.</li></ol><p>The most useful architectural choice was making every analysis function defensive and independent. Each one takes a DataFrame and returns a plain dict or list. When it fails, it logs a warning and returns an empty result. That matters because scrapers are fragile. If Apple changes an endpoint and App Store reviews come back empty, you still get a report from the Google Play data instead of a 500 error.</p><h3>Deep dive 1: “Fix First” prioritization</h3><p>The most obvious way to rank complaint themes is by raw count, and it’s wrong.</p><p>Suppose seven people mildly complain that the UI is “a bit cluttered” and give 3 stars. Meanwhile two people report that the app crashes on launch and give 1 star, and eight more users thumbs-up those crash reviews. Raw count says UI first. Common sense says crashes first.</p><p>ReviewMetrix ranks themes by:</p><pre>priority = (complaints + likes) × severity</pre><pre>severity = 5 − average rating of that theme&#39;s reviews</pre><p>A like on a review is effectively another user saying “me too,” so likes count as affected users. Severity punishes themes whose reviews skew toward 1 star. Here’s the core of it from categorize_complaints:</p><pre># priority = affected users x severity</pre><pre>#   affected = complaints + likes (a like is another &quot;me too&quot;)</pre><pre>#   severity = 5 - average rating (lower rating, worse problem)</pre><pre>affected = cnt + likes[theme]</pre><pre>severity = (5 - avg_score) if avg_score is not None else 3.0</pre><pre>themes.append({</pre><pre>&#39;theme&#39;: theme,</pre><pre>&#39;count&#39;: cnt,</pre><pre>&#39;likes&#39;: likes[theme],</pre><pre>&#39;avg_score&#39;: avg_score,</pre><pre>&#39;affected&#39;: affected,</pre><pre>&#39;priority_raw&#39;: round(affected * severity, 2),</pre><pre>})</pre><p>In the example, crashes score (2 + 8) × (5 − 1.0) = 40 and UI scores 7 × (5 − 3.0) = 14. Crashes win, which is the right call.</p><p>Themes come from keyword matching across ten buckets: Crashes &amp; Bugs, Performance, Ads, Login &amp; Account, Price &amp; Payment, UI &amp; UX, Updates, Notifications, Customer Support, and Privacy. A single review can count toward several themes. Keyword matching isn’t sophisticated, but it’s transparent. When a product manager asks why a review landed under “Login &amp; Account,” the answer is “it contains the word <em>password</em>,” and that’s easy to trust. For non-English languages, local keywords are merged with the English list, because real reviews mix languages...</p><h3>Deep dive 2: Rating momentum</h3><p>This is the feature behind the Spotify example. The idea is simple: compare the store’s lifetime average with the average of the reviews you just scraped, separately for each platform.</p><pre>lifetime = float(store[&#39;rating&#39;])</pre><pre>recent = float(subset[&#39;score&#39;].mean())</pre><pre>delta = recent - lifetime</pre><pre>if delta &lt;= MOMENTUM_DECLINE_THRESHOLD:      # -0.3</pre><pre>status = &#39;declining&#39;</pre><pre>elif delta &gt;= MOMENTUM_IMPROVE_THRESHOLD:    # +0.3</pre><pre>status = &#39;improving&#39;</pre><pre>else:</pre><pre>status = &#39;stable&#39;</pre><p>The ±0.3 threshold is deliberately coarse. A recent sample of a couple of hundred reviews is noisy, and a tool that cries “declining!” over a 0.05 dip will be ignored within a week. The dashboard also has a “Why this number?” popup that shows the underlying distribution, so nobody has to take the label on faith.</p><h3>Deep dive 3: Catching regressions early with trending keywords</h3><p>Momentum tells you <em>that</em> something is wrong. Trending keywords help explain <em>what</em>.</p><p>Complaints are sorted by date and split into an older half and a newer half. For each word, the tool computes its document frequency as a percentage of that window’s complaints, then ranks words by how much that percentage rose:</p><pre>rec_pct = rec_hits * 100 / n_rec</pre><pre>old_pct = old_hits * 100 / n_old</pre><pre>delta = rec_pct - old_pct</pre><pre># Only rising words that appear at least twice in the newer window</pre><pre>if rec_hits &gt;= 2 and delta &gt; 0:</pre><pre>scored.append({... &#39;change&#39;: round(delta, 1), &#39;is_new&#39;: old_hits == 0})</pre><p>Two details matter here:</p><ul><li>Normalizing per window. The two halves can contain different numbers of complaints, especially after date filtering, so raw counts would be biased. Percentages keep the comparison fair.</li><li>Flagging brand-new words. A word with zero occurrences in the older window that suddenly shows up in the newer one (“bluetooth,” “widget,” “paywall”) is often the first sign of a regression from a specific release.</li></ul><p>That pairs with the version breakdown, which groups complaints by app version along with average rating and sentiment, so you can see that 4.12.0 is where things went wrong.</p><h3>Deep dive 4: ASO keyword gap, or listening to your users’ vocabulary</h3><p>App Store Optimization usually starts with keyword research tools that guess what people search for. ReviewMetrix takes a different, complementary angle: which words do your users keep using in reviews that your store listing never mentions?</p><p>On Spotify, this surfaced apple music and youtube music, which means users are actively comparing it with competitors. That&#39;s useful for positioning, and the listing doesn&#39;t address it.</p><p>The interesting engineering lesson was in the noun filtering. ASO keywords are overwhelmingly nouns, so the tool POS-tags text with NLTK and keeps only nouns. My first version tagged the <em>cleaned</em> token list, with stopwords already removed. The results were bad:</p><pre>def _noun_set(text, lang_code=&#39;en&#39;):</pre><pre>&quot;&quot;&quot;POS-tag raw text and return the set of words tagged as nouns.</pre><pre>Tagging must run on the RAW text: in a stopword-stripped bag the tagger</pre><pre>has no context and becomes unreliable. Measured on such a bag,</pre><pre>&quot;audiobooks&quot; came back a verb (VBP) and &quot;wherever&quot; a noun (NN).</pre><p>A POS tagger is a sequence model and needs grammatical context. Feed it a bag of words and it guesses. The fix was to tag the raw text, collect the set of words tagged as nouns, and then filter the cleaned tokens against that set. Bigrams such as sound quality are taken from the unfiltered stream and only need to contain at least one noun, so useful phrases survive.</p><p>The ASO tab also includes:</p><ul><li>Listing health: title and description length against the 30 / 4000 character limits, plus rating and review-volume thresholds.</li><li>Competitor ASO gap: “they target, you don’t” vs. “you target, they don’t.” Brand and developer names are excluded because they aren’t transferable keywords.</li></ul><p>An honest caveat, also stated in the UI: this measures user vocabulary, not search volume. The public store APIs don’t expose real search-volume data.</p><h3>Deep dive 5: Multilingual sentiment without lying</h3><p>Sentiment for English reviews uses TextBlob. For Turkish, German, Spanish, and French, ReviewMetrix uses a small lexicon-based scorer with negation handling. If a negation word appears within the two tokens before a polar word, the polarity flips:</p><pre>window = tokens[max(0, i - 2):i]</pre><pre>if any(w in negations for w in window):</pre><pre>polarity = -polarity</pre><p>It also prefix-matches lexicon entries of five or more characters to handle inflected forms, which matters a lot for agglutinative languages like Turkish.</p><p>The more important decision, though, is what happens for languages that <em>aren’t</em> supported. The easy route is returning 0.0, which then shows up as &quot;neutral.&quot; That&#39;s a lie: it presents &quot;we couldn&#39;t measure this&quot; as &quot;users feel neutral.&quot; ReviewMetrix instead hides the sentiment sections and shows an explicit notice. Ratings, themes, keywords, and trends still work.</p><p>I think this is a general principle for analytics tools: a missing number is better than a misleading one.</p><h3>Performance: a small, honest cache</h3><p>Scraping is slow (a few seconds per app per store) and it’s the scarce resource, since the stores rate-limit and eventually block heavy callers. ReviewMetrix uses an in-memory TTL + LRU cache keyed by (app, country, language, review count):</p><pre>with _cache_lock:</pre><pre>entry = _review_cache.get(key)</pre><pre>if entry is not None:</pre><pre>cached_at, cached_df, cached_stats = entry</pre><pre>if now - cached_at &lt; ttl:</pre><pre>_review_cache.move_to_end(key)  # mark as most recently used</pre><pre>return cached_df.copy(), copy.deepcopy(cached_stats)</pre><pre>del _review_cache[key]  # expired</pre><p>Three small decisions do most of the work:</p><ol><li>Return copies. Analysis functions mutate DataFrames. Without .copy(), one request could quietly corrupt the cached data for the next.</li><li>Never cache empty results. If a scraper hiccups once, you don’t want “no reviews” stuck in the cache for an hour.</li><li>Bound the size. An OrderedDict with a 32-entry LRU cap keeps memory predictable. Measured: about 126 MB idle and 326 MB warm, which fits a 512 MB free-tier host.</li></ol><p>Measured on live data, a single app goes from 2.42s to 0.22s on a cache hit, and a three-country comparison drops from 6.25s to 0.53s. A Force refresh checkbox bypasses the cache when you need fresh data.</p><h3>Being a good citizen: rate limiting by cost, not by request</h3><p>An open deployment of a scraper needs a ceiling, both to protect the host’s IP from store blocks and to stop one user from draining everyone’s budget. A naive “N requests per hour” limiter doesn’t fit, because requests don’t cost the same:</p><ul><li>A single analysis performs 1 scrape.</li><li>A competitor comparison performs 2.</li><li>A six-country comparison performs 6.</li></ul><p>So ratelimit.py implements a sliding-window limiter that counts scrape units:</p><pre>def check(self, key, cost=1):</pre><pre>&quot;&quot;&quot;Record `cost` units against `key`.</pre><pre>Returns (allowed, remaining, retry_after_seconds). Nothing is recorded</pre><pre>when the request is rejected, so a blocked caller cannot push their own</pre><pre>reset further away by retrying.</pre><pre>&quot;&quot;&quot;</pre><p>That last property is easy to get wrong. If rejected attempts count against the budget, an impatient user who keeps hitting refresh while blocked extends their own lockout forever. Over-budget requests get a 429 with a Retry-After header.</p><p>There’s also a deliberate trust boundary: X-Forwarded-For is ignored unless TRUST_PROXY=1 is set. Otherwise any client could send a forged header and get a fresh IP, and a fresh budget, on every request.</p><h3>Security hardening for a “simple” internal tool</h3><p>A tool that takes user input, calls external services, and exports files has a bigger attack surface than its size suggests. A few hardening steps from the commit history:</p><ul><li>CSV formula injection. Review text is user-generated. A review starting with =, +, -, or @ becomes a live formula when someone opens the exported CSV in Excel. Export cells are neutralized before they&#39;re written.</li><li>No exception details in responses. Stack traces and library errors are logged server-side, and users see a generic message.</li><li>Input parsing. You can paste a full Play Store or App Store URL and the server extracts the ID or slug, so arbitrary strings aren’t passed straight to the scrapers.</li><li>Debug off by default. FLASK_DEBUG defaults to 0. The Werkzeug interactive debugger is effectively remote code execution if it&#39;s ever exposed.</li><li>Non-root Docker image, with NLTK corpora downloaded at build time so the container doesn’t make network calls on its first request.</li></ul><h3>Testing a scraper without the network</h3><p>Every one of the 253 tests runs offline. The scraping layer is patched out, so the suite is fast, deterministic, and doesn’t depend on Apple’s or Google’s mood that day.</p><p>One testing habit I’d recommend to anyone: make your fixtures discriminating. If you’re testing that themes are sorted by priority, don’t build a fixture where every theme has the same count. A test like that passes whether the sort is ascending, descending, or missing. ReviewMetrix’s ordering fixtures use deliberately unequal counts, so the sort direction is actually asserted.</p><p>The suite covers the analyzer pipeline and each of its error branches, all routes including partial failures (one app or one market returning nothing), cache TTL and LRU eviction order, per-language sentiment and negation, ASO fallback when the POS tagger is unavailable, the rate limiter’s window mechanics and proxy trust boundary, and the prompt library.</p><h3>Bonus: a prompt library for SEO, ASO, and AIO</h3><p>Analysis tells you what to fix. You still have to write the copy. ReviewMetrix includes a /prompts page with copy-ready LLM prompt templates in three tabs:</p><ul><li>SEO: keyword clusters, title/meta, content briefs, internal linking, FAQ schema</li><li>ASO: title/subtitle, keyword field, long description, review responses, screenshot captions</li><li>AIO (AI Optimization / Generative Engine Optimization): answer-first content, citable facts, comparison tables, and entity schema, so content gets picked up by AI answer engines like AI Overviews, ChatGPT, and Perplexity</li></ul><p>Each prompt is a Markdown file with a small front-matter block under reviewMetrix/prompts/{seo,aso,aio}/. Adding a new one means dropping in a .md file, with no code changes. That keeps contributions open to marketers and content people, not just developers.</p><h3>Known limitations</h3><p>I’d rather list these myself than have a user discover them:</p><ul><li>Some signals are Google Play only. The App Store scraper exposes neither the app version per review, nor likes, nor developer replies. Version breakdown, likes weighting, and developer response analysis therefore cover Google Play only, and the UI says so.</li><li>App Store scraping is fragile. Failures are caught so the rest of the report still renders.</li><li>Non-English sentiment is lexicon-based, not a transformer model. It handles clearly polar wording and negation but scores purely factual complaints as 0.</li><li>Cache and rate-limit counters are per-process. That’s why the recommended deployment is gunicorn --workers 1 --threads 8. Scraping is I/O-bound, so threads provide the concurrency without splitting the cache. Scaling out would need Redis.</li><li>Cloud IPs get blocked more readily than residential ones, so scraping that works from your laptop may return 403s from a datacenter.</li></ul><h3>Try it</h3><pre>git clone https://github.com/UtkuGlsvn/ReviewMetrix.git</pre><pre>cd ReviewMetrix</pre><pre>python3 -m venv venv &amp;&amp; source venv/bin/activate</pre><pre>pip install -r requirements.txt</pre><pre>pip install --no-deps app-store-scraper==0.3.5</pre><pre>python run.py</pre><p>Then open http://127.0.0.1:4999, enter a Play Store ID like com.spotify.music, and click Fetch &amp; Analyze Reviews. There&#39;s also a Dockerfile if you&#39;d rather run it in a container.</p><h3>Takeaways</h3><p>Building ReviewMetrix reinforced a few lessons that apply well beyond app reviews:</p><ol><li>Headline metrics hide the present. Lifetime averages, cumulative totals, and all-time counts tend to lag. Compare against a recent window.</li><li>Rank by impact, not volume. affected × severity beats count almost every time.</li><li>Give NLP models the context they need. A POS tagger fed a bag of words is just guessing.</li><li>Show nothing rather than something misleading. A hidden chart with a clear notice beats a confident-looking zero.</li><li>Small, boring infrastructure goes a long way. An OrderedDict cache and an in-memory sliding window covered everything this project needed, as long as the trade-offs are written down.</li></ol><p>ReviewMetrix is MIT licensed and contributions are welcome, especially new prompt templates, which don’t require any code. If you run it on your own app and find something surprising in the momentum or keyword gap, I’d love to hear about it.</p><p>⭐ <a href="https://github.com/UtkuGlsvn/ReviewMetrix">github.com/UtkuGlsvn/ReviewMetrix</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d35c22cf7ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Shipped Two Real-Time Map Games on a Single Codebase]]></title>
            <link>https://utkuglsvn.medium.com/how-i-shipped-two-real-time-map-games-on-a-single-codebase-4a4075649dc0?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a4075649dc0</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[supabase]]></category>
            <category><![CDATA[indiehackers]]></category>
            <category><![CDATA[outbid]]></category>
            <category><![CDATA[polar]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 12:17:35 GMT</pubDate>
            <atom:updated>2026-08-29T12:17:35.038Z</atom:updated>
            <content:encoded><![CDATA[<p><em>*How I turned the “r/place but with money” itch into two realtime web apps using Next.js, Supabase, and Polar checkout.*</em></p><p>There is a very specific kind of internet chaos that happens when you give people a blank canvas, charge them a trivial amount of money, and let them fight over pixels. It’s the energy of Reddit’s r/place mixed with the petty rivalries of a local pub debate. I wanted to capture that exact feeling — a digital turf war where anyone can claim a country, drop a meme, and rule it until someone else pays exactly one dollar more to overthrow them.</p><p>That was the absurd, simple premise behind BanterMap. I wanted to build something highly interactive, deeply silly, and entirely shippable for a solo developer. No politics, no grand utility — just pure banter and pixel blood. But as I started architecting the map, I realized the engine I was building was capable of much more than a single joke.</p><p><strong>Two Products, One Engine</strong></p><p><a href="https://www.bantermap.lol/">BanterMap</a> is the chaotic original flavor: you pick a country, pay a dollar (or two for major economies), and your chosen image and message are crowned. To make it slightly more cooperative, I added a “co-conquest” feature so friends can buy into your throne without dethroning you.</p><p>But distribution is the hardest part of any indie project. A generic turf war is fun, but it doesn’t target a specific, highly engaged community. Football fans, however, live for turf wars.</p><p>That realization birthed <a href="https://fans.bantermap.lol/">FanMap</a>. Instead of claiming a country for yourself, you paint the map for your football club. Fans buy votes, and whichever club has the most votes in a given country paints it their colors. I spun FanMap out onto a subdomain, deliberately keeping it indexed as a separate product. Under the hood, they are the exact same machine wearing two different costumes. Building them on a shared Next.js 16 and Supabase stack meant I could ship two distinct distribution bets for the price of one codebase.</p><p><strong>Engineering the Chaos</strong></p><p>When you are a solo builder, complexity is the enemy. Every technical decision had to maximize user experience while minimizing my maintenance burden. Here is how the stack actually came together.</p><p><strong>Real-time updates without the headache</strong></p><p>When someone overthrows a country on BanterMap, or drops a massive vote bomb on FanMap, the UI needs to update instantly. A page refresh kills the magic. To solve this, I leaned heavily on Supabase Realtime.</p><p>Instead of polling the database, the Next.js frontend subscribes directly to changes on aggregate tables (`country_team_totals` for FanMap, and conquest records for BanterMap). To keep performance snappy, I don’t calculate totals on the fly. Simple Postgres database triggers recompute the totals after every single insert. The moment a payment clears and the database writes the new row, the trigger fires, the aggregate table updates, and Supabase pushes that state change to every connected client in seconds.</p><p><strong>Handling money without a backend team</strong></p><p>I needed to accept payments globally, but I absolutely did not want to manage a sprawling backend to handle webhooks, edge cases, and state reconciliation. I went with <a href="https://polar.sh/">Polar</a></p><p>The flow is entirely webhook-driven. When a user initiates a takeover, the checkout session embeds exactly what they are trying to do in the metadata: `{country_id, team_id, vote_count}`. Polar handles the UI and the transaction. Once successful, they hit my Next.js API route with a signed webhook. The endpoint verifies the signature, runs an underpayment guard to ensure the user didn’t try to manipulate the payload, and then inserts the record directly into Supabase. It’s stateless, secure, and requires zero manual oversight.</p><p><strong>Pricing as a game mechanic</strong></p><p>Static pricing is boring. For BanterMap, the overthrow mechanic dictates the price: to steal a country, you must pay the current ruler’s bid plus $1. It creates an escalating bidding war naturally.</p><p>FanMap required something different. If a country is heavily contested, buying votes there should cost more, making late-game takeovers an expensive flex. I implemented a bonding curve for vote pricing. The formula is:</p><blockquote><strong>p(N) = 0.10 × (1 + N / 200) ^ 0.95</strong></blockquote><p>But you don’t just charge the current price for a bundle of votes. To be fair, the checkout integrates the curve, charging the exact mathematical area under it for the N votes you are buying. I also added inflation tiers — buying in bulk grants 10% or 25% bonus votes — turning the pricing model itself into a strategic element of the game.</p><blockquote><strong>Trust and safety on a shoestring budget</strong></blockquote><p>User-generated content is a massive liability. If you let people upload images and text to a public map, it will be tested by bots and trolls immediately. As a solo dev, I couldn’t afford a human moderation team.</p><p>The defense in depth starts with Cloudflare Turnstile to handle basic rate-limiting and bot protection. For text, I implemented a robust profanity filter utilizing `bad-words`, which I heavily extended with a custom Turkish word list and leetspeak normalization to catch creative misspellings. For the images, I routed uploads through the Sightengine AI moderation API. It aggressively flags nudity, gore, and offensive imagery before it ever hits my storage bucket. It costs pennies and keeps the map from becoming a wasteland.</p><p><strong>Being found by AI (AEO over SEO)</strong></p><p>Traditional SEO is a bloodbath for indie hackers, so I optimized for AI Search Engines (Perplexity, ChatGPT Search, Google SGE). I heavily utilized JSON-LD `@graph` structures, shipping explicit `WebApplication`, `VideoGame`, and `Organization` entities on the pages.</p><p>Because FanMap and BanterMap share a codebase but act as separate products, I built per-country landing pages with deep links (e.g., `/?country=TR`) and strict canonical URLs. This means an AI crawler doesn’t just see a single page app; it sees a structured database of entities and can confidently answer queries like “Who owns Turkey on BanterMap right now?”</p><p><strong>Takeaways for the Indie Hacker</strong></p><p>Building and shipping these two maps taught me a few things that I’ll carry into every future project:</p><p>1. <strong>Ship the small version of the idea.</strong> The instinct is to build a massive MMORPG. The reality is that people love simple, stupidly fun mechanics. A $1 map takeover is easy to explain and easy to buy into.</p><p>2. <strong>Reuse your engine.</strong> If you build a solid core mechanic (like a real-time map), ask yourself what other audiences might want to play with it. FanMap was almost free to build because the BanterMap engine already existed.</p><p>3. <strong>Make pricing part of the fun.</strong> Don’t just slap a payment link on a page. Overthrow mechanics and bonding curves turn the act of purchasing into a core gameplay loop.</p><p>4. <strong>Design for AI crawlers now. </strong>Stop fighting for page 1 on Google. Structure your data so AI agents can read your app’s state and serve it to users who are asking complex questions.</p><p>It’s been incredibly fun watching the map heat up, seeing which countries become meme battlegrounds, and watching football fans try to paint the globe.</p><p>You can check out the chaos at</p><p>-&gt; <a href="https://www.bantermap.lol/">BanterMap</a></p><p>-&gt;<a href="https://fans.bantermap.lol/">FansMap</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVpvCfU5a7UL2V-2Gkro5g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a4075649dc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overview of GitHub Actions for Android Development GitHub Actions]]></title>
            <link>https://utkuglsvn.medium.com/overview-of-github-actions-for-android-development-github-actions-b4b3f0474529?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4b3f0474529</guid>
            <category><![CDATA[firebase-app-distribution]]></category>
            <category><![CDATA[android-cicd]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[android-github-action]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Fri, 27 Dec 2024 21:16:13 GMT</pubDate>
            <atom:updated>2024-12-27T21:16:13.651Z</atom:updated>
            <content:encoded><![CDATA[<p>Overview of GitHub Actions for Android Development GitHub Actions simplifies automation processes for Android projects, enhancing code consistency and optimizing deployment tasks. It integrates directly into GitHub repositories, allowing the management of workflows directly on GitHub. I’ll explain how I use a YAML configuration in my projects to automatically generate APKs and upload them to Firebase App Distribution after merging pull requests from development and master branches.</p><p>Creating Workflow Files: Start by creating a .github/workflows directory in your project and adding a YAML file like android.yml to define your workflow.</p><p><strong>Setting Triggers:</strong> Specify when the workflow should be triggered, such as on pushes or pull requests to specific branches.</p><pre>on:<br>  push:<br>    branches:<br>      - development<br>      - master<br>  pull_request:<br>    branches:<br>      - feature/*<br>      - bugfix/*</pre><p><strong>Environment Setup:</strong> Configure an environment compatible with Gradle — Android development.</p><pre><br>- uses: actions/setup-java@v3<br>  with:<br>    distribution: &#39;temurin&#39;<br>    java-version: &#39;17&#39;<br>- name: Cache Gradle dependencies<br>  uses: actions/cache@v3<br>  with:<br>    path: |<br>      ~/.gradle/caches<br>      ~/.gradle/wrapper<br>    key: ${{ runner.os }}-gradle-${{ hashFiles(&#39;**/*.gradle*&#39;, &#39;**/gradle-wrapper.properties&#39;) }}</pre><p><strong>Compilation and Output Verification:</strong></p><pre><br>- name: Build the project (assembleProdDebug<br>  run: ./gradlew assembleProdDebug<br>- name: List build outputs<br>  run: ls -alh app/build/outputs/apk/prod/debug/</pre><p><strong>Uploading APK to Firebase:</strong></p><pre>- name: Upload APK to Firebase App Distribution<br>  uses: wzieba/Firebase-Distribution-Github-Action@v1<br>  with:<br>    appId: ${{ env.FIREBASE_APP_ID }}<br>    file: ${{ env.APK_PATH }}<br>    releaseNotes: ${{ env.COMMIT_MESSAGE }}</pre><p>GitHub Secrets securely store sensitive data such as API keys and passwords in your repository settings under “Secrets.” These secrets can be used in workflow files and are encrypted by GitHub, ensuring a secure development and production transition.</p><p>This explanation covers the essentials of setting up GitHub Actions for Android development, focusing on continuous integration and deployment, automating the process from code merge to deployment.</p><p>For example <a href="https://gist.github.com/UtkuGlsvn/b5438ca5174cdc85e042464a98bbacc6">github action</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/226c3e50f7cbb338f7e2d6ece6adcc5f/href">https://medium.com/media/226c3e50f7cbb338f7e2d6ece6adcc5f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4b3f0474529" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Geliştirme de Github Action Bakış]]></title>
            <link>https://utkuglsvn.medium.com/android-geli%C5%9Ftirme-de-github-action-bak%C4%B1%C5%9F-abb6ff657956?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/abb6ff657956</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[android-cicd]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Fri, 27 Dec 2024 20:54:57 GMT</pubDate>
            <atom:updated>2024-12-27T20:59:20.735Z</atom:updated>
            <content:encoded><![CDATA[<p>GitHub Actions, Android projeleri için otomasyon süreçlerini kolaylaştırarak kod kalitesini tutarlı kılar ve dağıtım işlemlerini verimli hale getirir. Bu, GitHub depolarınıza entegre edilmiş bir araçtır ve Android projeniz için iş akışlarını doğrudan GitHub üzerinden yönetmenize olanak tanır. Kendi projelerimde kullandığım develop ve master pull requelstlerini mergelendikten sonra otomatik bir şekilde apk çıkartıp firebase app distrubation yükleyen bir yaml den anlatacağım. Github action ile projeniz sürekli entegrasyon ve dağıtım (CI/CD) gereksinimlerini karşılamasına olanak sağlar.</p><ol><li><strong>Workflow Dosyası Oluşturma</strong>: .github/workflows dizinini projenizde oluşturun ve içine android.yml gibi bir YAML dosyası yerleştirerek iş akışınızı tanımlayın.</li><li><strong>Tetikleyicileri Belirleme</strong>: İş akışının ne zaman tetikleneceğini belirtin, örneğin belirli dallara push veya pull request yapıldığında.</li></ol><pre>on:<br>  push:<br>    branches:<br>      - development<br>      - master<br><br>  pull_request:<br>    branches:<br>      - feature/*<br>      - bugfix/*</pre><p>3. <strong>Ortam Kurulumu:</strong> Gradle — Android geliştirme ile uyumlu bir ortam ayarlayın .</p><pre>- uses: actions/setup-java@v3<br>  with:<br>    distribution: &#39;temurin&#39;<br>    java-version: &#39;17&#39;<br><br>- name: Cache Gradle dependencies<br>  uses: actions/cache@v3<br>  with:<br>    path: |<br>      ~/.gradle/caches<br>      ~/.gradle/wrapper<br>    key: ${{ runner.os }}-gradle-${{ hashFiles(&#39;**/*.gradle*&#39;, &#39;**/gradle-wrapper.properties&#39;) }}</pre><p>4. <strong>Derleme ve Çıktılarının Kontrolü:</strong></p><pre>- name: Build the project (assembleProdDebug)<br>  run: ./gradlew assembleProdDebug<br>- name: List build outputs<br>  run: ls -alh app/build/outputs/apk/prod/debug/</pre><p><strong>5. Firebase APK’e Yüklenmesi:</strong></p><pre>- name: Upload APK to Firebase App Distribution<br>  uses: wzieba/Firebase-Distribution-Github-Action@v1<br>  with:<br>    appId: ${{ env.FIREBASE_APP_ID }}<br>    file: ${{ env.APK_PATH }}<br>    releaseNotes: ${{ env.COMMIT_MESSAGE }}</pre><p>GitHub Secrets, GitHub repositorilerinde hassas verileri güvenli bir şekilde saklamanıza olanak tanır. Bunlar, API anahtarları, parolalar veya belirleme bilgileri gibi gizli bilgileri içerebilir. GitHub Actions iş akışlarınızda kullanabileceğiniz bu bilgiler, repository ayarları altında “Secrets” bölümünde tanımlanır. Secrets, iş akışı dosyalarında değişkenler olarak kullanılabilir ve GitHub tarafından şifrelenir. Bu sayede, kodunuzun güvenliği artırılırken, geliştirme ve üretim ortamları arasında kolay geçiş yapılmasına imkan tanınır.</p><p>Firebase app distrubation tamamına <a href="https://gist.github.com/UtkuGlsvn/b5438ca5174cdc85e042464a98bbacc6">buradan ulaşabilirsiniz</a> -&gt;</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/226c3e50f7cbb338f7e2d6ece6adcc5f/href">https://medium.com/media/226c3e50f7cbb338f7e2d6ece6adcc5f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abb6ff657956" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jetpack Compose Ve Xml Karşılaştırması]]></title>
            <link>https://utkuglsvn.medium.com/jetpack-compose-ve-xml-kar%C5%9F%C4%B1la%C5%9Ft%C4%B1rmas%C4%B1-ba68bb32aa1b?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba68bb32aa1b</guid>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[compose]]></category>
            <category><![CDATA[jetpack-compose-vs-xml]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sun, 05 May 2024 12:01:17 GMT</pubDate>
            <atom:updated>2024-05-05T12:01:17.375Z</atom:updated>
            <content:encoded><![CDATA[<p>Jetpack Compose ve XML tabanlı UI yaklaşımları, Android uygulamalarının kullanıcı arayüzlerini geliştirme konusunda iki farklı metodolojidir. Her birinin kendine özgü avantajları ve dezavantajları bulunmaktadır. Bu iki yöntemi karşılaştıran bir makale yazarak bu iki popüler UI geliştirme yaklaşımını detaylı bir şekilde inceleyelim.</p><h3>Jetpack Compose</h3><p>Jetpack Compose, modern Android uygulamaları için geliştirilmiş bir UI kitidir. Declarative bir yaklaşım kullanır, yani UI’nizi Kotlin koduyla tanımlarsınız ve UI bileşenleri state değişikliklerine otomatik olarak yanıt verir. Bu, UI kodunuzu daha modüler ve okunabilir hale getirir. Ayrıca fonksiyonlar da ilk harfin büyük olmasının nedeni, fonksiyonun view set eden bir komponent olduğunu temsil ediyor.</p><p>Avantajları:</p><ul><li>Declarative Yaklaşım: UI bileşenlerinizin nasıl görünmesi gerektiğini açıklarsınız, bu da kodun okunabilirliğini ve bakımını kolaylaştırır.</li><li>Daha Az Boilerplate Kod: XML yerine Kotlin kullanarak UI bileşenlerini doğrudan tanımlayabilirsiniz, böylece gereksiz kod miktarını azaltır.</li><li>Entegre Animasyon ve Geçişler: Compose, animasyonlar ve UI geçişleri için yerleşik destek sağlar, bu da daha zengin kullanıcı deneyimleri yaratmayı kolaylaştırır.</li></ul><p>Dezavantajları:</p><ul><li>Yeni ve Sürekli Gelişen: Compose henüz yeni ve sürekli olarak geliştirilmekte olan bir teknolojidir, bu da bazı özelliklerin eksik olabileceği veya hataların bulunabileceği anlamına gelir.</li><li>Öğrenme Eğrisi: XML ve View-based UI’den farklı bir paradigma olduğu için, özellikle eski yaklaşımlara alışkın geliştiriciler için öğrenme eğrisi zorlayıcı olabilir.</li></ul><h3>XML UI</h3><p>XML, Android’in en başından beri kullanılan, layout dosyalarını tanımlamak için kullanılan işaretleme dilidir. Imperative bir yaklaşım kullanır, yani UI’nin her bir bileşenini ve onların davranışlarını açıkça belirtirsiniz.</p><p>Avantajları:</p><ul><li>Olgun ve Geniş Çapta Kabul Görüş: XML tabanlı UI yaklaşımı, yıllar içinde geliştirilmiş ve pek çok projede test edilmiştir.</li><li>Detaylı Dokümantasyon ve Topluluk Desteği: Geniş bir topluluk ve kapsamlı dokümantasyon sayesinde sorunlara çözüm bulmak genellikle daha kolaydır.</li><li>Araç Desteği: Android Studio, XML layoutları için kapsamlı bir tasarım editörü ve araç seti sunar.</li></ul><p>Dezavantajları:</p><ul><li>Boilerplate Kod: UI bileşenlerini tanımlamak için genellikle çok sayıda tekrar eden kod yazmanız gerekebilir.</li><li>Yavaş Yeniden Derlemeler: UI değişiklikleri için genellikle uygulamanın yeniden derlenmesi gerektiğinden, geliştirme süreci yavaşlayabilir.</li></ul><h3>Temel Bileşenler</h3><p>Jetpack Compose’da birkaç temel bileşen bulunmaktadır. Text, Image, Button ve LazyColumn gibi sıklıkla kullanılan bileşenlere bakalım:</p><h4>Text Bileşeni</h4><p>Text bileşeni, ekranda metin göstermenizi sağlar. Font büyüklüğü, renk, stil ve daha fazlasını özelleştirebilirsiniz.</p><pre>@Composable<br>fun XmlToTextview() {<br> Text(<br> text = “Hello World”,<br> fontSize = 18.sp,<br> color = Color.Blue,<br> fontFamily = FontFamily.Serif,<br> fontWeight = FontWeight.Bold,<br> fontStyle = FontStyle.Italic<br> )<br>}</pre><h4>Image Bileşeni</h4><p>Image bileşeni ile uygulamanıza resim ekleyebilirsiniz. Resimleri çeşitli şekillerde kırpabilir ve renk filtreleri uygulayabilirsiniz.</p><pre>@Composable<br>fun XmlToImageView() {<br> Image(<br> painter = painterResource(id = R.drawable.ic_launcher_foreground),<br> contentDescription = null,<br> modifier = Modifier<br> .size(50.dp)<br> .clip(CircleShape),<br> colorFilter = ColorFilter.tint(Color.Red)<br> )<br>}</pre><h4>Button Bileşeni</h4><p>Button bileşeni, tıklanabilir düğmeler oluşturmanıza olanak tanır. Tıklama işlevselliğini Kotlin lambda ifadeleri ile tanımlayabilirsiniz.</p><pre>@Composable<br>fun XmlToButton(name: String, context: Context = LocalContext.current) {<br>    Button(onClick = {<br>        Toast.makeText(context, &quot;Hello, $name!&quot;, Toast.LENGTH_SHORT).show()<br>    }) {<br>        Text(&quot;Click Me&quot;)<br>    }<br>}</pre><h4>LazyColumn ve LazyVerticalGrid</h4><p>LazyColumn ve LazyVerticalGrid, liste ve ızgara görünümlerini oluşturmak için kullanılır.</p><pre>@Composable<br>fun XmlToGridView() {<br>    LazyVerticalGrid(<br>        columns = GridCells.Fixed(2),<br>        contentPadding = PaddingValues(10.dp),<br>        content = {<br>            items(4) { index -&gt;<br>                Text(&quot;Item ${index + 1}&quot;)<br>            }<br>        }<br>    )<br>}</pre><p>Daha fazla örnek için github projesine bakabilirsiniz: <a href="https://github.com/UtkuGlsvn/XmlViewToComposeView/blob/master/app/src/main/java/com/utkuglsvn/xmlviewtocomposeview/MainActivity.kt">https://github.com/UtkuGlsvn/XmlViewToComposeView/blob/master/app/src/main/java/com/utkuglsvn/xmlviewtocomposeview/MainActivity.kt</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba68bb32aa1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Jetpack Compose- 2]]></title>
            <link>https://utkuglsvn.medium.com/android-jetpack-compose-2-5c2f735538ec?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c2f735538ec</guid>
            <category><![CDATA[compose]]></category>
            <category><![CDATA[compose-sideeffect]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[side-effects]]></category>
            <category><![CDATA[jetpack-compose]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Wed, 11 Oct 2023 06:54:03 GMT</pubDate>
            <atom:updated>2023-10-11T06:54:03.714Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@utkuglsvn/android-jetpack-compose-1-30ee89a996d7">İlk yazıyla jetpack compsose nedir, lifecycle, stateless, stateful akışlarını incelemiştik</a>. Bu seride side effect konusuna bakacağız.</p><p><strong>Side Effect Nedir</strong></p><p>Jetpack Compose’da “side effect”ler, composable dışındaki durumu değiştirmek için kullanılır. Bu nedenle, Jetpack Compose&#39;da side effect&#39;ler, bir Composable&#39;in yaşam döngüsü içinde dış durumu değiştirmek, kaynakları yönetmek ve genel olarak dış etkileşimde bulunmak için kullanılır.</p><p>Örneğin, bir Composable’in bir kaynağı (örneğin bir listener veya bir coroutine) ayırması ve bu kaynağı daha sonra serbest bırakması gerekebilir. Ya da bir Composable, dış bir durumu (state) değiştirebilir veya bir coroutine başlatabilir. Bu tür etkileşimler ve kaynak yönetimi için Jetpack Compose, LaunchedEffect, DisposableEffect, produceState gibi side effectler sunar.</p><h3>Avantajlar:</h3><ol><li>Yaşam Döngüsüne Bağlılık: Jetpack Compose’da side effect’ler, Composable’in yaşam döngüsüne otomatik olarak bağlıdır. Bu, kaynakların (örneğin listener’lar, coroutines) otomatik olarak yönetilmesini sağlar.</li><li>Deklaratif Yaklaşım: Side effect’ler, Composable fonksiyonların saf (pure) kalmasına yardımcı olur ve böylece UI kodunu deklaratif tutar. Bu, kodun daha okunabilir ve anlaşılır olmasını sağlar.</li><li>Optimize Edilmiş Güncellemeler: Bazı side effect’ler, sadece gerçekten gerekli olduğunda güncellemelerin yapılmasını sağlar. Örneğin, produceState composable&#39;ı, asenkron veri yüklemesi yaparken state&#39;in sadece gerekli olduğunda güncellenmesine yardımcı olabilir.</li><li>Entegre Kaynak Yönetimi: DisposableEffect gibi side effect&#39;ler, kaynakların ayırılması ve serbest bırakılması arasında otomatik bir köprü oluşturarak kaynak yönetimini basit ve hatasız hale getirir.</li></ol><ul><li>Side effectlerin yanlış kullanılması sonucu gereksiz bellek tüketimine neden olabilir. (Memory Leak)</li></ul><h4><strong><em>Side Effect</em></strong></h4><ul><li>Kullanım Amacı: Composable’in her re-composition sırasında sadece bir kez çalıştırılacak işlemler için kullanılır.</li></ul><p>Kullanım Yerleri:</p><ul><li>Bir günlük mesajı yazdırmak</li><li>Bir analitik olayını kaydetmek</li><li>Bir harici durumu güncellemek</li></ul><pre>@Composable<br>fun LogEffect() {<br>    val count = remember { mutableStateOf(0) }<br><br>    SideEffect {<br>        Log.d(&quot;LogEffect&quot;, &quot;Count value: ${count.value}&quot;)<br>    }<br><br>    Button(onClick = { count.value++ }) {<br>        Text(&quot;Increment Count&quot;)<br>    }<br>}</pre><h4><strong><em>Launched Effect</em></strong></h4><p>Kullanım Amacı: Asenkron işlemleri, özellikle coroutines ile yapılan işlemleri yönetmek için kullanılır. (Network, room …)</p><p>Kullanım Yerleri:</p><ul><li>Bir ağ isteği göndermek ve yanıtı UI’ya yansıtmak</li><li>Bir veritabanını güncellemek ve değişiklikleri UI’ya yansıtmak</li><li>Bir günlük mesajı yazdırmak</li><li>Bir analitik olayını kaydetmek</li></ul><pre>@Composable<br>fun FetchData() {<br>    val data = remember { mutableStateOf&lt;String?&gt;(null) }<br><br>    LaunchedEffect(Unit) {<br>        data.value = fetchDataFromAPI() // asenkron bir API çağrısı<br>    }<br><br>    Text(text = data.value ?: &quot;Loading...&quot;)<br>}</pre><h3>Disposable Effect</h3><p>Kullanım Amacı: Kaynakların ayırılması ve serbest bırakılması için kullanılır. Özellikle listener’ların kaydedilmesi ve kaldırılması gibi işlemlerde kullanılır.</p><p>Kullanım Yerleri:</p><ul><li>Bir sunucuya bağlantı kurmak ve bağlantıyı kapatmak</li><li>Bir ses dosyası oynatmak ve dosyayı durdurmak</li><li>Bir animasyon çalıştırmak ve animasyonu durdurma</li></ul><pre>@Composable<br>fun SensorListener() {<br>    val context = LocalContext.current<br>    val sensorManager = context.getSystemService(Context.SENSOR_SERVICE) as SensorManager?<br>    val listener = SensorEventListener { /* işlemler... */ }<br><br>    DisposableEffect(sensorManager) {<br>        sensorManager?.registerListener(listener, /* diğer parametreler... */)<br><br>        onDispose {<br>            sensorManager?.unregisterListener(listener)<br>        }<br>    }<br>}</pre><h3>ProduceState</h3><p>Kullanım Amacı: Asenkron veri yüklemesi yaparken, composable durumunu (state) güncellemek için kullanılır.</p><p>Kullanım Yerleri:</p><ul><li>Bir ağ isteği gönderdikten sonra gelen verileri tutmak</li><li>Bir kullanıcının girişini işlemek ve giriş verilerini tutmak</li></ul><pre>@Composable<br>fun DisplayDataFromAPI() {<br>    val data by produceState(initialValue = null) {<br>        value = fetchDataFromAPI() // asenkron bir API çağrısı<br>    }<br><br>    Text(text = data ?: &quot;Loading...&quot;) // data geldiğinde texti günceller<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLCit-RtYHmKchG1X3CTGw.png" /><figcaption>Bard</figcaption></figure><p><strong><em>Referanslar:</em></strong></p><ul><li><a href="https://medium.com/@mortitech/exploring-side-effects-in-compose-f2e8a8da946b">https://medium.com/@mortitech/exploring-side-effects-in-compose-f2e8a8da946b</a></li><li><a href="https://developer.android.com/jetpack/compose/side-effects">https://developer.android.com/jetpack/compose/side-effects</a></li></ul><p><strong><em>Jetpack Compose Devam Serisi :</em></strong></p><ol><li>Part : <a href="https://utkuglsvn.medium.com/android-jetpack-compose-1-30ee89a996d7">https://utkuglsvn.medium.com/android-jetpack-compose-1-30ee89a996d7</a></li></ol><p>…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c2f735538ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Work Manager 101]]></title>
            <link>https://utkuglsvn.medium.com/work-manager-101-187a227e6a8?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/187a227e6a8</guid>
            <category><![CDATA[kotlinworkmananger]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[workmanager]]></category>
            <category><![CDATA[android-workmanager]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sun, 24 Sep 2023 19:02:58 GMT</pubDate>
            <atom:updated>2023-09-24T19:02:58.715Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>What is work manager</strong></h3><p>Workmanager is a part of Android Jetpack and is designed to run background tasks efficiently, taking into account various constraints such as network availability, charging status, etc.</p><ul><li><strong>Scheduling:</strong> WorkManager allows you to schedule tasks to run at a specific time, periodically, or on demand.</li><li><strong>Chaining:</strong> WorkManager allows you to chain tasks together, so that one task triggers another.</li><li><strong>Constraints:</strong> WorkManager allows you to specify constraints for when tasks should run, such as network connectivity or battery level.</li><li><strong>Retrying:</strong> WorkManager can automatically retry tasks that fail.</li><li><strong>Cancellation:</strong> WorkManager allows you to cancel tasks that are in progress.</li></ul><h3>Types of persistent work</h3><p>WorkManager handles three types of persistent work:</p><ul><li><strong>Immediate</strong>: Tasks that must begin immediately and complete soon. May be expedited.</li><li><strong>Long Running</strong>: Tasks which might run for longer, potentially longer than 10 minutes.</li><li><strong>Deferrable</strong>: Scheduled tasks that start at a later time and can run periodically.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JsLKlwO4eGih2OeNjI-oA.png" /><figcaption><a href="https://developer.android.com/topic/libraries/architecture/workmanager">https://developer.android.com/topic/libraries/architecture/workmanager</a></figcaption></figure><h3>Benefits:</h3><ul><li><strong>Backward Compatibility:</strong> It works all the way back to API level 14 while integrating with the OS’s job scheduling system.</li><li><strong>Constraints Handling:</strong> Allows setting constraints like network type, battery charging status, storage space, etc.</li><li><strong>Flexibility:</strong> WorkManager allows you to schedule tasks to run at a specific time, periodically, or on demand. You can also chain tasks together, so that one task triggers another.</li><li><strong>Task Chaining:</strong> Enables you to list tasks in a sequence, where one runs after the other or in parallel.</li><li><strong>Reliability:</strong> WorkManager ensures that background tasks are executed, even if the device is restarted or the app is in the background.</li><li><strong>Efficiency:</strong> WorkManager uses system APIs to optimize the execution of background tasks. This helps to improve battery life and performance.</li></ul><p>Here are some examples of how WorkManager can be used to improve your app:</p><ul><li>Schedule tasks to run at specific times: For example, you could use WorkManager to schedule a task to run every day to sync data with a server.</li><li>Run tasks periodically: For example, you could use WorkManager to schedule a task to run every hour to check for updates to a database.</li><li>Chain tasks together: For example, you could use WorkManager to chain together a task to download a file and a task to process the file.</li></ul><p><strong>Setup workmanager project</strong></p><ul><li>Add to workmanager gradle</li></ul><pre>implementation (&quot;androidx.work:work-runtime:2.8.1&quot;) // Check for the latest version</pre><ul><li>Create a worker class</li></ul><pre>class MyWorker(context: Context, workerParams: WorkerParameters) : Worker(context, workerParams) {<br> override fun doWork(): Result { // Your task here return Result.success() } <br>}</pre><ul><li>Setting Constraints:</li></ul><pre>val constraints = Constraints.Builder()<br>    .setRequiredNetworkType(NetworkType.CONNECTED)<br>    .setRequiresCharging(true)<br>    .build()</pre><ul><li>Creating a WorkRequest:</li></ul><pre>val myWorkRequest = OneOffWorkRequestBuilder&lt;MyWorker&gt;()<br>    .setConstraints(constraints)<br>    .build()<br>//work in period time<br>val myWorkRequest = PeriodicWorkRequestBuilder&lt;SimpleWorker&gt;<br>(15, TimeUnit.MINUTES).build()<br><br>//chain work manager<br><br>// Create the first WorkRequest object.<br>val firstWorkRequest = PeriodicWorkRequestBuilder&lt;SimpleWorker&gt;<br>(15, TimeUnit.MINUTES)<br><br>// Create the second WorkRequest object.<br>val secondWorkRequest = OneTimeWorkRequest.Builder(MySecondWorker::class.java)<br>    .addTrigger(WorkTrigger.Builder().addDependency(firstWorkRequest).build())<br>    .build()<br><br>// Submit the WorkRequest objects to WorkManager.<br>WorkManager.getInstance().enqueue(firstWorkRequest)<br>WorkManager.getInstance().enqueue(secondWorkRequest)</pre><ul><li>Enqueue the Work:</li></ul><pre>WorkManager.getInstance(context).enqueue(myWorkRequest)</pre><p>Example Github Project: <a href="https://github.com/UtkuGlsvn/WorkManagerTutorial">https://github.com/UtkuGlsvn/WorkManagerTutorial</a></p><p>References: <a href="https://developer.android.com/topic/libraries/architecture/workmanager">https://developer.android.com/topic/libraries/architecture/workmanager</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=187a227e6a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Palette API. How to use Palette API]]></title>
            <link>https://utkuglsvn.medium.com/what-is-palette-api-how-to-use-palette-api-1e594e371bb7?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e594e371bb7</guid>
            <category><![CDATA[android-color]]></category>
            <category><![CDATA[kotlin-palette]]></category>
            <category><![CDATA[palette]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-palette]]></category>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Sun, 10 Sep 2023 16:04:16 GMT</pubDate>
            <atom:updated>2023-09-10T16:04:16.718Z</atom:updated>
            <content:encoded><![CDATA[<p>Colors play a pivotal role in the realm of digital design. A single hue can radically alter the character of your brand, influence user experiences, and dictate the overall feel of your product.</p><h3>What is Palette Api</h3><p>The Palette API is part of the AndroidX library, allowing developers to pull specific colors from any image, thereby providing a way to use these colors for UI elements dynamically. This ensures better visual integration between your images and UI components.</p><h3>Setup Palette Api</h3><p>Firstly, ensure you have the required dependency in your build.gradle:</p><pre>android {<br>    compileSdkVersion(33)<br>    ...<br>}<br><br>dependencies {<br>    ...<br>    //implementation(&quot;com.android.support:palette-v7:28.0.0&quot;)<br>    implementation(&quot;androidx.palette:palette-ktx:1.0.0&quot;)<br>}</pre><h3>Create a Palette</h3><p>A Palette object allows you to access the colors in an image, as well as their corresponding colors for overlaid text.</p><pre>val myBitmap = BitmapFactory.decodeResource(resources, R.drawable.your_image)<br>val palette = Palette.from(myBitmap).generate()</pre><h3>Extracting Colors</h3><p>To extract colors from an image, follow these steps:</p><pre>val vibrantColor = palette.vibrantColor<br>val mutedColor = palette.mutedColor<br>...</pre><p>These colors are categorized into predefined profiles based on their luminance and saturation characteristics. Each of these profiles aims to help developers achieve a harmonious and aesthetically pleasing color scheme for their apps by matching UI elements with the prominent colors of displayed images.</p><ul><li>Vibrant: This profile extracts a color that is vibrant and eye-catching. It typically represents the most dominant, rich, and prominent color in an image.</li><li>Light Vibrant:As the name suggests, this profile provides a lighter, more pastel variant of the vibrant color. It’s often suitable for backgrounds where you want a softer, more subtle vibrant hue.</li><li>Dark Vibrant: This is the darker variant of the vibrant color. It can be effectively used for text or UI elements that need to stand out against lighter backgrounds.</li><li>Muted: This profile gives colors that are muted or less saturated. Such colors are typically subdued and can be used where you want less attention drawn, offering a neutral backdrop for other UI components.</li><li>Light Muted:A lighter, more pastel version of the muted color. It works well for backgrounds where you prefer a gentle, unobtrusive look.</li><li>Dark Muted: This is the deeper variant of the muted color. It’s often suitable for text or other UI elements you wish to make prominent without the loudness of a vibrant color.</li></ul><h3>Other Properties Palette API</h3><ul><li>rgb: The RGB color of the swatch.</li><li>bodyTextColor : A suitable color for text (for example, for labels).</li><li>titleTextColor: A suitable color for text on top of the rgb background (for headers).</li></ul><pre>palette.vibrantSwatch?.let {<br>    Log.i(&quot;rgb color&quot;,&quot;${it.rgb}&quot;)<br>    Log.i(&quot;title text color&quot;,&quot;${it.titleTextColor}&quot;)<br>    Log.i(&quot;body text color&quot;,&quot;${it.bodyTextColor}&quot;)<br>}</pre><p>Example project: <a href="https://github.com/UtkuGlsvn/PaletteApiAndroidTutorial">https://github.com/UtkuGlsvn/PaletteApiAndroidTutorial</a></p><p>Resource: <a href="https://developer.android.com/develop/ui/views/graphics/palette-colors#kts">https://developer.android.com/develop/ui/views/graphics/palette-colors#kts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e594e371bb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deneme 2 — Karanlıkta Kaybolmak]]></title>
            <link>https://utkuglsvn.medium.com/deneme-2-karanl%C4%B1kta-kaybolmak-a1b628f8994a?source=rss-ca23c9f3bc77------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b628f8994a</guid>
            <dc:creator><![CDATA[Utku Glsvn]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 21:03:21 GMT</pubDate>
            <atom:updated>2023-08-16T21:03:21.374Z</atom:updated>
            <content:encoded><![CDATA[<h3>Deneme 2 — Karanlıkta Kaybolmak</h3><p>Umut arıyorum bu karanlık dünyada, sadece var olabilmek ve varlığımı kabul edebilmek için. Kendi karanlığım kaybolmadan önce verdiğim sözleri tutmak istiyorum. Kendimi bulmak için karanlığa girerken, bir taraftan işlerimi yapabilmek bazen zor oluyor. Karanlık daha kuvvetli geliyor ve karanlıkta kayboluyorum.</p><p>Arkamı dönüp baktığımda, hep aynı sorularla karşı karşıya geliyorum. Küçük yaşta karanlıkta kayboldum, hala aydınlığa bulamadım. Bazen dans edeni, çalışanı, yaşayanı anlamıyorum. Ölümden öte bir şey yokken, bunları yapıyormuş gibi yapmaya çabalamak neye hizmet ediyor.</p><p>Kelimelerin arasında kendimi tutsak hissediyorum. Bedenimin sınırları içinde sıkışmış ruhum özgürlüğe gitmek istiyor. Sadece o vakti bekliyor, zamanı geldiğinde tüm sorunlarım ve çaresizliklerim çözülecek. Belki bir veda mektubu olur, belki bir yok oluş mektubu. Ama karanlıktan çıkmadan gitmek istemiyorum. Ölüme koşmak ne kadar mantıklı ki, elbet gelecek zaten.</p><p>Yazarken mi kafam güzel oluyor, yoksa karanlıkta kaybolduğumdan mı bilmiyorum. Kendimi bulmak için bir yolculuğa çıkıyorum. Umarım karanlığın içinde daha fazla kaybolmam. Bazen çok yorucu oluyor ve bunları konuşmak her zaman mümkün olmuyor. Kendi kendime konuşup anlam aramak için daha ne kadar gitmem gerektiğini de bilmiyorum. Ama asla diğerleri gibi yaşayamayacağımı biliyorum. Nietzsche dediği gibi, azınlıkların azlarıyız.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b628f8994a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>