<?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 Dmytro Virych on Medium]]></title>
        <description><![CDATA[Stories by Dmytro Virych on Medium]]></description>
        <link>https://medium.com/@damienissa?source=rss-32796b66bdaf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zqIBTxf7tAVkcDZ6WgF_Ew.jpeg</url>
            <title>Stories by Dmytro Virych on Medium</title>
            <link>https://medium.com/@damienissa?source=rss-32796b66bdaf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:18:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damienissa/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 Mac Screen Sharing Alternative That Shares One Window, Not the Whole Screen]]></title>
            <link>https://medium.com/@damienissa/a-mac-screen-sharing-alternative-that-shares-one-window-not-the-whole-screen-de2cd11b1cd6?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/de2cd11b1cd6</guid>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[remote-access]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 19:20:51 GMT</pubDate>
            <atom:updated>2026-11-12T19:20:51.595Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to remote access a Mac mini from your MacBook and use its apps as if they were installed here</h3><figure><img alt="Mac screen sharing alternative showing a Mac mini’s Xcode window on a MacBook, next to local apps" src="https://cdn-images-1.medium.com/max/1024/1*4V8-_l0W8Mfn9P-0p9Lk0A.jpeg" /></figure><p>Looking for a Mac Screen Sharing alternative? macOS Screen Sharing shows another Mac’s <em>entire screen</em> inside one window. Wormhole takes a different approach: it opens a <em>single app window</em> from your other Mac (a Mac mini, a Mac Studio, an old MacBook) as a real window on the Mac in front of you, with its own Dock icon and ⌘Tab entry. When you need the whole screen, that’s one click away too.</p><p>I’m the developer, and I built it because Screen Sharing kept giving me the whole Mac when all I wanted was one app. Below: how the two compare, when to use each, and how to set it up.</p><h3>What’s wrong with Mac Screen Sharing?</h3><p>Nothing — it just answers a different question.</p><p>I have a MacBook I carry around and a Mac mini on a shelf that does the heavy lifting: long builds, the big project, the simulator that eats 12 GB of RAM. To reach the mini, I used Screen Sharing, the app built into every Mac.</p><p>Every day it made me do the same dance. I needed Xcode’s build log, and I got <em>the entire mini</em>: its desktop, Dock, menu bar and wallpaper, squeezed into one window on my laptop. Switch in, find Xcode inside a smaller copy of another Mac, squint, switch back. Forty times a day.</p><p>Screen Sharing answers <em>“Can I see and control that Mac?”</em> What I wanted to ask was <em>“Can I use that app here, as if it were installed here?”</em></p><h3>Screen sharing vs. window sharing on a Mac</h3><ul><li>Screen sharing gives you one big picture. Everything on the other Mac lives inside a single window of the Screen Sharing app: one Dock icon, one ⌘Tab entry, one thing to resize.</li><li>Window sharing gives you individual windows your Mac already knows how to handle. Put one next to your editor, ⌘Tab to it, give it half the display, and forget it isn’t local.</li></ul><h3>Wormhole vs. macOS Screen Sharing at a glance</h3><p>What you see → Wormhole: one window from the other Mac, as its own window here (or the whole screen, from the same picker) → Screen Sharing: the other Mac’s whole screen</p><p>Several remote apps at once → Wormhole: yes, each in its own window → Screen Sharing: one screen per connection</p><p>Dock icon and ⌘Tab → Wormhole: each remote window has its own → Screen Sharing: one for the Screen Sharing app</p><p>Password managers → Wormhole: never offered, even in whole-screen mode → Screen Sharing: whatever is on the screen is shown</p><p>Install → Wormhole: a download, on both Macs → Screen Sharing: built into macOS (Applications › Utilities)</p><p>Pairing → Wormhole: once, with a six-digit code shown on both screens → Screen Sharing: a user name and password</p><p>Cost → Wormhole: free for one window at a time; one-time license for more → Screen Sharing: free</p><p><em>(Screen Sharing facts are from Apple’s Mac User Guide, “Share the screen of another Mac”.)</em></p><h3>How to use a Mac mini’s apps from your MacBook</h3><ol><li>Install Wormhole on both Macs from <a href="https://wormhole.buildmac.app/">wormhole.buildmac.app</a>.</li><li>Pair them once. Each Mac shows a six-digit code; confirm it matches on both screens.</li><li>On the Mac that shares (the Mac mini), turn on Screen Recording and Accessibility when macOS asks. Accessibility is what lets your clicks and typing reach its windows.</li><li>On your MacBook, press ⌃⌥⌘Space, type an app’s name, and press Return. Its window opens here.</li></ol><p>That’s it. If the app isn’t running on the mini, search for it anyway: Wormhole launches it over there and opens its first window here. The full walkthrough is in the <a href="https://wormhole.buildmac.app/setup">setup guide</a>.</p><p><em>[GIF: picker → typing “Xcode” → the window springs onto the MacBook]</em> <em>Alt text: Opening a Mac mini app window on a MacBook with Wormhole’s window picker</em></p><h3>What a remote window can do</h3><ul><li>Sharp on Retina, at your display’s full resolution, not a scaled-down slice of someone else’s desktop.</li><li>Click, type, scroll and use shortcuts. Resizing your copy resizes the real window.</li><li>Its own Dock icon and ⌘Tab entry, ringed in the other Mac’s colour so you always know where it lives.</li><li>Copy and paste between Macs: text, images and files. Drop a file on a remote window to send it across.</li><li>Several windows at once, each its own window.</li><li>Type in your language. Since version 1.4.0, Chinese, Japanese and Korean compose with the input method of the Mac you’re sitting at.</li></ul><h3>Is it secure to remote access a Mac this way?</h3><p>This was the part I cared about most.</p><ul><li>Secrets are never offered. The sharing Mac filters its own window list before it leaves the machine: password managers, hidden windows and untitled windows never appear, and a viewer can’t request a window it was never told about.</li><li>Direct, Mac to Mac. No account, and no relay server in the middle.</li><li>End-to-end encrypted. Every frame after pairing is sealed with AES-GCM. Someone on your network sees packet sizes and timings, never a pixel or a keystroke.</li></ul><h3>Can you access a Mac mini remotely from outside your home network?</h3><p>Yes. Add the other Mac by IP address or hostname — over Tailscale, for example — and windows you opened at home reconnect when you take your laptop elsewhere. On the same network, Macs find each other automatically.</p><p>It also takes care of the things that make you stop trusting a remote tool: it reconnects on its own after sleep or a Wi-Fi drop, reopens your windows after a restart, and keeps the sharing Mac awake and unlocked while sharing is on.</p><h3>Does it work with a headless Mac mini?</h3><p>Honest answer: I haven’t tested it on a truly headless Mac mini yet. With no display plugged in, macOS can have nothing to draw windows on — which affects every screen sharing tool, not just this one. The usual fix is an inexpensive HDMI dummy plug. Wormhole detects the situation and tells you so, instead of showing an empty list.</p><h3>When Mac Screen Sharing is the better choice</h3><p>I still keep Screen Sharing around. Use it when:</p><ul><li>You need the whole machine: System Settings, the login window, a Mac still at its setup screen.</li><li>You’re helping someone on a Mac you’ve never set anything up on. Screen Sharing needs nothing installed; Wormhole must be on both Macs.</li><li>You want zero cost and zero installs.</li></ul><p>Wormhole is for the other case: a Mac you own that keeps work running, from which you need <em>one app</em> next to everything on the Mac in front of you.</p><h3>Known limitations</h3><ul><li>Clicking a remote window brings it to the front on the other Mac — a click can only reach the frontmost window. Nobody notices on an unattended Mac mini; someone using that Mac will see their window order change.</li><li>Without Accessibility permission, shared windows are view-only.</li><li>Copy, paste and drop carry files but not folders, and nothing over 20 MB at once.</li></ul><p>Everything that doesn’t work yet, or works differently on purpose, is on the public <a href="https://wormhole.buildmac.app/known-issues">known issues page</a>.</p><h3>And two things just for fun</h3><p>Windows arrive on a spring, with a glow in their Mac’s colour. Fling (optional): push a window against the edge of the screen on one Mac and it opens on the other. Carry (experimental, for MacBooks): pick up your laptop and the window you were just using on your desk Mac opens on it. Both are off by default.</p><h3>FAQ</h3><p>Is there a free Mac Screen Sharing alternative? Wormhole is free for one remote window at a time, with no time limit. A one-time license (no subscription, a year of updates) opens several at once — see <a href="https://wormhole.buildmac.app/pricing">pricing</a>.</p><p>Can I share just one app window instead of my whole Mac screen? Yes. That’s what Wormhole does: it opens a single window from your other Mac as a window of its own, with its own Dock icon.</p><p>How do I control my Mac mini from my MacBook? Install Wormhole on both, pair once with a six-digit code, then press ⌃⌥⌘Space on the MacBook and pick the app. Or use macOS Screen Sharing if you need the whole desktop.</p><p>What macOS version do I need? macOS 14 Sonoma or later, on Apple silicon or Intel, on both Macs.</p><p>Does it need an account or a cloud server? No. The two Macs connect directly and every frame is end-to-end encrypted.</p><h3>Try it</h3><p>If you’ve got a Mac mini on a shelf, a Mac Studio under the desk, or an old MacBook doing a job in the corner, try it free:</p><p>👉 <a href="https://wormhole.buildmac.app/">Wormhole — remote access to your Mac, window by window</a></p><p>I’d love to hear how you use it and what it gets wrong. There’s a Feedback tab in Settings that reaches me directly.</p><p><em>I’m an independent developer building small, focused Mac apps. If this was useful, a clap or a follow helps other Mac people find it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de2cd11b1cd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get recommended by ChatGPT (with real numbers)]]></title>
            <link>https://medium.com/@damienissa/how-to-get-recommended-by-chatgpt-with-real-numbers-f95e1e922242?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f95e1e922242</guid>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 18:28:06 GMT</pubDate>
            <atom:updated>2026-10-18T18:28:06.047Z</atom:updated>
            <content:encoded><![CDATA[<p>Ask ChatGPT which tool to use for a job your product does. Then ask Perplexity. Count how many answers name you.</p><p>For most small SaaS products, the count is zero. Not because the AI dislikes you, and not because your product is worse. It’s because of <strong>where the AI gets its recommendations from</strong>, and almost nobody building a product is looking there.</p><p>We measure this every week. This post shows what one real test found, why ChatGPT recommends some products and ignores others, and the five steps that get your product into the answer. No tricks, no prompt hacks.</p><h3>The test: read 381 times, recommended 0 times</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYy_EEglBwRYUAVoyHw0UQ.png" /></figure><p>We picked a small developer tool in mobile deep linking, a category with one dominant player. We asked ChatGPT and Perplexity the questions its customers ask before they choose a tool, like <em>“What is the best deep linking tool for a Flutter app?”</em> and <em>“What are the best alternatives to Branch?”</em>. We asked each question three times, because AI answers change from run to run.</p><p>Out of 18 answers:</p><ul><li><strong>The product was named 0 times.</strong></li><li><strong>Its biggest competitor was named 15 times.</strong></li></ul><p>In the same month, the product’s own analytics showed that <strong>AI assistants opened its pages 381 times.</strong></p><p>So the AI was reading the product’s website constantly. It knew the product existed and what it did. It just never recommended it.</p><p><strong>Read 381 times. Recommended 0.</strong> AI reads you; it doesn’t recommend you. Those are two different things, and the gap between them is where small products lose customers they never knew they had.</p><h3>Why this matters now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-UvK_vDGOSUv9K_4VIwdg.png" /></figure><p><strong>1 in 2 customers now ask AI before they ask Google.</strong> This is not a niche problem. In <a href="https://company.g2.com/news/g2-research-the-answer-economy">G2’s March 2026 survey</a> of 1,076 people buying B2B software:</p><ul><li><strong>51%</strong> now start their research with an AI chatbot more often than with Google (up from 29% a year earlier).</li><li><strong>69%</strong> chose a different vendor than they planned because of what the chatbot recommended.</li></ul><p>The AI names three or four products, and most people never look further. If you’re not on that short list, you’re not in the deal.</p><h3>Why doesn’t ChatGPT recommend my product?</h3><p>When ChatGPT or Perplexity answers a question like <em>“best X for Y”</em>, it searches the web and builds the answer from a short list of pages it trusts for that question. Those are mostly:</p><ol><li><strong>“Best X tools” lists and roundups</strong>, written by blogs, media and agencies.</li><li><strong>Review and directory sites</strong> such as G2, Capterra, AlternativeTo and Product Hunt.</li><li><strong>Community threads</strong>, especially Reddit.</li><li><strong>Comparison pages</strong>: “X vs Y” and “alternatives to X”.</li><li><strong>The product’s own website</strong>, but mainly for facts (pricing, features), not for the recommendation itself.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0VR3Yf9btQznnJpxCVnlQ.png" /></figure><p><strong>AI picks names from other pages.</strong> That explains our test. The AI read the product’s site 381 times to get facts. But when it decided <em>which</em> products to recommend, it took the names from lists, review sites and comparison pages. The competitor was on those pages. The product wasn’t.</p><p>Research backs this up. <a href="https://arxiv.org/abs/2601.00912">A January 2026 study</a> of 112 Product Hunt startups found that ChatGPT <strong>recognised 99.4% of them by name</strong>, but <strong>recommended only 3.32%</strong> when asked open “best tool for…” questions (Perplexity: 8.29%). What went with being recommended: more sites linking to the product, and presence on Reddit. On-page optimisation scores had no correlation at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-AXu52A_8X_IvLwSRybEg.png" /></figure><p><strong>Known. Not recommended.</strong> In short: AI doesn’t recommend what it reads. It recommends what other pages say about you.</p><h3>How to get recommended by ChatGPT: 5 steps</h3><h3>Step 1. Find the sources AI uses for your category</h3><p>Before you change anything, find out where the answers come from.</p><ul><li>Write down 10 to 15 questions your customers actually ask before they buy: <em>“best [category] for [audience]”</em>, <em>“alternatives to [market leader]”</em>, <em>“[competitor] vs [competitor]”</em>, <em>“[category] for [specific use case]”</em>.</li><li>Ask each one in <strong>ChatGPT and Perplexity</strong>, in the real apps, logged out. Ask each question two or three times. The answers vary.</li><li>For every answer, note <strong>who was named</strong> and <strong>which pages were cited</strong>. Perplexity shows its sources by default; in ChatGPT, open the sources panel.</li></ul><p>Test in the real apps, not only through an API. The brands named in ChatGPT’s app and in its API often differ, and the app is what your customers see.</p><p>The list of cited pages is your to-do list. That is where the recommendation is decided.</p><h3>Step 2. Make your own site easy to quote</h3><p>Your site doesn’t decide the recommendation, but it decides whether the AI gets your facts right when it does mention you.</p><ul><li><strong>Say what you are in the first sentence:</strong> <em>“[Product] is a [category] for [who] that [does what].”</em> Use the words your customers use for the category, not your slogan.</li><li><strong>Put pricing on a plain, public page</strong>, readable without JavaScript and not hidden behind “Contact sales”. AI tools often fetch pages without running scripts; if your pricing loads by script, the AI sees an empty page.</li><li><strong>Publish comparison pages:</strong> <em>“[You] vs [competitor]”</em> and <em>“[competitor] alternatives”</em>. They match the exact questions people ask, and AI cites them often. Be fair to the competitor; a one-sided page reads as an ad.</li><li><strong>Answer real questions on real pages</strong>: use cases, FAQs, integrations.</li><li><strong>Check that robots.txt doesn’t block AI crawlers:</strong> GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot.</li></ul><h3>Step 3. Get on the pages AI already trusts</h3><p>This is the step that made the difference between 0 and 15 in our test, and it’s the one most founders skip.</p><ul><li><strong>Directories and review sites.</strong> List your product on G2, Capterra, AlternativeTo, Product Hunt and SaaSHub, plus the niche directories for your category. Ask a few real customers for honest reviews.</li><li><strong>The lists AI cites.</strong> From step 1 you know which “best X tools” articles appear in the answers. Write to their authors, briefly and personally, with a real reason to include you: a feature the others lack, a price point, an audience. Don’t pay for placement and don’t send templates.</li><li><strong>Reddit and communities.</strong> Answer real questions in your niche honestly, and mention your product only where it genuinely helps. Spam gets removed, and it’s the fastest way to burn trust.</li><li><strong>Guest posts and your own articles</strong> on sites AI cites in your category.</li></ul><h3>Step 4. Keep the same facts everywhere</h3><p>If your site says “free plan”, G2 says “from $29” and an old list says “$19 a month”, the AI has to choose. Usually it hedges, or leaves you out.</p><p>Use the same <strong>name, category, one-line description and pricing</strong> on your site, every directory and every profile. Update old listings when your pricing changes. It’s boring, and it’s one of the cheapest fixes there is.</p><h3>Step 5. Check every week, and be patient</h3><p>Re-ask the same questions on a schedule, ideally weekly, several runs each. Track how often you’re named, how often each competitor is named, and which pages are cited.</p><p>Set your expectations:</p><ul><li><strong>Perplexity</strong> searches the web live and usually reflects changes first.</li><li><strong>ChatGPT</strong> tends to move more slowly.</li><li>Expect first mentions in <strong>weeks to a couple of months</strong>, not overnight. Anyone who guarantees a ChatGPT recommendation is guessing.</li></ul><h3>What doesn’t work</h3><ul><li><strong>Keyword stuffing or hidden text “for AI.”</strong> There is no secret prompt, tag or file that makes ChatGPT recommend you.</li><li><strong>Fake reviews.</strong> They break the review sites’ rules and the law in most markets, and they get removed.</li><li><strong>Spamming Reddit or communities.</strong> It gets deleted, and it gets you banned from the places that matter.</li><li><strong>Only working on your own site.</strong> It helps the AI describe you correctly, but on its own it rarely gets you recommended. The test above is the proof: 381 reads, 0 recommendations.</li></ul><h3>FAQ</h3><p><strong>Can you pay to get recommended by ChatGPT?</strong> No. There’s no ad slot or submission form for ChatGPT’s recommendations. You can only make your product easier to find, check and cite on the pages it reads.</p><p><strong>How long does it take to get recommended by ChatGPT?</strong> Usually weeks to a couple of months after you appear on the pages AI cites. Perplexity often changes first; ChatGPT follows more slowly.</p><p><strong>Is this the same as SEO?</strong> It overlaps but isn’t the same. Classic SEO is about ranking your own pages in Google. Getting recommended by AI is mostly about being named on <em>other</em> pages that AI trusts.</p><p><strong>Does llms.txt help?</strong> It can help AI tools read your site, but there’s no evidence it makes ChatGPT recommend you. Treat it as a small extra, not a strategy.</p><p><strong>Should I check ChatGPT or Perplexity first?</strong> Both, but start with Perplexity: it shows its sources clearly, so it’s the fastest way to see which pages decide your category.</p><h3>The short version</h3><ol><li>Ask AI the questions your customers ask, and note which pages it cites.</li><li>Make your site say clearly what you are, with public pricing and comparison pages.</li><li>Get your product onto the lists, directories, review sites and threads AI cites.</li><li>Keep your facts identical everywhere.</li><li>Re-check weekly, and give it weeks, not days.</li></ol><p>AI doesn’t recommend what it reads. It recommends what other pages say about you. So get on the pages AI reads. Then relax.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YayBJaXyJLi60UCoICI3Tg.png" /></figure><p><em>The relaxing part is the point. I’m Dmytro, and I’m building </em><a href="https://lazygeo.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=recommended-by-chatgpt"><em>LazyGEO</em></a><em>, which does steps 1 to 5 for small SaaS teams on autopilot. If you want to see who ChatGPT and Perplexity recommend instead of you, there’s a </em><a href="https://lazygeo.com/?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=recommended-by-chatgpt#free-check"><em>free check</em></a><em>, or reply here with your product and I’ll run the questions by hand and tell you what I find.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f95e1e922242" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build and Sell a macOS App with Build Mac App]]></title>
            <link>https://medium.com/@damienissa/how-to-build-and-sell-a-macos-app-with-build-mac-app-a40669bee325?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/a40669bee325</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[macos-app-development]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 18:38:35 GMT</pubDate>
            <atom:updated>2026-09-27T18:38:35.869Z</atom:updated>
            <content:encoded><![CDATA[<h3>From an empty folder to your first sale: the app, the website, payments, licensing, and auto-updates, with an AI agent doing the grunt work</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7MdUyicXxc-CxghXohs8g.png" /><figcaption><em>Everything that ships with the template, in one picture.</em></figcaption></figure><p>I’ve shipped three paid Mac apps. Every single time, the app itself was the fun part, and it was also the small part.</p><p>The rest was plumbing. License keys. A checkout. Receipt emails. Code signing. Notarization. Building a DMG that doesn’t scare people. Auto-updates. A website that actually sells the thing. Every new app, I rebuilt the same stuff, and every time something new broke.</p><p>So after app number three, I pulled all of that out into one template: <strong>Build Mac App</strong>. This post walks through how you go from zero to a Mac app people can buy, step by step, with the real commands.</p><h3>What’s inside</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXoUDf-dbQrndVQgpFJNIg.png" /><figcaption><em>Six pieces, already wired together and tested.</em></figcaption></figure><p>Here’s what you get out of the box:</p><ul><li><strong>The Mac app.</strong> Swift 6 and SwiftUI, with a license window, Settings (open at login, updates, license, about), a real main menu, and Sparkle auto-updates. The home screen is a placeholder, and that’s where your app goes.</li><li><strong>The website.</strong> Next.js, with a landing page, pricing, FAQ, blog, changelog, and terms, privacy, and refund pages. The SEO is done right: canonical URLs, structured data, a sitemap, and llms.txt so AI search can read it too.</li><li><strong>Payments.</strong> Creem or Polar as merchant of record, so they handle sales tax and VAT, not you. You get license keys with device limits, refunds, and disputes.</li><li><strong>Emails.</strong> Receipts with the license key, lost-key recovery, refund confirmations, release notes, and a waitlist, all sent through Resend.</li><li><strong>Releases.</strong> One command builds, signs, notarizes, and packages a DMG, and publishes a signed update feed. GitHub Actions can do the same.</li><li><strong>AI tooling.</strong> 13 “skills” (step-by-step recipes) so Claude Code, Cursor, or Codex can work on the project without wrecking it, plus checks that run after every change.</li></ul><h3>What you need</h3><p>To build and run it (all free):</p><ul><li>A Mac on macOS 14 or later</li><li>Xcode 16 or later (Swift 6)</li><li>XcodeGen: brew install xcodegen</li><li>Node.js 22 or later: brew install node</li></ul><p>To actually sell it, you’ll need these later (not today):</p><ul><li>The <strong>Apple Developer Program</strong> ($99/year), for signing and notarization</li><li>A <strong>Creem</strong> or <strong>Polar</strong> account for payments</li><li>A <strong>Resend</strong> account for email</li><li>Somewhere to host the site. <strong>Vercel</strong> is the easy default</li></ul><h3>Step 1: See it all running (10 minutes)</h3><p>Before you change anything, look at it working.</p><p><strong>Check your setup.</strong> This one script tells you where the project is at and what to do next:</p><pre>scripts/doctor.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2ISHRtqbtsJufzKUqY-gA.png" /><figcaption><strong><em>doctor.sh</em></strong><em> checks the project and always ends with the one next step.</em></figcaption></figure><p>I use this constantly. It answers “where am I?”, which is also the first thing an AI agent needs to know when it opens the repo.</p><p><strong>Run the website:</strong></p><pre>cd site<br>corepack enable<br>pnpm install<br>pnpm dev</pre><p>Open http://localhost:3000. That&#39;s the site your customers will see, with placeholder text for now.</p><p><strong>Run the Mac app:</strong></p><pre>mac/scripts/bootstrap.sh   # generates mac/App.xcodeproj<br>open mac/App.xcodeproj</pre><p>Hit <strong>Run</strong> (⌘R) in Xcode. The app opens on its license window:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wg48Rij9niTB8D-JXY6iCw.png" /><figcaption><em>The license window: paste a key, or buy one.</em></figcaption></figure><p>Want to see what a paying customer sees without a key? Add the launch argument -AppDebugLicense YES under <strong>Product → Scheme → Edit Scheme → Run → Arguments</strong>. It only works in Debug builds, so a real release never skips the license.</p><p><strong>Make sure everything passes:</strong></p><pre>scripts/verify.sh --quick</pre><p>That runs the checks and both test suites in about a minute.</p><h3>Step 2: Make it yours</h3><p>This is where the AI part kicks in. Open the repo in Claude Code (or Cursor, or Codex) and paste something like:</p><blockquote>Make this my product. It’s called <strong>Clip Stack</strong>, the website is <strong>clipstack.app</strong>, I’m <strong>Jane Doe</strong>, and I want to sell it through <strong>Creem</strong> with a license key. Then run doctor and tell me what’s next.</blockquote><p>The agent follows the new-app recipe. It renames everything, sets up payments, runs the checks, and tells you the next step.</p><p>Prefer doing it by hand? Same result:</p><pre>scripts/new-app.sh --name &quot;Clip Stack&quot; --domain clipstack.app \<br>    --maker &quot;Jane Doe&quot; --payments creem --deliverable licence-key<br>scripts/doctor.sh</pre><blockquote>⚠️ <strong>Pick your name and domain carefully.</strong> The app’s bundle ID and URL scheme come from them, and they’re locked in forever once your first version ships.</blockquote><h3>Step 3: Build the part only you can build</h3><p>The main window literally says “Your app goes here.” That’s your job. Everything else is already done.</p><p>The trick is small steps. Describe one feature at a time and let the agent build, test, and check each one before moving on:</p><blockquote>Replace the home screen with my app: [what it does, in two or three sentences]. Keep the Settings button.<br>Add a feature: [one thing the app should do].<br>Add a setting to [what the user can choose].</blockquote><p>Each of these triggers a recipe: add-feature, add-screen, add-setting, add-entitlement. Every recipe ends by running the checks and telling you what only <em>you</em> can verify, like &quot;open the app and click this.&quot;</p><p>Settings, the menu, and the updater are already there, so you’re only adding your own stuff:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QOFVKnuu0K8TXWoAikK5xA.png" /><figcaption><em>Settings ships ready. You just add your own rows.</em></figcaption></figure><h3>Step 4: Write your website</h3><p>The site’s name, copy, and links live in one file: site/lib/site.ts. Prices are in site/lib/pricing.ts. Change those and the whole site follows, including the Open Graph images and structured data.</p><p>The agent can help here too:</p><blockquote>Rewrite the landing page copy for my app: [what it does, who it’s for]. Keep every claim true to what the app really does.</blockquote><blockquote>Write a blog post answering “[a question your customers search for]”, with sources.</blockquote><p>Then deploy the site/ folder to Vercel and point your domain at it. Until you&#39;re ready to sell, the site shows a waitlist instead of a Buy button. You flip that on later.</p><h3>Step 5: Payments and licensing (the part everyone gets wrong)</h3><p>Here’s the whole license flow. Three players: <strong>your Mac app</strong>, <strong>your website</strong>, and <strong>Creem or Polar</strong>.</p><ol><li><strong>Buy.</strong> The Buy button opens your site, which redirects to the provider’s hosted checkout. The provider charges the card and creates a license key with a device limit.</li><li><strong>Key + receipt.</strong> The buyer lands on your thanks page with the key and a one-click “open in app” link. At the same time, a webhook hits your site, which emails a receipt.</li><li><strong>Activate.</strong> The app sends the key and the Mac’s name to <em>your site</em>. Your site checks it with the provider and gets back an activation ID. The app stores it in the Keychain.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pA4QJOt_i4HCWS_ybblmhg.png" /><figcaption><em>The app never talks to the provider directly, so your API key never ships inside the app.</em></figcaption></figure><ol><li><strong>Stay valid.</strong> Once a week, the app checks in.</li></ol><p>This is the part I care about most: <strong>“the server said no” and “I couldn’t reach the server” are two different things.</strong></p><ul><li>The provider says <strong>no</strong> → the app locks right away.</li><li>The server <strong>can’t be reached</strong> → the app keeps working for <strong>14 days</strong> from the last good check.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zzdwq2qeOM4vawxLpII3w.png" /><figcaption><em>No answer is not a “no.” Nobody who paid you should get locked out because your server had a bad day.</em></figcaption></figure><p>It goes one step further. If<em>your</em>API key breaks or gets rotated, the site reports that as “unreachable,” not “invalid.” Otherwise a config mistake on your end would tell every customer their license is bad.</p><ol><li><strong>Refunds.</strong> The provider revokes the key, your site sends a refund email, and the next check-in locks the app. You don’t lift a finger.</li><li><strong>New Mac or lost key.</strong> “Deactivate this Mac” in Settings frees the seat. A /recover page emails every key bought with that address.</li></ol><p>And the best part: <strong>there’s no database.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W0tVcp8LYykj6thvIxSWXA.png" /><figcaption><em>The provider holds the truth. The Keychain holds a copy. Your server remembers nothing.</em></figcaption></figure><p>No database means nothing to back up, nothing to migrate, and no user table to leak. And because the app only talks to your site, you can switch from Creem to Polar (there’s a switch-payments recipe for that) without shipping a new build.</p><h3>Step 6: Emails</h3><p>Emails go out through Resend, and they’re already written: the receipt with the license key, lost-key recovery, refund confirmation, release notes, and the waitlist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dU1vcOM-7i77xawksCk7kQ.png" /><figcaption><em>What a customer gets right after buying.</em></figcaption></figure><p>Need another one? Ask the agent: <em>“Add an email that’s sent to customers when [event], matching the other emails.”</em> That’s the add-email recipe.</p><h3>Step 7: Signing and notarization (the trap)</h3><p>This one burns a lot of first-time Mac devs, so it’s worth spelling out.</p><p>There are two kinds of code-signing certificate. <strong>Apple Development</strong> signs apps for your own devices. <strong>Developer ID Application</strong> signs apps for anyone. An app signed with the first one runs perfectly <em>on your Mac</em>. Then a stranger downloads it and macOS tells them it’s damaged and should go in the Trash.</p><p>No build setting fixes that. You need a Developer ID certificate, and Apple only gives those out through the Apple Developer Program. Enroll early, because Apple’s review of a new account can take anywhere from an hour to a week.</p><p>Once you’re in, docs/releasing.md walks through the one-time setup: the certificate, a notarization profile, and a Sparkle signing key. doctor.sh tells you which parts are still missing.</p><h3>Step 8: Ship it (and every update after)</h3><p>When you’re ready, one command does the whole release:</p><pre>mac/scripts/release.sh 1.0.0 1</pre><p>It builds, signs, notarizes, staples, packages the DMG, and publishes a signed update feed (the “appcast”). You can run the exact same flow in GitHub Actions instead.</p><p>After that, shipping v1.1 is the same command with a new version number. Everyone who has the app gets this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F_9nZIXnYkja14lt41TObg.png" /><figcaption><em>Sparkle only installs updates signed with your key, and the release script refuses to build one that isn’t.</em></figcaption></figure><p>Or just tell the agent:<em>”Ship version 1.1 with these changes: [list]. Stop before publishing so I can check.”</em></p><h3>Step 9: Open for sale</h3><p>docs/go-live.md takes you from test mode to real money:</p><ol><li>Set up the product in the Creem or Polar dashboard (license keys on, device limit set).</li><li>Add your production keys in your hosting dashboard.</li><li>Make <strong>one real purchase</strong> yourself and check the key, the email, and the activation.</li><li><strong>Refund it</strong>, and check that the refund path works too.</li><li>Flip the site from waitlist to Buy.</li></ol><p>That’s it. You’re selling a Mac app.</p><h3>Cheat sheet</h3><p>CommandWhat it doesscripts/doctor.shWhere the project is at, and the next stepscripts/verify.sh --quickChecks + tests, about a minute. Run after any changescripts/verify.shEverything, including both builds. Run before you finishcd site &amp;&amp; pnpm devThe website at localhost:3000mac/scripts/bootstrap.shRegenerate the Xcode project after adding a Swift filemac/scripts/release.sh 1.1.0 2Build, sign, notarize, and ship version 1.1.0 (build 2)</p><h3>Wrapping up</h3><p>The point of all this is simple: <strong>you should spend your time on the part that makes your app yours.</strong> Licensing, payments, emails, signing, and updates are solved problems. They just take forever to solve the first time, and they break in annoying ways when you rush them.</p><p>If you want to skip that part, Build Mac App is at <a href="https://buildmac.app/?ref=medium-article">buildmac.app</a></p><p>Either way, I hope the licensing breakdown saves you some pain. If you’ve got questions about shipping Mac apps (notarization, Sparkle, pricing, whatever), drop them in the comments. I’ve probably hit the same wall.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a40669bee325" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should We Use Flutter Flavors?]]></title>
            <link>https://medium.com/@damienissa/should-we-use-flutter-flavors-d6dda14a865e?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6dda14a865e</guid>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[flutter-architecture]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 21:20:04 GMT</pubDate>
            <atom:updated>2025-12-02T21:20:04.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>Should We Use Flutter Flavors? Or Switch to a Single-Entrypoint Architecture Using dart-define + Injectable?</h3><h3>A practical deep dive for teams building multi-environment Flutter + Firebase apps.</h3><p>When building a production-grade Flutter app, one of the first architectural questions that comes up is:</p><blockquote><strong><em>“How should we manage multiple environments — dev, staging, production — without turning the project into a maintenance nightmare?”</em></strong></blockquote><p>Most tutorials push Flutter <strong>flavors</strong> and <strong>multiple iOS/Android targets</strong>, but in real projects this leads to growing complexity and endless duplication.</p><p>This article explores whether we <em>need</em> flavors at all — especially for teams using Firebase, analytics, deep links, or A/B testing — and outlines an alternative, cleaner architecture that uses:</p><ul><li><strong>One single Flutter entrypoint</strong></li><li><strong>Environment selection via </strong><strong>--dart-define</strong></li><li><strong>Automatic dependency switching via </strong><strong>injectable + </strong><strong>get_it</strong></li></ul><p>Let’s evaluate both approaches and decide which one is best.</p><h3>❓ Do We Actually Need Flavors?</h3><p>Flavors solve real problems, but they also introduce significant overhead.</p><h3>Flavors are useful when you need:</h3><ul><li>Multiple apps installed side-by-side<br> (com.app.dev, com.app.staging, com.app.prod)</li><li>Different app icons, names, splash screens</li><li>Different push notification certificates</li><li>Different associated domains for deep links</li><li>Different Firebase apps <strong>at the native level</strong></li></ul><p>If these cases apply — you can’t avoid iOS/Android native configuration.</p><h3>But in many real apps, we don’t need any of that.</h3><p>You may only need:</p><ul><li>Different <strong>API base URLs</strong></li><li>Different <strong>Firebase collections</strong> or remote config params</li><li>Different <strong>analytics keys</strong></li><li>Different <strong>feature flags</strong></li><li>Different <strong>debug menus</strong></li><li>Different <strong>deep-link routing</strong></li><li>Different <strong>logging / stubs / mocks</strong></li></ul><p>These do <strong>not</strong> require separate iOS targets or flavors.<br>And that’s where the “single entrypoint + dart-define + DI” architecture shines.</p><h3>❗️ The Hidden Problems With Flavors</h3><h4>1. Duplicate iOS targets = massive maintenance burden</h4><p>Every capability (Push Notifications, Associated Domains, Keychain, Signing) must be updated across all targets.</p><h4>2. CI/CD becomes harder</h4><p>Each flavor requires separate build configs and signing settings.</p><h4>3. Flutter code grows messy</h4><p>Developers start sprinkling logic like:</p><pre>if (flavor == Flavor.staging) { ... }</pre><p>across the whole codebase.</p><h4>4. Onboarding new developers becomes painful</h4><p>“Open Xcode, duplicate this target, add the plist, fix the bundle IDs…”</p><h4>5. You lose flexibility</h4><p>Want to add a temporary “QA build”?<br> Congratulations — you now need yet another native target.</p><h3>💡 The Alternative: One Entrypoint + dart-define + Injectable</h3><p>This approach keeps <strong>all environment logic in Dart</strong>, not the native layers.</p><h3>The idea is simple:</h3><h4>1. Single Flutter entrypoint (main.dart)</h4><h4>2. Read environment from --dart-define=APP_ENV=dev|staging|prod</h4><h4>3. Use injectable environments to automatically provide:</h4><ul><li>API client URLs</li><li>Firebase init configs</li><li>Mixpanel/Amplitude/Sentry keys</li><li>Real vs stub deep link handlers</li><li>Real vs debug analytics services</li><li>“Dev menu” toggles</li><li>Mock data in dev mode</li><li>Different feature flags per env</li></ul><p>All controlled by one line of code during startup.</p><h3>🤝 Is This Approach compatible with Firebase?</h3><p><strong>Yes — easily. </strong>For this, you need to initialize Firebase manually:</p><pre>@module<br>abstract class FirebaseModule {<br>  @prod<br>  FirebaseOptions get prodOptions =&gt; const FirebaseOptions(<br>    apiKey: &quot;...&quot;,<br>    projectId: &quot;myapp-prod&quot;,<br>    appId: &quot;...&quot;,<br>    messagingSenderId: &quot;...&quot;,<br>  );<br><br>  @dev<br>  FirebaseOptions get devOptions =&gt; const FirebaseOptions(<br>    apiKey: &quot;...&quot;,<br>    projectId: &quot;myapp-dev&quot;,<br>    appId: &quot;...&quot;,<br>    messagingSenderId: &quot;...&quot;,<br>  );<br>}</pre><p>Then your AppInitializer simply injects the correct one:</p><pre>await Firebase.initializeApp(options: getIt&lt;FirebaseOptions&gt;());</pre><p><strong>No multiple targets needed.<br>No flavor files.<br>No duplicated </strong><strong>GoogleService-Info.plist.</strong></p><h3>🧭 Is It Compatible with Deep Links and Universal Links?</h3><p>Yes — as long as:</p><h3>1. You use ONE associated domain</h3><p>Example:</p><pre>applinks:safeorbit.app</pre><p>You can then route inside the app based on:</p><ul><li>/prod/...</li><li>/staging/...</li><li>/dev/...</li></ul><p>Or add an environment param in the query string.</p><p>This works because the deep link <em>parsing</em> happens in Dart.</p><h3>📊 Is It Compatible with Mixpanel / Amplitude / Sentry?</h3><p>Absolutely.</p><p>Example with injectable:</p><pre>@prod<br>@LazySingleton(as: AnalyticsService)<br>class ProdAnalytics implements AnalyticsService {<br>  ProdAnalytics(this.config);<br>  final AppConfig config;<br>  ...<br>}<br><br>@dev<br>@Environment(&#39;staging&#39;)<br>@LazySingleton(as: AnalyticsService)<br>class DebugAnalytics implements AnalyticsService {<br>  @override<br>  Future&lt;void&gt; logEvent(...) =&gt; print(event);<br>}</pre><p>The correct implementation is injected automatically based on the environment.</p><h3>🧩 Using One Entrypoint with injectable and get_it</h3><p>Here is the final architecture.</p><h3>1. main.dart (single entrypoint)</h3><pre>const _envString = String.fromEnvironment(&#39;APP_ENV&#39;, defaultValue: &#39;prod&#39;);<br><br>Future&lt;void&gt; main() async {<br>  WidgetsFlutterBinding.ensureInitialized();<br>  <br>  final env = parseEnv(_envString);<br>  final injectableEnv = envToInjectable(env);<br>  await configureDependencies(injectableEnv);<br>  runApp(const MyApp());<br>}</pre><h3>2. Environment Config with Injectable</h3><pre>@module<br>abstract class AppConfigModule {<br>  @dev<br>  AppConfig get dev =&gt; const AppConfig(<br>        env: AppEnv.dev,<br>        apiBaseUrl: &quot;https://api-dev.example.com&quot;,<br>        enableDebugMenu: true,<br>      );<br><br>  @Environment(&#39;staging&#39;)<br>  AppConfig get staging =&gt; const AppConfig(<br>        env: AppEnv.staging,<br>        apiBaseUrl: &quot;https://api-staging.example.com&quot;,<br>        enableDebugMenu: true,<br>      );<br><br>  @prod<br>  AppConfig get prod =&gt; const AppConfig(<br>        env: AppEnv.prod,<br>        apiBaseUrl: &quot;https://api.example.com&quot;,<br>        enableDebugMenu: false,<br>      );<br>}</pre><h3>3. Run Commands (No Flavors)</h3><pre>flutter run --dart-define=APP_ENV=dev<br>flutter run --dart-define=APP_ENV=staging<br>flutter run --dart-define=APP_ENV=prod</pre><h3>🏁 Final Verdict: Should You Use Flavors?</h3><h3>✔️ Use this single-entrypoint architecture if:</h3><ul><li>You don’t need multiple apps installed at once</li><li>You want less iOS/Android target maintenance</li><li>You want to manage environments fully in Flutter code</li><li>You use Firebase, Mixpanel, Sentry, Deep Links, or Web sockets</li><li>You want cleaner CI/CD pipelines</li><li>You prefer a DI-driven, scalable architecture</li></ul><h3>❌ Use flavors only if you need:</h3><ul><li>Different bundle IDs</li><li>Different app icons/names</li><li>Different push certificates</li><li>Side-by-side installations</li><li>Different associated domains per env</li><li>Different entitlements per env</li></ul><p><strong>Most apps do NOT need these.</strong></p><h3>🎯 Conclusion</h3><p>A single-entrypoint Flutter app using:</p><ul><li>--dart-define=APP_ENV=...</li><li>injectable environments</li><li>get_it for DI</li></ul><p>is cleaner, easier to maintain, and far more scalable than flavors for the majority of real-world apps.</p><p>You avoid Xcode hell, reduce CI complexity, simplify developer onboarding, and keep all environment logic in one place: <strong>your Dart code.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6dda14a865e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redirectly: Firebase Dynamic Links Alternative]]></title>
            <link>https://medium.com/@damienissa/redirectly-firebase-dynamic-links-alternative-2c30bbd5f13f?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c30bbd5f13f</guid>
            <category><![CDATA[appsflyer]]></category>
            <category><![CDATA[dynamiclinking]]></category>
            <category><![CDATA[deeplink]]></category>
            <category><![CDATA[branch]]></category>
            <category><![CDATA[firebasedynamiclinks]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Thu, 26 Jun 2025 20:00:41 GMT</pubDate>
            <atom:updated>2025-06-26T20:00:41.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pQgLmsOh0gm00npSwsDWrg.png" /></figure><p><strong>Redirectly</strong> lets you create branded deep links that open the right place on <strong>web, iOS, Android, and Flutter</strong> — no heavyweight SDKs, no vendor lock‑in. If Firebase Dynamic Links feels like overkill, this guide is for you.</p><h3>Quick start</h3><h4>Create an Account</h4><p>Sign up at <a href="https://redirectly.app/"><strong>redirectly.app</strong></a>, pick a username, and copy the API key from the dashboard.</p><h4>Create your first link</h4><pre>curl -X POST https://redirectly.app/api/v1/temp-links \ <br>  -H &quot;Authorization: Bearer $API_KEY&quot; \<br>  -d &#39;{ &quot;target&quot;: &quot;https://google.com&quot;, &quot;ttlSeconds&quot;: 900 }&#39;</pre><h3>Backend Integration Recipes</h3><p>Below are minimal snippets. Swap in your own language or visit the full <a href="https://redirectly.app/docs">API reference</a>.</p><pre>import axios from &#39;axios&#39;;<br><br>const redirectly = axios.create({<br>  baseURL: &#39;https://redirectly.app/api&#39;,<br>  headers: { Authorization: `Bearer ${process.env.REDIRECTLY_KEY}` },<br>});<br><br>export async function tempLink(target: string) {<br>  const { data } = await redirectly.post(&#39;/v1/temp-links&#39;, {<br>    target,<br>    ttlSeconds: 900,<br>  });<br>  return data.url;<br>}</pre><h3>Flutter Deep‑Linking in Pure Dart</h3><h4>Install</h4><pre># pubspec.yaml<br>dependencies:<br>  flutter_redirectly: ^2.0.0</pre><h4>Initialize</h4><pre>import &#39;package:flutter_redirectly/flutter_redirectly.dart&#39;;<br><br>final redirectly = FlutterRedirectly();<br><br>Future&lt;void&gt; main() async {<br>  WidgetsFlutterBinding.ensureInitialized();<br>  await redirectly.initialize(<br>    RedirectlyConfig(apiKey: &#39;YOUR_API_KEY&#39;),<br>  );<br>  runApp(const MyApp());<br>}</pre><h4>Handling the Link</h4><pre>// Listen for incoming links<br>redirectly.onLinkClick.listen((linkClick) {<br>  print(&#39;Link: ${linkClick.originalUrl}&#39;);<br>  print(&#39;Slug: ${linkClick.slug}&#39;);<br>  <br>});<br><br>// Handle app launch from link<br>final initialLink = await redirectly.getInitialLink();<br>if (initialLink != null) {<br>  // Handle same as above<br>}</pre><h3>iOS Associated Domains<strong> Setup</strong></h3><p>Add to Runner.entitlements:</p><pre>&lt;array&gt;<br>  &lt;string&gt;applinks:YOUR_SUB.redirectly.app&lt;/string&gt;<br>&lt;/array&gt;</pre><h3>Android Manifest</h3><pre>&lt;intent-filter android:autoVerify=&quot;true&quot;&gt;<br>  &lt;action android:name=&quot;android.intent.action.VIEW&quot;/&gt;<br>  &lt;category android:name=&quot;android.intent.category.DEFAULT&quot;/&gt;<br>  &lt;category android:name=&quot;android.intent.category.BROWSABLE&quot;/&gt;<br>  &lt;data android:scheme=&quot;https&quot;<br>        android:host=&quot;YOUR_SUB.redirectly.app&quot;/&gt;<br>&lt;/intent-filter&gt;</pre><h3>Conclusion</h3><p>Redirectly removes the friction from deep‑linking so you can concentrate on building products, not plumbing. In a few API calls you get branded, privacy‑respecting links that work everywhere — web, iOS, Android, and Flutter — without Google’s bulk or lock‑in. Whether you’re a solo hacker testing an MVP or an enterprise team migrating thousands of links, Redirectly keeps your stack slim and your users landing exactly where they should.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c30bbd5f13f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launch an ERC-20 Token in 5 Minutes. Zero Coding Required]]></title>
            <link>https://medium.com/@damienissa/launch-an-erc-20-token-in-5-minutes-zero-coding-required-3de711ef0ac5?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/3de711ef0ac5</guid>
            <category><![CDATA[erc20-token]]></category>
            <category><![CDATA[erc20-token-development]]></category>
            <category><![CDATA[erc20]]></category>
            <category><![CDATA[erc20-token-generator]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 12:37:46 GMT</pubDate>
            <atom:updated>2025-06-16T12:37:46.511Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>You don’t need Solidity skills or a dev team.<br>You only need a browser, MetaMask, and a few clicks</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*xlzd5S5ZJ88NjlPZV6B1Ow.png" /></figure><h3>Why You Might Want a Token?</h3><ul><li>Reward your community</li><li>Power an in-game economy</li><li>Test a new business idea</li><li>Raise funds with a presale</li></ul><p>In the past, you had to write smart-contract code, hope it was secure, then fight with Etherscan to verify it. That’s slow, risky, and expensive.</p><p><a href="http://presalehub.io/"><strong>PresaleHub’s</strong></a><strong> token builder makes the whole process as easy as filling out a form.</strong></p><h3>What You’ll Need?</h3><ol><li><strong>MetaMask</strong> (or any WalletConnect wallet)</li><li><strong>A little ETH</strong> for gas + feature fees</li><li><strong>Five minutes</strong> of your time</li></ol><p>That’s it.</p><h3>The 5-Step Flow</h3><ul><li><strong>Name your token</strong> — enter name, symbol, supply, and decimals</li><li><strong>Pick features</strong> — toggle Mintable, Burnable, Pausable, etc. Each shows a small extra fee</li><li><strong>Check the price</strong> — live total updates as you toggle</li><li><strong>Connect wallet &amp; sign</strong> — MetaMask pops up; hit <em>Confirm</em></li><li><strong>Done!</strong> — Contract deploys &amp; auto-verifies on Etherscan</li></ul><h3>Built-In Safety</h3><ul><li>Uses battle-tested <strong>OpenZeppelin</strong> code</li><li>Only adds the features you select — no extra bloat</li><li>Auto-verifies source on <strong>Etherscan</strong> so anyone can inspect it</li></ul><h3>Popular Setups</h3><ul><li><strong>Fixed community token</strong> → toggle <strong>Burnable</strong></li><li><strong>Governance token</strong> → toggle <strong>Ownable</strong> + <strong>Access Roles</strong></li><li><strong>Game currency</strong> → toggle <strong>Mintable</strong> + <strong>Pausable</strong></li></ul><h3>Why It’s Cheaper &amp; Faster</h3><ul><li>Write &amp; test Solidity → <strong>0 code</strong> with PresaleHub</li><li>Pay for an audit (1–2 ETH) → <strong>Audit included</strong></li><li>Manual Etherscan verify → <strong>Auto-verified</strong></li><li>Weeks of dev time → <strong>Minutes</strong></li></ul><h3>Try It Yourself</h3><ol><li>Open <a href="http://presalehub.io/"><strong>PresaleHub.io</strong></a></li><li>Click <strong>Create ERC-20 Token</strong></li><li>Follow the 5 steps above</li></ol><p>Your token will be live on Ethereum before your coffee cools.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3de711ef0ac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crafting an Effective Resume in 2025: Personalize, Optimize, and Stand Out]]></title>
            <link>https://medium.com/@damienissa/crafting-an-effective-resume-in-2025-personalize-optimize-and-stand-out-54179d7548a1?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/54179d7548a1</guid>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[resume-writing-tips]]></category>
            <category><![CDATA[resume-writing]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Mon, 02 Jun 2025 21:02:37 GMT</pubDate>
            <atom:updated>2025-06-02T21:02:37.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_UIyRun1iyD-AL1Mvp1IA.png" /></figure><p>The job hunt has changed dramatically, and so has the resume. In 2025, a great resume is more than just a list of past jobs — it’s a personalized marketing tool tuned for both human recruiters and the AI-driven systems that screen applications. Whether you’re going for your first job or switching careers mid-stream, knowing the latest resume trends will give you an edge. In this article, we’ll highlight how personalization, AI/ATS optimization, and modern design best practices can make your resume stand out and land you interviews.</p><h3>Why Beating the ATS Bots Is Essential</h3><p>Most medium-to-large companies now use Applicant Tracking Systems (ATS) to scan resumes — if yours isn’t optimized for these systems, it might never reach human eyes. On average, only about one in four resumes passes the ATS filters and gets seen by a recruiter. These bots scan for relevant keywords, job titles, and proper formatting to decide if your resume matches the job.</p><p>How can you make sure your resume survives the filter? Use a straightforward format that the software can easily read — stick to standard fonts and clear headings, and avoid any graphics or layouts that might confuse the parser. Next, mirror the job description’s keywords in your resume. If the job posting mentions “Project Management” or “JavaScript,” include those exact terms in your skills or experience sections (assuming you have those qualifications).</p><p>One smart move is to run your resume through an AI resume checker before you apply. For example, <a href="https://jobbotic.space/">Jobbotic</a> is an AI-powered service that compares your resume against a specific job posting and gives you feedback to improve your ATS score. Tools like this can quickly highlight missing keywords or formatting issues, so you can adjust your resume and boost your chances of getting through the digital gatekeeper.</p><h3>Personalize Your Resume for Each Application</h3><p>No more one-size-fits-all resumes — in 2025, personalization is key. A generic resume that you blast out everywhere is likely to flop. Hiring managers can tell when you haven’t bothered to tailor your application, and an untailored resume often lacks the specific keywords and focus that ATS scans look for. Instead, <em>customize your resume for each job</em>: show that you understand what the employer wants and highlight how you meet their needs.</p><p>Start by researching the role and the company. Then tweak your resume’s content to spotlight the most relevant experience, skills, and achievements for that position. Maybe you reorder some bullet points or add details that address a requirement from the job ad. These tweaks can make a big difference.</p><p>Consider swapping out the old-fashioned objective statement for a brief professional summary or personal branding statement that captures who you are and what value you bring. For example: <em>“Marketing graduate with proven SEO and social media skills, eager to drive growth at Company X with data-driven strategy.”</em> In two or three lines, you’ve showcased relevant skills and aligned yourself with the company’s goals.</p><p>If you’re an entry-level job seeker, leverage any internships, class projects, or volunteer work to show you have real-world skills. And if you’re a mid-career professional changing fields, highlight the transferable skills from your past roles that apply to your new target role. In both cases, make it clear that you have what it takes to succeed in the position, even if your background is non-traditional.</p><h3>Modern Resume Design: Keep it Simple, Make it Skimmable</h3><p>Resume design trends in 2025 favor clean, easy-to-read layouts. This isn’t the era of overly fancy templates — the goal is a modern, professional look that’s also ATS-compatible. Use legible fonts (think Calibri, Arial, or similar), clear section headings, and plenty of white space for readability. A subtle pop of color or a unique header can add a touch of personality, but don’t go overboard. Remember that both hiring managers <em>and</em> algorithms need to parse your resume without trouble, so avoid elements like text boxes, images, or intricate graphics that might get scrambled.</p><h3>Quick Tips to Make Your Resume Stand Out</h3><ul><li>Tailor every time: Edit your resume for <em>each</em> application. Show the exact skills and keywords that the particular employer is looking for, rather than sending a generic resume.</li><li>Lead with a strong summary: Begin with a concise and impactful summary or branding statement that effectively highlights your top relevant strengths and goals. Grab their attention in the first few lines.</li><li>Show results, not just duties: Under each job, focus on what you <em>achieved</em>. Use numbers and action verbs (e.g., “boosted customer satisfaction 25%” instead of “responsible for customer service”).</li><li>Use keywords wisely: Weave important keywords from the job description into your resume naturally so ATS bots and human readers both see them. Don’t overstuff jargon; make sure your sentences still read smoothly.</li><li>Please keep it clean and ATS-friendly: Fancy fonts or complicated layouts can hurt more than help. Stick to a clean format with standard sections and simple design elements. Your goal is a resume that looks good <em>and</em> parses correctly.</li><li>Double-check and refine: Typos or sloppy formatting can ruin an otherwise great resume. Always proofread and get a second pair of eyes to review it. You can also use a tool like Jobbotic or an online resume grader to catch anything you might have missed.</li></ul><p>By following these trends and tips, you’ll create a resume that <em>both</em> passes the high-tech screening filters <em>and</em> impresses the humans on the other side. It takes a bit more effort to personalize and optimize your resume in 2025, but the payoff is huge: more callbacks, more interviews, and a faster track to that job you’re after.</p><p><strong>Good luck with your job search!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54179d7548a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Instantly Improve Your Resume]]></title>
            <link>https://medium.com/@damienissa/how-to-instantly-improve-your-resume-a6871ef49327?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6871ef49327</guid>
            <category><![CDATA[cv-writing]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Sun, 25 May 2025 20:26:16 GMT</pubDate>
            <atom:updated>2025-05-25T20:26:16.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xq7Vqlkvryxrx7xHRdG7eA.png" /></figure><p>Let’s face it — writing a resume is one of the most soul-sucking tasks in the job hunt. You’re expected to condense years of experience into one clean, compelling page that somehow makes you look competent, likable, and hireable. Easy, right?</p><p>No wonder most resumes end up sounding the same: overly formal, packed with buzzwords, and completely forgettable.</p><p>But here’s the good news: improving your resume doesn’t have to mean starting from scratch. A few small changes can make a huge difference in how you’re perceived by both hiring managers and the ever-mysterious ATS bots.</p><p>Here’s how to level up your resume without tearing it all down.</p><h3>1. Cut the Fluff. Seriously.</h3><p>Phrases like <em>“hard-working team player”</em>, <em>“results-oriented professional”</em>, and <em>“excellent communication skills”</em> sound impressive — until you realize that everyone else is using them too.</p><p><strong>What to do instead</strong>: Focus on specific achievements. Numbers are your best friend.</p><blockquote><em>❌ “Responsible for managing a team”<br> ✅ “Managed a team of 5 and increased delivery speed by 30% over 3 months”</em></blockquote><h3>2. Reorder for Impact</h3><p>Most people bury their most impressive achievements in the middle of a bullet list.</p><p><strong>Fix this</strong> by putting your strongest, most measurable result at the top of each section. It hooks the reader instantly — and makes skimming way easier.</p><h3>3. Use Keywords — But Make Them Natural</h3><p>Yes, you need to optimize for applicant tracking systems (ATS). But that doesn’t mean stuffing your resume like a Thanksgiving turkey with every keyword you can think of.</p><p>Instead, read a few job descriptions in your field and sprinkle in those relevant phrases, as long as they fit naturally.</p><h3>4. Let AI Do the Heavy Lifting (Shhh… This Is the Secret Weapon)</h3><p>There’s a reason professional resume writers charge hundreds of dollars: writing about yourself is hard. That’s why a new generation of AI tools is quietly changing the game.</p><p>Take <a href="https://www.jobbotic.space/"><strong>Jobbotic</strong></a> for example — it’s a clever little platform that turns your raw experience into a job-ready resume in less than 60 seconds. No templates to mess with. No second-guessing your wording. Just answer a few fun questions and boom — you get a solid draft that sounds like you <em>on your best day</em>.</p><p>I tried it with a messy old resume I hadn’t touched in years — and the result was surprisingly fresh, focused, and modern. If you’re short on time (or confidence), it’s a no-brainer.</p><h3>5. Tailor for Each Role (Yes, Every Time)</h3><p>The best resumes were written specifically for the job. That means tweaking your summary, rearranging your skills, and swapping out less-relevant experience.</p><p>It takes 10–15 minutes max, <em>showing the hiring manager that you care</em>.</p><h3>6. Format for Skimmability</h3><p>Recruiters spend 6–8 seconds on a resume before making a judgment. That means:</p><ul><li>Use clear section headings</li><li>Avoid walls of text</li><li>Stick to a clean font (no Comic Sans, please)</li><li>Leave plenty of white space</li></ul><p>Pro tip: If a 14-year-old can’t skim your resume and tell you what you do, it’s too cluttered.</p><h3>Final Thought: Your Resume Is a Pitch, Not a Biography</h3><p>Don’t try to cram in everything you’ve ever done. Just tell a short, sharp story that makes one thing clear: <em>this person can help our company win</em>.</p><p>And if you’re feeling stuck, tools like <strong>Jobbotic</strong> exist for a reason. Let the robots help you look human — and maybe even land that interview faster than you think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6871ef49327" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Beat the ATS and Get Interviews Using Jobbotic]]></title>
            <link>https://medium.com/@damienissa/how-to-beat-the-ats-and-get-interviews-using-jobbotic-b185c02b4543?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/b185c02b4543</guid>
            <category><![CDATA[ats-resume]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[resume-writing-tips]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Thu, 08 May 2025 14:41:56 GMT</pubDate>
            <atom:updated>2025-05-08T14:41:56.698Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6HsqALVpCkAKCb-k" /></figure><h3>🧠 The Harsh Truth About Hiring</h3><p>When you apply for a job, you imagine someone reading your resume, thinking “This person is perfect,” and inviting you to interview.</p><p>The reality? <strong>Most resumes never get read.</strong></p><p>They get filtered out by an algorithm — aka the <strong>ATS</strong> (Applicant Tracking System) — before a human even sees your name.</p><p>I know this because I’ve been there.<br> Hundreds of applications.<br> Zero responses.<br> And a growing suspicion that something was broken.</p><h3>👨‍💻 My Story: From Rejection to Reinvention</h3><p>I wanted to work in big tech. I had experience, projects, passion.<br> But no matter how many resumes I tailored or how often I updated my LinkedIn, <strong>I got ghosted.</strong></p><p>That pain turned into obsession.</p><p>And that obsession turned into <strong>Jobbotic</strong> — an AI-powered resume optimizer designed to help job seekers beat the ATS and finally get noticed.</p><p>I built it not just as a tool, but as a <em>response</em> to the system that kept shutting me out.</p><h3>🤖 What Is an ATS (And Why Is It So Brutal)?</h3><p>An ATS is like a robot gatekeeper.<br> It scans resumes for:</p><ul><li>Keywords</li><li>Formatting</li><li>Relevance to the job description</li></ul><p>If your resume doesn’t match the machine’s criteria, you’re out — before a recruiter ever lays eyes on it.</p><p>And most people don’t even know they’ve been filtered.</p><h3>💡 Why I Built Jobbotic</h3><p>Jobbotic isn’t just a resume tool. It’s an <strong>ATS fighting assistant</strong>.</p><p>Link: <a href="https://jobbotic.space/">https://jobbotic.space</a><br>Here’s how it works:</p><ol><li><strong>You upload your resume</strong></li><li><strong>You paste the job description</strong></li><li><strong>Jobbotic runs an AI comparison</strong></li><li><strong>You get suggestions to boost your ATS score</strong></li><li><strong>You fix your resume and stand a real chance</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b8ruWHik6O8etQ9GBptauQ.png" /></figure><h3>📈 Real Results (Even In Beta)</h3><p>Since launching:</p><ul><li>I’ve received honest feedback from users</li><li>Fixed bugs, improved UX</li><li>And watched people start getting interviews again</li></ul><p>It’s early. But it’s working.</p><p>And I’m building in public so you can follow every update, win, and breakdown in real-time.</p><h3>🎯 Tips to Beat the ATS With or Without Jobbotic</h3><p>Whether you use my tool or not, here’s what you need to do:</p><ul><li>Match the job description closely</li><li>Use exact phrases and skills listed in the post</li><li>Avoid over-designed resumes (stick to simple layouts)</li><li>Tailor every resume — generic ones get trashed</li><li>Include hard skills, not just soft ones</li></ul><h3>🚀 Final Thoughts</h3><p>Job hunting in 2025 isn’t just about being qualified.<br>It’s about being visible to the machine that decides if you get a shot.</p><p>I built Jobbotic because I was tired of waiting to be seen.</p><p>Now I’m helping others do the same.</p><p>If you’re tired of getting ghosted, maybe it’s time to fight back — with code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b185c02b4543" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ How to Create an ERC20 Token on Ethereum — Without Writing a Single Line of Code]]></title>
            <link>https://medium.com/@damienissa/how-to-create-an-erc20-token-on-ethereum-without-writing-a-single-line-of-code-79592352cf53?source=rss-32796b66bdaf------2</link>
            <guid isPermaLink="false">https://medium.com/p/79592352cf53</guid>
            <category><![CDATA[erc20-token]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum-blockchain]]></category>
            <category><![CDATA[erc20-token-development]]></category>
            <dc:creator><![CDATA[Dmytro Virych]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 07:50:02 GMT</pubDate>
            <atom:updated>2025-04-23T07:50:02.379Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚀 How to Create an ERC20 Token on Ethereum — Without Writing a Single Line of Code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q9sPCAEnYDz7nYhJxelemA.png" /></figure><p>In the past, launching a token on Ethereum required developers, smart contract audits, and a solid grasp of Solidity. Today? You don’t even need to write code.</p><p>At <a href="http://presalehub.io/">PresaleHub</a>, we’re on a mission to make token creation as easy as launching a Shopify store. If you’ve got an idea and a wallet — you’re ready.</p><p>Let’s walk you through <strong>how to create your own ERC20 token</strong> in just a few clicks.</p><h3>🧠 Wait, What Is an ERC20 Token?</h3><p>ERC20 is the most popular token standard on Ethereum. It defines how tokens behave: how they’re transferred, how balances are tracked, and how interactions with smart contracts work.</p><p>Most tokens you’ve heard of — $UNI, $LINK, $USDT — are ERC20s.</p><h3>👨‍💻 Why People Think You Need to Code</h3><p>Traditionally, creating a token required:</p><ul><li>Writing a smart contract in Solidity</li><li>Setting up a development environment (like Hardhat or Remix)</li><li>Deploying the contract via MetaMask</li><li>Testing everything to make sure your contract is secure</li></ul><p>And if you got it wrong? You could lock or lose your entire supply.</p><h3>✨ No-Code Token Creation with PresaleHub</h3><p>PresaleHub removes the technical headache. Here’s how:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aa28ddyA5dSTI15Hd_Lh-A.png" /></figure><h3>✅ Step 1: Enter Your Token Info</h3><p>Just fill out a simple form:</p><ul><li><strong>Token name</strong> (e.g., My Token)</li><li><strong>Symbol</strong> (e.g., MTK)</li><li><strong>Supply</strong> (e.g., 1,000,000)</li></ul><h3>🔒 Step 2: Select Features</h3><p>Choose from advanced options without writing code:</p><ul><li><strong>Mintable</strong>: You can mint more tokens later</li><li><strong>Burnable</strong>: Tokens can be destroyed</li><li><strong>Pausable</strong>: Emergency stop if needed</li><li><strong>Ownable</strong>: Transfer ownership of the contract</li></ul><h3>🚀 Step 3: Deploy to Ethereum</h3><p>Click “Deploy,” approve the transaction in your wallet, and your token is live on the Ethereum blockchain.</p><p>That’s it. No developers, no audits, no mistakes.</p><h3>🛠️ Why This Matters</h3><p>PresaleHub was designed for creators, meme lords, founders, and marketers — not Solidity engineers.</p><p>You can:</p><ul><li><strong>Test ideas quickly</strong></li><li><strong>Launch tokens for real communities</strong></li><li><strong>Build your own tokenomics experiments</strong></li></ul><p>And if you’re serious about taking the next step — we even offer <strong>no-code presale pages</strong>, smart contract-secured fundraising, and full token distribution automation.</p><h3>🌍 Your Token Is Just the Beginning</h3><p>PresaleHub isn’t just a generator. It’s an ecosystem:</p><ul><li>🚫 No-code token creation</li><li>📊 Transparent, decentralized presale system</li><li>💰 Launch fundraising without trust issues</li><li>🛠️ Tools to grow your community and utility</li></ul><h3>Ready to create?</h3><p>Click here to launch your token in minutes — no code required:<br> 👉 <a href="https://presalehub.io/">presalehub.io</a></p><p>Whether you’re building a meme coin, testing a new DAO model, or starting the next Web3 revolution — it begins here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79592352cf53" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>