<?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"><channel><title><![CDATA[Jordan Hayes]]></title><description><![CDATA[Jordan Hayes]]></description><link>https://jordanhayes.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 20:15:30 GMT</lastBuildDate><atom:link href="https://jordanhayes.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Free Instant Cash Advance Apps: Auditing the Claims in Code]]></title><description><![CDATA[Every cash advance app on the App Store claims to be "free" and "instant." As developers, we know that marketing copy and actual system behavior are two…]]></description><link>https://jordanhayes.hashnode.dev/free-instant-cash-advance-apps-auditing-the-claims-in-code</link><guid isPermaLink="true">https://jordanhayes.hashnode.dev/free-instant-cash-advance-apps-auditing-the-claims-in-code</guid><category><![CDATA[cash advance apps]]></category><dc:creator><![CDATA[jordanhayes]]></dc:creator><pubDate>Wed, 09 Sep 2026 17:11:32 GMT</pubDate><content:encoded><![CDATA[<p>Every cash advance app on the App Store claims to be "free" and "instant." As developers, we know that marketing copy and actual system behavior are two very different things. So I did what any engineer would do: I pulled the public API documentation, fee schedule endpoints, and terms of service from the top contenders and mapped out what "free" actually means at the data layer.</p>
<p>The results were... unsurprising if you've ever read a SaaS pricing page carefully. Most apps use a classic freemium architecture where the free tier is real but deliberately throttled — specifically on the <em>speed</em> dimension. Let me walk through what I found.</p>
<h2>The Architecture of "Free" in Fintech Apps</h2>
<p>Before diving into individual apps, it helps to understand the two-axis model these products are built on:</p>
<ul>
<li><p><strong>Cost axis</strong>: subscription fees, per-advance fees, tips, interest</p>
</li>
<li><p><strong>Speed axis</strong>: standard ACH (1–3 business days) vs. instant transfer (debit card push, typically sub-30 minutes)</p>
</li>
</ul>
<p>Nearly every app in this space offers $0 on the cost axis for standard delivery. The monetization kicks in on the speed axis. Instant transfers — technically implemented as debit card push payments via networks like Visa Direct or Mastercard Send — cost the app real money to process. That cost gets passed to users as an "express fee" ranging from $1.99 to over $8.00 depending on the advance amount.</p>
<p>So when an app says "free instant cash advance," you need to ask: free <em>and</em> instant, or free <em>or</em> instant?</p>
<h2>Auditing the Top Apps: What the Fee Schedules Actually Say</h2>
<h3>Dave</h3>
<p>Dave's public terms show a \(1/month membership fee just to access advances. Instant delivery to an external bank account runs \)3.00–$13.99 depending on amount. The "free" label applies only to standard ACH delivery, which takes 1–3 days. If you need $100 today, you're paying a fee. Their API responses for transfer status include an <code>express_fee</code> field that's never null for instant transfers to non-Dave accounts.</p>
<h3>Earnin</h3>
<p>Earnin's model is tip-based, which is clever from a regulatory standpoint but functionally equivalent to a fee. Their Lightning Speed feature (instant transfer) requires a $3.99 "tip" minimum in practice, according to their disclosed fee schedule. The CFPB has <a href="https://www.consumerfinance.gov/">noted concerns</a> about tip-based models obscuring true APR in earned wage access products — worth reading if you're building in this space.</p>
<h3>MoneyLion (Instacash)</h3>
<p>MoneyLion's fee disclosure is more transparent than most. Standard delivery is genuinely $0, but instant delivery fees scale from $0.49 to \(8.99. Their RoarMoney account holders get better rates, which is a classic product-led growth lock-in pattern. The subscription tier (MoneyLion+ at \)19.99/month) unlocks higher advance limits. Not free.</p>
<h3>Brigit</h3>
<p>Brigit requires a $9.99/month subscription to access any cash advance. The advance itself has no additional fee, but the subscription is a hard gate. From an engineering perspective, their eligibility API requires an active subscription token before returning advance availability — the free tier literally cannot call the advance endpoint successfully.</p>
<h3>FloatMe</h3>
<p>FloatMe caps advances at $50 and charges $1.99/month. Small amounts, small fees, but not zero. Their instant transfer uses standard debit push and is included in the subscription — so "instant" is real here, but "free" isn't.</p>
<h2>The One App With an Actual $0 Structure</h2>
<p>After going through the fee schedules, one app stood out structurally: Gerald. The model is architecturally different from the others. Rather than a freemium speed-gate, Gerald uses a BNPL (Buy Now, Pay Later) gateway model. Users make a purchase through Gerald's integrated marketplace first, which unlocks a cash advance transfer with zero fees — no subscription, no express fee, no tip prompt, no interest.</p>
<p>The BNPL-as-gateway pattern is genuinely novel in this space. It shifts the monetization to the merchant side (Gerald earns from retail partnerships) rather than extracting fees from users who are, by definition, already cash-constrained. If you want to see how this plays out in practice, the <a href="https://apps.apple.com/us/app/gerald-cash-advance-app/id1569801600">free instant cash advance apps</a> category on the App Store includes Gerald, and the reviews reflect the zero-fee experience consistently.</p>
<p>From a product architecture standpoint, this is a cleaner separation of concerns: the monetization layer is decoupled from the advance delivery layer. Users aren't penalized for needing money faster.</p>
<h2>How Instant Transfer Actually Works Under the Hood</h2>
<p>For the developers curious about the plumbing: "instant" transfers in consumer fintech are almost always implemented via one of two rails:</p>
<ol>
<li><p><strong>Visa Direct / Mastercard Send</strong>: Push payments to debit cards, typically settling in under 30 minutes. Cost to the sender: roughly $0.25–$1.50 per transaction depending on volume and agreement.</p>
</li>
<li><p><strong>RTP (Real-Time Payments) via The Clearing House</strong>: Bank-to-bank, settles in seconds. Requires both sending and receiving banks to be RTP-enabled. Growing adoption but not universal as of 2026.</p>
</li>
</ol>
<p>Standard ACH, by contrast, costs fractions of a cent per transaction but batches overnight. This is why the speed-cost tradeoff exists — it's not artificial scarcity, it's real infrastructure cost. The question is who absorbs it.</p>
<p>According to <a href="https://www.bankrate.com/">Bankrate</a>, the average American has less than $500 in emergency savings, which explains the demand for these products. The irony is that the users who most need instant access are the ones least able to absorb a $3–$8 express fee on a $100 advance — that's an effective APR that would make any regulator wince.</p>
<h2>What to Look For If You're Building in This Space</h2>
<p>If you're a developer evaluating these apps for integration, partnership, or just competitive research, here's a quick audit checklist:</p>
<ul>
<li><p><strong>Check the fee schedule endpoint</strong>, not the marketing page. Most apps expose <code>/fees</code> or <code>/pricing</code> in their developer docs or terms of service appendix.</p>
</li>
<li><p><strong>Look for subscription gates</strong> on the advance eligibility endpoint. If eligibility requires an active paid subscription, the product isn't free.</p>
</li>
<li><p><strong>Test the instant transfer flow</strong> end-to-end. The express fee is often surfaced only at the final confirmation step — a dark pattern worth noting.</p>
</li>
<li><p><strong>Read the tip prompt UX</strong>. Tip-based models are designed to make $0 feel socially uncomfortable. That's a behavioral economics pattern, not a technical one, but it affects real cost.</p>
</li>
</ul>
<h2>The Verdict</h2>
<p>The phrase "free instant cash advance" is doing a lot of work in the App Store. In 2026, after auditing the public fee schedules and terms of service for the major players, the honest breakdown is:</p>
<ul>
<li><p><strong>Free + slow</strong>: Most apps (Dave, MoneyLion, Earnin on standard ACH)</p>
</li>
<li><p><strong>Instant + paid</strong>: Most apps when you need money today</p>
</li>
<li><p><strong>Free + instant</strong>: Structurally rare — requires a different monetization model entirely</p>
</li>
</ul>
<p>The BNPL-gateway model Gerald uses is the most technically coherent answer to this constraint I've found. Whether it's the right fit depends on your use case, but it's worth understanding as a pattern — especially as earned wage access regulation continues to evolve under CFPB oversight.</p>
<p>If you're building a fintech product or just doing competitive analysis, the lesson here is the same one we apply to any system: read the actual spec, not the README. The fee schedule is the spec. The marketing page is the README.</p>
]]></content:encoded></item><item><title><![CDATA[Free Instant Cash Advance Apps: A Developer's Technical View of the Zero-Fee Model (2026)]]></title><description><![CDATA[If you've ever looked under the hood of a fintech app, you know that "free" and "instant" are two words that rarely coexist without some engineering…]]></description><link>https://jordanhayes.hashnode.dev/free-instant-cash-advance-apps-a-developer-s-technical-view-of-the-zero-fee-model-2026</link><guid isPermaLink="true">https://jordanhayes.hashnode.dev/free-instant-cash-advance-apps-a-developer-s-technical-view-of-the-zero-fee-model-2026</guid><category><![CDATA[instant cash advance,]]></category><dc:creator><![CDATA[jordanhayes]]></dc:creator><pubDate>Wed, 09 Sep 2026 17:03:30 GMT</pubDate><content:encoded><![CDATA[<p>If you've ever looked under the hood of a fintech app, you know that "free" and "instant" are two words that rarely coexist without some engineering trade-off. Spending time thinking about API latency, payment rails, and monetization architecture made me curious about how free instant cash advance apps actually pull off their zero-fee promise — or whether they do at all.</p>
<p>This isn't a marketing listicle. It's a technical and product-level breakdown of how these apps work, where the money actually comes from, and what the architecture looks like behind the scenes. If you're building in fintech or just want to understand the mechanics before trusting an app with your bank credentials, this is for you.</p>
<p>The Core Problem: ACH Is Free but Slow; Instant Is Fast but Costly Every cash advance app is fundamentally solving the same problem: bridging a user's cash flow gap between now and their next paycheck. The payment infrastructure they sit on top of is largely the same across the industry — the ACH (Automated Clearing House) network and real-time payment rails like RTP or push-to-debit via Visa/Mastercard networks.</p>
<p>Here's the technical reality:</p>
<p>Standard ACH transfers: Free to initiate, but settlement takes 1–3 business days. That's why "free" transfers on most apps aren't actually instant. Same-day ACH: Faster (same business day), but the originating bank pays a per-transaction fee to the ACH operator. That cost gets passed to users as an "express fee." Push-to-debit (Visa/Mastercard rails): Near-instant (typically under 30 minutes), but interchange fees and network fees make this the most expensive option for the app to offer. Most apps charge $1–$8+ for this. So when Google's AI overview correctly notes that "truly instant and completely free transfers are rare," it's describing a real infrastructure constraint — not just a business decision. Which apps have found a model that absorbs or routes around these costs?</p>
<p>Monetization Architecture: Where the Revenue Actually Comes From To understand how an app can offer a free advance, you need to understand how it makes money elsewhere. There are roughly four monetization models available:</p>
<ol>
<li><p>Subscription Model Apps like Dave (\(1/month) and MoneyLion (up to \)19.99/month for premium tiers) charge a flat subscription. The advance itself may be "free" in the sense that there's no per-advance fee, but you're paying for access. From an engineering standpoint, this is the simplest model — predictable recurring revenue, easy to model churn and LTV.</p>
</li>
<li><p>Tips / Voluntary Fees Earnin popularized this approach. There's no mandatory fee, but the UI nudges users toward tipping. The CFPB has scrutinized this model — see consumerfinance.gov for their ongoing work on earned wage access regulation. From a product perspective, this carries a dark pattern risk: the "free" framing is technically accurate but behaviorally manipulative.</p>
</li>
<li><p>Express Fee Upsell This is the most common model. Standard delivery is free (ACH, 1–3 days). Instant delivery costs $2–$8. The app makes money on the delta between users who need it now and users who can wait. Brigit, FloatMe, and many others use this architecture.</p>
</li>
<li><p>BNPL / Commerce Integration This is the most technically interesting model, and it's where the genuinely zero-fee advance becomes possible. Instead of charging for the advance directly, the app monetizes through a commerce layer — essentially acting as a merchant or affiliate for purchases made through an integrated marketplace. The advance is subsidized by the margin on those transactions.</p>
</li>
</ol>
<p>Gerald relies on this exact setup. Users shop through Gerald's integrated Cornerstore (a BNPL marketplace), and that commerce activity unlocks the ability to transfer a cash advance to their bank at zero cost — no subscription, no express fee, no tip prompt. If you want to see how this plays out in a real app, free instant cash advance apps built on this BNPL-gateway model are worth studying from a product architecture standpoint. The advance ceiling is $200, but the fee structure is genuinely $0 across the board.</p>
<p>What "Instant" Actually Means at the Infrastructure Level When an app advertises instant transfers, it's almost always referring to push-to-debit delivery to a Visa or Mastercard debit card. The technical flow looks roughly like this:</p>
<p>User requests advance in-app App's backend calls its banking partner's API (e.g., Evolve Bank, Sutton Bank, or similar BaaS providers) Banking partner initiates a Visa Direct or Mastercard Send transaction Funds appear in user's debit account within minutes The "instant" label is accurate for supported banks. However, not all debit cards support push-to-debit receiving, and not all banks process these credits at the same speed. Gerald notes that instant transfers are available for select banks — an honest disclosure of this infrastructure reality, rather than a bait-and-switch.</p>
<p>Standard ACH delivery, by contrast, goes through the Federal Reserve's ACH system or EPN (Electronic Payments Network), with batch processing windows that explain the 1–3 day delay. The Federal Reserve has been expanding FedNow (launched 2023) as a real-time alternative, and some fintech platforms are beginning to integrate it — though adoption is still early as of 2026.</p>
<p>No Credit Check: What's Actually Happening Most cash advance apps advertise no credit check, and technically that's true — they aren't pulling a hard inquiry from Equifax, Experian, or TransUnion. They aren't flying blind either. The underwriting model typically uses:</p>
<p>Bank account data (via Plaid or similar): Income frequency, average balance, overdraft history, direct deposit patterns Behavioral signals: App usage patterns, repayment history within the platform Employment verification: Some apps require proof of regular income or direct deposit Cash flow underwriting is a legitimate alternative credit model that the CFPB has been studying as part of broader open banking initiatives. For users locked out of traditional credit products, it's a meaningful access point. Developers building consumer features will find that Plaid's API and competitors like MX or Finicity form the data layer most of these platforms rely on.</p>
<p>Comparing the Real-World Models in 2026 Here's a quick technical comparison of the dominant models, based on publicly available product information:</p>
<p>Dave: \(1/month subscription + optional express fee. Advances up to \)500. Uses Plaid for bank linking. MoneyLion (Instacash): Up to $500, 0% interest, but instant delivery has an optional fee. Premium tiers add subscription cost. Brigit: $9.99–\(14.99/month subscription. Advances \)25–\(250. Strong budgeting features bundled in. Earnin: Tip-based model. Advances up to \)750/pay period. Lightning Speed (instant) costs $3.99. Gerald: $0 fees across the board. Advances up to $200. BNPL commerce layer is the monetization engine. No subscription, no tips, no express fee for supported banks. From a pure fee-structure standpoint, the BNPL-gateway model is the only architecture that credibly delivers both "free" and "instant" without a subscription wrapper. The trade-off is that it requires user engagement with the commerce layer first — a product constraint worth understanding before recommending it to someone who just needs emergency cash without prior app usage.</p>
<p>What This Means If You're Building in This Sector Developers thinking about adding a cash advance feature to a consumer app should keep a few architectural considerations in mind:</p>
<p>BaaS partner selection matters enormously: Your banking partner determines which payment rails you can access, your compliance overhead, and your unit economics on instant transfers. Plaid dependency is a risk: The 2019 class action and ongoing regulatory scrutiny mean you should evaluate MX or Finicity as alternatives. The "free" claim requires a real revenue model: Regulators are increasingly skeptical of tip-based models. Build your monetization around something durable — commerce integration, subscription, or interchange on a debit card. FedNow integration is worth watching: As more banks adopt it, the cost of instant transfers may drop significantly, which could reshape the market by 2027. Fintech platforms that are winning don't just solve a UX problem — they solve a payment infrastructure problem with a sustainable business model attached. Understanding that distinction separates a product that lasts from one that burns out when VC funding dries up.</p>
<p>Evaluating these tools from a user perspective, the short answer to getting $100 or $200 instantly for free depends on your bank, your income pattern, and your willingness to engage with a commerce layer. Zero-fee models do exist — they're just built on a different revenue architecture than most people assume.</p>
]]></content:encoded></item><item><title><![CDATA[Cash Advance Apps: A Technical Analysis of Revenue Models and What They Cost You]]></title><description><![CDATA[If you've ever integrated a third-party fintech SDK or audited a consumer app's monetization layer, you know that revenue model and product architecture…]]></description><link>https://jordanhayes.hashnode.dev/cash-advance-apps-a-technical-analysis-of-revenue-models-and-what-they-cost-you</link><guid isPermaLink="true">https://jordanhayes.hashnode.dev/cash-advance-apps-a-technical-analysis-of-revenue-models-and-what-they-cost-you</guid><category><![CDATA[cash advance apps]]></category><dc:creator><![CDATA[jordanhayes]]></dc:creator><pubDate>Wed, 09 Sep 2026 16:50:17 GMT</pubDate><content:encoded><![CDATA[<p>If you've ever integrated a third-party fintech SDK or audited a consumer app's monetization layer, you know that revenue model and product architecture are deeply intertwined. These micro-lending apps are a fascinating case study in this dynamic — the way an app generates revenue directly determines what features get prioritized, what data gets collected, and ultimately, how much users pay.</p>
<p>In 2026, this market has matured into several distinct monetization archetypes. Understanding them isn't just useful for consumers — it's genuinely instructive for developers building in the fintech space. Let's break down the major models, the technical implications of each, and what they mean for users who need access to $20, $100, or $200 quickly.</p>
<p>The Four Revenue Model Archetypes After analyzing the top players in this space, most of these platforms fall into one of four revenue model categories. Each has distinct architectural fingerprints.</p>
<ol>
<li>Subscription-Gated Access Apps like Dave (ExtraCash) and MoneyLion (Instacash) use a subscription paywall to access their highest advance tiers. From an engineering perspective, this means the app's core advance logic is wrapped in an entitlement check — your subscription status is a first-class citizen in the data model, likely stored server-side and synced on session start.</li>
</ol>
<p>The UX consequence: users who don't pay the monthly fee see a degraded product. Dave charges around $1/month; MoneyLion's premium tiers can run significantly higher. The subscription model also incentivizes the product team to build features that justify recurring payment — budgeting tools, credit monitoring, banking integrations — which can be genuinely useful but also bloats the app surface area.</p>
<p>Technical tell: Look for aggressive session-start API calls and entitlement refresh logic. These apps need to know your subscription state before rendering the home screen.</p>
<ol>
<li>Tip-Encouraged Transactions EarnIn pioneered the voluntary tip model. Technically, this is elegant — there's no hard paywall, so the advance flow is simpler. But the tip prompt is a dark pattern in disguise: it's presented at the moment of highest user motivation (right before they get money), which inflates conversion on optional payments.</li>
</ol>
<p>From a revenue engineering standpoint, tip-based models require careful A/B testing infrastructure. The tip prompt UI, default tip amounts, and placement in the flow are all heavily optimized. According to research cited by the CFPB, voluntary tips on cash advance products can translate to effective APRs well above 100% when annualized — a fact the UI design isn't incentivized to surface.</p>
<p>Technical tell: Expect extensive experimentation frameworks (LaunchDarkly, Optimizely, or homegrown) and heavy analytics instrumentation around the tip step.</p>
<ol>
<li>Instant Transfer Fee Model This is the most common monetization layer across the board, even among apps that don't charge subscriptions. Standard ACH transfers are free and take 1–3 business days. Instant transfers (via push-to-debit or RTP rails) cost the user a fee — typically $1.99 to $8.99 depending on advance size.</li>
</ol>
<p>The architecture here is interesting: the app must integrate with multiple disbursement rails (ACH, Visa/Mastercard push, RTP) and present a choice that nudges users toward the paid option. Since most people requesting an advance are in an urgent situation, the conversion rate on instant fees is high. This is a classic good-better-best pricing structure implemented at the infrastructure layer.</p>
<p>Apps like Klover and FloatMe use this model. Klover offers advances up to $750 with free standard transfers, but instant delivery triggers a fee. The engineering team's incentive is to make the free option feel slow and the paid option feel essential.</p>
<ol>
<li>BNPL-Integrated Advance Model This is the most architecturally interesting model, and the one that genuinely changes the user cost equation. Rather than charging for it directly, some apps tie cash access to a Buy Now, Pay Later (BNPL) commerce layer. The advance is essentially subsidized by merchant economics — the app earns interchange or affiliate revenue when users shop through its marketplace.</li>
</ol>
<p>Gerald is the clearest example of this approach. Users shop essentials through Gerald's integrated Cornerstore (think household goods, groceries, electronics) using BNPL, and that activity grants fee-free cash advance transfers — no subscription, no tip prompts, no instant transfer fees. For developers curious about the implementation, cash advance apps built on this model require a tightly coupled commerce + advance engine, where BNPL transaction state gates advance eligibility in real time.</p>
<p>From a product architecture standpoint, this is more complex to build — you're essentially running a marketplace and a fintech product simultaneously — but it creates a genuinely different incentive alignment. The app makes money when users shop, not when users pay fees. That's a meaningful structural difference.</p>
<p>What Revenue Model Means for Advance Limits A common question is: what app will give me $200 instantly? The answer depends heavily on which revenue model the app uses, because advance limits are often tied to monetization strategy:</p>
<p>Subscription apps tend to offer higher limits to justify the monthly fee — Dave goes up to $500, MoneyLion up to $500 on Instacash. Tip-based apps like EarnIn can go up to \(150/day (\)1,000/pay period) but require verified employment and direct deposit history. Instant-fee apps often start lower ($20–$100) and increase limits over time as repayment history builds. BNPL-integrated apps like Gerald cap advances at $200 — a deliberate product decision that keeps the advance in the "bridge" category rather than competing with personal credit products. For users who need exactly $100 or \(200 to cover a gap between paychecks, the BNPL-integrated model often wins on total cost, since there are genuinely zero fees involved. For users who need \)500 quickly, subscription-gated apps may be the only option — but factor in the monthly fee when calculating true cost.</p>
<p>The Data Architecture Behind Income Verification All of these apps share a common technical requirement: income verification. Before extending any advance, the app needs to assess repayment risk. The approaches vary:</p>
<p>Plaid/MX integration: Most apps use open banking aggregators to read transaction history from the user's primary checking account. This gives them direct deposit patterns, balance history, and spending behavior. Employer verification: EarnIn goes further, verifying employment directly with employers or via GPS/timekeeping integrations for hourly workers. Behavioral scoring: Some apps build proprietary risk models on top of transaction data, incrementally increasing limits as repayment history accumulates. Notably, none of these approaches involve a traditional credit bureau pull. As Bankrate has covered extensively, cash advance apps explicitly market the no-credit-check aspect as a feature — and technically, it's accurate. The risk model is cash-flow based, not credit-score based.</p>
<p>This has regulatory implications worth watching. The CFPB has been actively examining earned wage access and cash advance products to determine whether they constitute credit under the Truth in Lending Act. How that classification lands will have significant architectural consequences for apps in this space — particularly around disclosure requirements and APR calculation.</p>
<p>Developer Takeaways If you're building in the consumer fintech space, this product category offers several useful lessons:</p>
<p>Revenue model is product architecture. The choice between subscription, tips, instant fees, or commerce-subsidized advances isn't just a business decision — it shapes every major technical component from auth flows to disbursement rails to risk models. Incentive alignment matters. Apps that make money when users pay fees are structurally incentivized to make fees feel necessary. Apps that make money through commerce are incentivized to make shopping convenient. Users (and regulators) are increasingly sophisticated about this distinction. Open banking is the foundation. Plaid, MX, and Finicity are the infrastructure layer for this entire category. If you're building anything adjacent to cash flow-based lending, your Plaid integration quality will directly affect your risk model quality. Regulatory risk is real. The CFPB's ongoing scrutiny of this space means compliance architecture needs to be first-class, not bolted on. Build disclosure and consent flows that can adapt to changing requirements. This product category is a genuinely interesting intersection of consumer behavior, financial regulation, and product engineering. The apps that will win long-term are those whose revenue models align with user outcomes — and right now, that's a much shorter list than the app stores suggest.</p>
]]></content:encoded></item></channel></rss>