<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Insights and News covering Mobile App Development | Glance</title>
    <link>https://thisisglance.com/blog</link>
    <description>If you're looking for the latest news and expert opinions on the tech industry, check out our blog posts, where we discuss app development and more.</description>
    <language>en</language>
    <pubDate>Mon, 19 Jan 2026 09:00:00 GMT</pubDate>
    <dc:date>2026-01-19T09:00:00Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>When Saying No to Investors Is the Smartest Move</title>
      <link>https://thisisglance.com/blog/when-saying-no-to-investors-is-the-smartest-move</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/when-saying-no-to-investors-is-the-smartest-move" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/when-saying-no-to-investors-is-the-smartest-move.webp" alt="When Saying No to Investors Is the Smartest Move" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;What would you do if an investor offered you £500,000 for 40% of your app business, but the terms included veto rights over hiring decisions and forced you to hit aggressive growth targets that would mean compromising your product quality? Over the past ten years of building apps at Glance, I've watched plenty of founders jump at investment offers that looked brilliant on paper, only to find themselves locked into agreements that made their business almost impossible to run the way they'd originally envisioned. The pressure to secure funding can make any offer feel like a lifeline, but turning down investment money is often the smarter decision for long-term success and happiness as a founder.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/when-saying-no-to-investors-is-the-smartest-move" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/when-saying-no-to-investors-is-the-smartest-move.webp" alt="When Saying No to Investors Is the Smartest Move" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;What would you do if an investor offered you £500,000 for 40% of your app business, but the terms included veto rights over hiring decisions and forced you to hit aggressive growth targets that would mean compromising your product quality? Over the past ten years of building apps at Glance, I've watched plenty of founders jump at investment offers that looked brilliant on paper, only to find themselves locked into agreements that made their business almost impossible to run the way they'd originally envisioned. The pressure to secure funding can make any offer feel like a lifeline, but turning down investment money is often the smarter decision for long-term success and happiness as a founder.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhen-saying-no-to-investors-is-the-smartest-move&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Mon, 19 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/when-saying-no-to-investors-is-the-smartest-move</guid>
      <dc:date>2026-01-19T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Your Best Feature Idea Might Be Your Worst Business Decision</title>
      <link>https://thisisglance.com/blog/why-your-best-feature-idea-might-be-your-worst-business-decision</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-best-feature-idea-might-be-your-worst-business-decision" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-best-feature-idea-might-be-your-worst-business-decision.webp" alt="Why Your Best Feature Idea Might Be Your Worst Business Decision" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A dating app company spent six months building a video chat feature after users kept requesting it in feedback surveys. They launched it to great fanfare, complete with a PR campaign and featured placement on their home screen. Three months later, less than two percent of their active users had tried it even once, and engagement with their core matching features had dropped by fourteen percent because the interface had become cluttered and confusing. The feature cost them £140k to build and was quietly removed in a subsequent update.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-best-feature-idea-might-be-your-worst-business-decision" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-best-feature-idea-might-be-your-worst-business-decision.webp" alt="Why Your Best Feature Idea Might Be Your Worst Business Decision" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A dating app company spent six months building a video chat feature after users kept requesting it in feedback surveys. They launched it to great fanfare, complete with a PR campaign and featured placement on their home screen. Three months later, less than two percent of their active users had tried it even once, and engagement with their core matching features had dropped by fourteen percent because the interface had become cluttered and confusing. The feature cost them £140k to build and was quietly removed in a subsequent update.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-your-best-feature-idea-might-be-your-worst-business-decision&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Thu, 15 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-your-best-feature-idea-might-be-your-worst-business-decision</guid>
      <dc:date>2026-01-15T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Push Notification Mistakes That Kill User Engagement</title>
      <link>https://thisisglance.com/blog/push-notification-mistakes-that-kill-user-engagement</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/push-notification-mistakes-that-kill-user-engagement" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/push-notification-mistakes-that-kill-user-engagement.webp" alt="Push Notification Mistakes That Kill User Engagement" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Push notifications can be one of the most powerful tools for keeping users engaged with your app... but they can also be one of the fastest ways to get people to uninstall it. After ten years of building apps for clients in healthcare, fintech, and ecommerce, I've seen businesses make the same mistakes over and over again, and the data doesn't lie when it comes to how quickly users will abandon an app that annoys them with poorly thought-out notifications.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/push-notification-mistakes-that-kill-user-engagement" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/push-notification-mistakes-that-kill-user-engagement.webp" alt="Push Notification Mistakes That Kill User Engagement" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Push notifications can be one of the most powerful tools for keeping users engaged with your app... but they can also be one of the fastest ways to get people to uninstall it. After ten years of building apps for clients in healthcare, fintech, and ecommerce, I've seen businesses make the same mistakes over and over again, and the data doesn't lie when it comes to how quickly users will abandon an app that annoys them with poorly thought-out notifications.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fpush-notification-mistakes-that-kill-user-engagement&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Tips</category>
      <category>Marketing</category>
      <category>Mobile App Strategy</category>
      <pubDate>Wed, 14 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/push-notification-mistakes-that-kill-user-engagement</guid>
      <dc:date>2026-01-14T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Mobile App Regulatory Approval: 5 Critical Steps to Success</title>
      <link>https://thisisglance.com/blog/mobile-app-regulatory-approval-5-critical-steps-to-success</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/mobile-app-regulatory-approval-5-critical-steps-to-success" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/mobile-app-regulatory-approval-5-critical-steps-to-success.webp" alt="Mobile App Regulatory Approval: 5 Critical Steps to Success" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A sports fitness app spent eighteen months building a platform that tracked athlete performance data and connected users with personal trainers. The development went smoothly, the interface looked great, and early beta testers loved it. They launched in the UK without any regulatory checks, and within six weeks they received a letter from the Information Commissioner's Office flagging serious data protection issues. The app was storing health data without proper consent mechanisms, sharing information with third parties without clear documentation, and using analytics tools that weren't compliant with GDPR. They had to pull the app from the store, rebuild core features, and delay their European expansion by eight months... all because they treated regulatory approval as an afterthought rather than a core part of the development process.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/mobile-app-regulatory-approval-5-critical-steps-to-success" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/mobile-app-regulatory-approval-5-critical-steps-to-success.webp" alt="Mobile App Regulatory Approval: 5 Critical Steps to Success" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A sports fitness app spent eighteen months building a platform that tracked athlete performance data and connected users with personal trainers. The development went smoothly, the interface looked great, and early beta testers loved it. They launched in the UK without any regulatory checks, and within six weeks they received a letter from the Information Commissioner's Office flagging serious data protection issues. The app was storing health data without proper consent mechanisms, sharing information with third parties without clear documentation, and using analytics tools that weren't compliant with GDPR. They had to pull the app from the store, rebuild core features, and delay their European expansion by eight months... all because they treated regulatory approval as an afterthought rather than a core part of the development process.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fmobile-app-regulatory-approval-5-critical-steps-to-success&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Mobile App Strategy</category>
      <category>Legal</category>
      <category>Mobile App Development</category>
      <pubDate>Tue, 13 Jan 2026 21:44:40 GMT</pubDate>
      <guid>https://thisisglance.com/blog/mobile-app-regulatory-approval-5-critical-steps-to-success</guid>
      <dc:date>2026-01-13T21:44:40Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Most App Funding Rounds Fail (And How to Win)</title>
      <link>https://thisisglance.com/blog/why-most-app-funding-rounds-fail-and-how-to-win</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-most-app-funding-rounds-fail-and-how-to-win" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-most-app-funding-rounds-fail-and-how-to-win.webp" alt="Why Most App Funding Rounds Fail (And How to Win)" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;More than half of all funding rounds for app startups never close, and a good portion of founders give up after their first serious rejection from investors. This failure rate stays high across seed rounds through Series A, and the pattern repeats itself with different teams making the same mistakes year after year. After watching dozens of funding attempts from both sides of the table (and helping clients prepare their own pitches), the issues that derail these deals are surprisingly predictable, which means they're also preventable if you know what to look for.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-most-app-funding-rounds-fail-and-how-to-win" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-most-app-funding-rounds-fail-and-how-to-win.webp" alt="Why Most App Funding Rounds Fail (And How to Win)" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;More than half of all funding rounds for app startups never close, and a good portion of founders give up after their first serious rejection from investors. This failure rate stays high across seed rounds through Series A, and the pattern repeats itself with different teams making the same mistakes year after year. After watching dozens of funding attempts from both sides of the table (and helping clients prepare their own pitches), the issues that derail these deals are surprisingly predictable, which means they're also preventable if you know what to look for.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-most-app-funding-rounds-fail-and-how-to-win&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Business</category>
      <category>Strategy</category>
      <category>Startups</category>
      <pubDate>Tue, 13 Jan 2026 14:16:18 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-most-app-funding-rounds-fail-and-how-to-win</guid>
      <dc:date>2026-01-13T14:16:18Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Your Development Team Keeps Missing Deadlines</title>
      <link>https://thisisglance.com/blog/why-your-development-team-keeps-missing-deadlines</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-development-team-keeps-missing-deadlines" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-development-team-keeps-missing-deadlines.webp" alt="Why Your Development Team Keeps Missing Deadlines" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Around 75% of software development projects fail to meet their original deadlines, and mobile app projects tend to run even later than traditional software builds. Having spent a decade building apps across healthcare, fintech and e-commerce sectors, I can tell you that late deliveries are rarely about lazy developers or unrealistic clients... they're about a collection of predictable problems that keep showing up on nearly every project, and most people don't spot them until the timeline has already blown out by weeks or months.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-development-team-keeps-missing-deadlines" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-development-team-keeps-missing-deadlines.webp" alt="Why Your Development Team Keeps Missing Deadlines" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Around 75% of software development projects fail to meet their original deadlines, and mobile app projects tend to run even later than traditional software builds. Having spent a decade building apps across healthcare, fintech and e-commerce sectors, I can tell you that late deliveries are rarely about lazy developers or unrealistic clients... they're about a collection of predictable problems that keep showing up on nearly every project, and most people don't spot them until the timeline has already blown out by weeks or months.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-your-development-team-keeps-missing-deadlines&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Tue, 13 Jan 2026 11:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-your-development-team-keeps-missing-deadlines</guid>
      <dc:date>2026-01-13T11:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Your App's Biggest Competitor Isn't Who You Think</title>
      <link>https://thisisglance.com/blog/why-your-apps-biggest-competitor-isnt-who-you-think</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-apps-biggest-competitor-isnt-who-you-think" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-apps-biggest-competitor-isnt-who-you-think.webp" alt="Why Your App's Biggest Competitor Isn't Who You Think" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When we run competitor analysis workshops with new clients, most arrive with a list of apps that look similar to theirs... but after a decade of building apps across healthcare, fintech and retail, I can tell you that the apps stealing your users aren't always the ones you've mapped out on your competitive matrix. The real competition often comes from places that won't show up in any app store search, and missing this can mean spending six months building features that solve the wrong problem entirely.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-apps-biggest-competitor-isnt-who-you-think" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-apps-biggest-competitor-isnt-who-you-think.webp" alt="Why Your App's Biggest Competitor Isn't Who You Think" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When we run competitor analysis workshops with new clients, most arrive with a list of apps that look similar to theirs... but after a decade of building apps across healthcare, fintech and retail, I can tell you that the apps stealing your users aren't always the ones you've mapped out on your competitive matrix. The real competition often comes from places that won't show up in any app store search, and missing this can mean spending six months building features that solve the wrong problem entirely.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-your-apps-biggest-competitor-isnt-who-you-think&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Marketing</category>
      <category>Mobile App Strategy</category>
      <category>Strategy</category>
      <pubDate>Tue, 13 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-your-apps-biggest-competitor-isnt-who-you-think</guid>
      <dc:date>2026-01-13T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Your App Keeps Getting Rejected Over Privacy Settings</title>
      <link>https://thisisglance.com/blog/why-your-app-keeps-getting-rejected-over-privacy-settings</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-app-keeps-getting-rejected-over-privacy-settings" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-app-keeps-getting-rejected-over-privacy-settings.webp" alt="Why Your App Keeps Getting Rejected Over Privacy Settings" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;App store rejections for privacy issues have become one of the most frustrating roadblocks for developers, and I've watched this problem grow steadily worse over the past five years as both Apple and Google have tightened their requirements. The rejection email usually arrives within 48 hours of submission (sometimes within minutes if the automated systems catch something obvious), and the explanation often feels vague or confusing, leaving you wondering what exactly went wrong with your privacy implementation. I've probably walked about 50 different clients through this exact situation, and the pattern is always the same... they thought they'd covered everything, ticked all the boxes during submission, but still got that dreaded "we've identified one or more issues with your submission" message. The frustration compounds when you're working to a deadline, when you've got users waiting for features, when every day of delay costs money in development resources and missed market opportunities.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-app-keeps-getting-rejected-over-privacy-settings" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-app-keeps-getting-rejected-over-privacy-settings.webp" alt="Why Your App Keeps Getting Rejected Over Privacy Settings" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;App store rejections for privacy issues have become one of the most frustrating roadblocks for developers, and I've watched this problem grow steadily worse over the past five years as both Apple and Google have tightened their requirements. The rejection email usually arrives within 48 hours of submission (sometimes within minutes if the automated systems catch something obvious), and the explanation often feels vague or confusing, leaving you wondering what exactly went wrong with your privacy implementation. I've probably walked about 50 different clients through this exact situation, and the pattern is always the same... they thought they'd covered everything, ticked all the boxes during submission, but still got that dreaded "we've identified one or more issues with your submission" message. The frustration compounds when you're working to a deadline, when you've got users waiting for features, when every day of delay costs money in development resources and missed market opportunities.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-your-app-keeps-getting-rejected-over-privacy-settings&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>App Store</category>
      <category>Privacy</category>
      <category>Mobile App Development</category>
      <pubDate>Tue, 13 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-your-app-keeps-getting-rejected-over-privacy-settings</guid>
      <dc:date>2026-01-13T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>OWASP API Security Risks Every Mobile Developer Must Know</title>
      <link>https://thisisglance.com/blog/owasp-api-security-risks-every-mobile-developer-must-know</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/owasp-api-security-risks-every-mobile-developer-must-know" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/owasp-api-security-risks-every-mobile-developer-must-know.webp" alt="OWASP API Security Risks Every Mobile Developer Must Know" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Apps with security flaws are rejected by Apple and Google at rates that have tripled in recent years, and the main culprit behind most of these rejections is poor API security. I've been building mobile apps for a decade now, and I can tell you that API security has gone from being an afterthought to being one of the first things we discuss with every client. The truth is that most data breaches in mobile apps happen not because of sophisticated hacking techniques, but because developers overlook basic security principles that OWASP has been documenting for years. You might build the most beautiful app with perfect functionality, but if your API security has holes in it then you're essentially leaving the back door wide open for anyone who knows where to look.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/owasp-api-security-risks-every-mobile-developer-must-know" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/owasp-api-security-risks-every-mobile-developer-must-know.webp" alt="OWASP API Security Risks Every Mobile Developer Must Know" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Apps with security flaws are rejected by Apple and Google at rates that have tripled in recent years, and the main culprit behind most of these rejections is poor API security. I've been building mobile apps for a decade now, and I can tell you that API security has gone from being an afterthought to being one of the first things we discuss with every client. The truth is that most data breaches in mobile apps happen not because of sophisticated hacking techniques, but because developers overlook basic security principles that OWASP has been documenting for years. You might build the most beautiful app with perfect functionality, but if your API security has holes in it then you're essentially leaving the back door wide open for anyone who knows where to look.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fowasp-api-security-risks-every-mobile-developer-must-know&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Technical</category>
      <category>Security</category>
      <category>Mobile App Development</category>
      <pubDate>Tue, 13 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/owasp-api-security-risks-every-mobile-developer-must-know</guid>
      <dc:date>2026-01-13T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
    <item>
      <title>Why Your CFO Keeps Saying No to Your App Budget</title>
      <link>https://thisisglance.com/blog/why-your-cfo-keeps-saying-no-to-your-app-budget</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-cfo-keeps-saying-no-to-your-app-budget" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-cfo-keeps-saying-no-to-your-app-budget.webp" alt="Why Your CFO Keeps Saying No to Your App Budget" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A retail fashion brand spent £140k building a mobile shopping app that promised to boost revenue by thirty percent within the first year. Six months after launch, the app had been downloaded only eight thousand times and generated less than £12k in sales... the CFO blocked every technology budget request for the next eighteen months, and the marketing director who championed the project left the company shortly after. Your chief financial officer isn't being difficult when they push back on your app budget, they're protecting the business from what they've learned are high-risk investments that rarely deliver the returns promised in those glossy pitch decks.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://thisisglance.com/blog/why-your-cfo-keeps-saying-no-to-your-app-budget" title="" class="hs-featured-image-link"&gt; &lt;img src="https://thisisglance.com/hubfs/article-images/why-your-cfo-keeps-saying-no-to-your-app-budget.webp" alt="Why Your CFO Keeps Saying No to Your App Budget" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A retail fashion brand spent £140k building a mobile shopping app that promised to boost revenue by thirty percent within the first year. Six months after launch, the app had been downloaded only eight thousand times and generated less than £12k in sales... the CFO blocked every technology budget request for the next eighteen months, and the marketing director who championed the project left the company shortly after. Your chief financial officer isn't being difficult when they push back on your app budget, they're protecting the business from what they've learned are high-risk investments that rarely deliver the returns promised in those glossy pitch decks.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=26870616&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fthisisglance.com%2Fblog%2Fwhy-your-cfo-keeps-saying-no-to-your-app-budget&amp;amp;bu=https%253A%252F%252Fthisisglance.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Business</category>
      <category>Financial</category>
      <category>Mobile App Development</category>
      <pubDate>Tue, 13 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://thisisglance.com/blog/why-your-cfo-keeps-saying-no-to-your-app-budget</guid>
      <dc:date>2026-01-13T09:00:00Z</dc:date>
      <dc:creator>Simon Lee</dc:creator>
    </item>
  </channel>
</rss>
