<?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 ASTRO LAB TECH on Medium]]></title>
        <description><![CDATA[Stories by ASTRO LAB TECH on Medium]]></description>
        <link>https://medium.com/@edabdallamo?source=rss-9d0e3e371a93------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*22w7ZaIyQntAJBBHP-ztmg.jpeg</url>
            <title>Stories by ASTRO LAB TECH on Medium</title>
            <link>https://medium.com/@edabdallamo?source=rss-9d0e3e371a93------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:22:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edabdallamo/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[Stop hardcoding temperature units. Let Apple’s APIs do it for you.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@edabdallamo/stop-hardcoding-temperature-units-let-apples-apis-do-it-for-you-e8f441edfbe8?source=rss-9d0e3e371a93------2"><img src="https://cdn-images-1.medium.com/max/2600/0*aruUjqhedxljA0KQ" width="5288"></a></p><p class="medium-feed-snippet">A tiny Swift pattern that makes your weather UI locale-aware with zero extra logic.</p><p class="medium-feed-link"><a href="https://medium.com/@edabdallamo/stop-hardcoding-temperature-units-let-apples-apis-do-it-for-you-e8f441edfbe8?source=rss-9d0e3e371a93------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@edabdallamo/stop-hardcoding-temperature-units-let-apples-apis-do-it-for-you-e8f441edfbe8?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8f441edfbe8</guid>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Fri, 10 Apr 2026 04:20:55 GMT</pubDate>
            <atom:updated>2026-04-10T04:20:55.998Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Integrating Firebase Analytics into a SwiftUI App: A Developer’s Thought Process]]></title>
            <link>https://medium.com/@edabdallamo/integrating-firebase-analytics-into-a-swiftui-app-a-developers-thought-process-b27945668bc3?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/b27945668bc3</guid>
            <category><![CDATA[daily-thoughts]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[swiftui]]></category>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 07:11:43 GMT</pubDate>
            <atom:updated>2025-10-23T07:11:43.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0vM0gLLXQ4YxHpJf" /><figcaption>Photo by <a href="https://unsplash.com/@dengxiangs?utm_source=medium&amp;utm_medium=referral">Deng Xiang</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In this blog post, I want to walk you through my thought process for adding Firebase Analytics into a SwiftUI app. Whether you’re just starting out or looking for a straightforward approach, here’s how I did it.</p><h3>Setting the Stage</h3><p>First, the main goal was to keep things as clean and maintainable as possible. I knew I wanted to use SwiftUI’s environment to make the analytics service easily accessible throughout the app. This way, I wouldn’t have to inject it manually into every single view.</p><h3>Steps to Integrate Firebase</h3><p><strong>1-Setting Up Firebase:</strong><br> Start by adding Firebase to your Xcode project. You’ll need to create a Firebase project in the Firebase console, download the GoogleService-Info.plist file, and include it in your app. Then, use FirebaseApp.configure() in your app’s initialization (usually in the App struct or an AppDelegate if you have one).</p><p><strong>2-Creating an Analytics Service:</strong><br> I designed a simple analytics service class to wrap around Firebase’s calls. This service can have methods like logEvent that you can call from anywhere in your app. It’s kind of like having a neat little utility that talks to Firebase for you.</p><p><strong>3-Using the Environment Object:</strong><br> To make the analytics service available throughout the app, I used SwiftUI’s environment. By attaching the analytics service as an environment object, any view can access it without having to pass it through initializers or create it anew.</p><h3>Final Thoughts</h3><p>This approach made it super easy to keep the code flexible. If I ever want to switch from Firebase to another analytics provider in the future, all I need to do is update the service class. The rest of the app doesn’t have to change at all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b27945668bc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Toolbar to Floating Action Button: Simplifying My App’s UI/UX]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@edabdallamo/from-toolbar-to-floating-action-button-simplifying-my-apps-ui-ux-7db5796e7656?source=rss-9d0e3e371a93------2"><img src="https://cdn-images-1.medium.com/max/2600/1*_x7kdZvcmgiCouvw1HJoMQ@2x.jpeg" width="3240"></a></p><p class="medium-feed-snippet">Photo by Alvaro Reyes on Unsplash</p><p class="medium-feed-link"><a href="https://medium.com/@edabdallamo/from-toolbar-to-floating-action-button-simplifying-my-apps-ui-ux-7db5796e7656?source=rss-9d0e3e371a93------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@edabdallamo/from-toolbar-to-floating-action-button-simplifying-my-apps-ui-ux-7db5796e7656?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/7db5796e7656</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 05:13:57 GMT</pubDate>
            <atom:updated>2025-10-16T05:13:57.275Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Swift Combine: Hot vs Cold Publishers Explained with an Uber Analogy]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@edabdallamo/swift-combine-hot-vs-cold-publishers-explained-with-an-uber-analogy-8e8e4b65ccf9?source=rss-9d0e3e371a93------2"><img src="https://cdn-images-1.medium.com/max/2600/0*1HFz3A9dR7oxCExr" width="5751"></a></p><p class="medium-feed-snippet">When learning Combine, one confusing part is understanding the difference between hot and cold publishers. Let&#x2019;s make it simple by&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@edabdallamo/swift-combine-hot-vs-cold-publishers-explained-with-an-uber-analogy-8e8e4b65ccf9?source=rss-9d0e3e371a93------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@edabdallamo/swift-combine-hot-vs-cold-publishers-explained-with-an-uber-analogy-8e8e4b65ccf9?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e8e4b65ccf9</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 23:43:15 GMT</pubDate>
            <atom:updated>2025-09-04T23:43:15.522Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Avoid the “Build Trap” as an Indie Developer]]></title>
            <link>https://medium.com/@edabdallamo/how-to-avoid-the-build-trap-as-an-indie-developer-5b5c04201d2d?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b5c04201d2d</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Mon, 19 May 2025 22:10:40 GMT</pubDate>
            <atom:updated>2025-05-19T22:10:40.432Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wn7G-Co7rB75lCNQf1ZrqQ@2x.jpeg" /><figcaption>Photo by <a href="http://danielkorpai.com/">Daniel Korpai</a> on<a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral"> Unsplas</a>h</figcaption></figure><p>When you’re building an app solo, it’s easy to fall into the build trap – adding features just because you can, not because users need them. The freedom of being your own boss also means there’s no product manager telling you to slow down, no QA team pushing back, and no customer success agent passing on feedback. It’s just you, your ideas, and the endless temptation to build more.</p><p>But more isn’t always better.</p><p>In this post, we’ll explore how to avoid the build trap as an indie developer – and how to focus your energy where it really matters.</p><p><strong>What Is the Build Trap?</strong></p><p>The “build trap” is a common problem in software development. It happens when you:</p><p>•	Ship features without validating if users want them</p><p>•	Add complexity that increases maintenance without adding real value</p><p>•	Focus more on shipping something rather than solving real problems</p><p>The result? A bloated app, confused users, and wasted effort.</p><p>Why Indie Developers Are at Higher Risk</p><p>Solo developers are especially vulnerable because:</p><p>•	There’s no one to challenge your assumptions</p><p>•	You often don’t have access to product analytics or user research</p><p>•	You may equate productivity with adding new features</p><p>•	You don’t get much direct feedback – especially early on</p><p>So how do you stay focused?</p><ol><li><strong>Start With a Problem, Not a Feature</strong></li></ol><p>Before building anything, ask yourself:</p><p>What user problem does this solve?</p><p>If you can’t answer that clearly in one sentence, don’t build it yet.</p><p>Start with pain points – something users struggle with or can’t do today. The best features are solutions to real problems, not ideas that “might be cool.”</p><p><strong>2. Validate Before You Build</strong></p><p>You don’t need a huge user base to validate an idea. Try:</p><p>•	Mockups or Figma prototypes</p><p>•	Quick polls or surveys on Reddit, Twitter, or Discord</p><p>•	Asking friends or niche communities</p><p>•	App store reviews of similar apps (see what users complain about)</p><p>Even one or two responses from potential users can save you hours of wasted development.</p><p><strong>3. Look at Your Data – If You Have It</strong></p><p>If your app is live, check:</p><p>•	Are people using the feature you’re thinking of improving?</p><p>•	Is there a drop-off in certain flows?</p><p>•	Do users abandon onboarding or skip parts of the app?</p><p>If you don’t have analytics yet, adding something simple like Firebase Analytics or Mixpanel can help validate future decisions.</p><p><strong>4. Make It Easy for Users to Talk to You</strong></p><p>Many solo devs don’t hear from users simply because they haven’t made it easy.</p><p>Add:</p><p>•	A feedback button in your app</p><p>•	An email address in the settings screen</p><p>•	A simple prompt: “What’s missing in this app?”</p><p>Tools like Wishkit.io let users submit feature requests directly inside your app.</p><p><strong>5. Improve What You Already Have</strong></p><p>Before building something new, ask:</p><p>Is there a way to improve what’s already in the app?</p><p>Sometimes the biggest gains come from refining existing features – improving usability, fixing friction points, or enhancing performance.</p><p><strong>6. Prioritize Like a Product Manager</strong></p><p>Every feature has a cost – code to write, bugs to fix, time to maintain.</p><p>Use this simple framework:</p><p>•	Must-have (user can’t function without it)</p><p>•	Nice-to-have (enhances experience)</p><p>•	Waste-of-time (adds clutter)</p><p>Prioritize only the top few and park the rest in a “maybe later” list.</p><p>Final Thoughts</p><p>As an indie dev, your time is your most precious resource. Avoiding the build trap means staying laser-focused on what actually improves the user experience – and saying “no” to ideas that don’t serve that goal.</p><p>Remember: a smaller app that solves a real problem wins over a bloated one that tries to do everything.</p><p>Have you ever fallen into the build trap? What helped you climb out of it? Let’s share stories and help each other build better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b5c04201d2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Why I Built a Tactical Sports App for Coaches (and What Makes It Different)]]></title>
            <link>https://medium.com/@edabdallamo/why-i-built-a-tactical-sports-app-for-coaches-and-what-makes-it-different-eb675381948a?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb675381948a</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Fri, 16 May 2025 01:50:56 GMT</pubDate>
            <atom:updated>2025-05-17T15:31:42.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D3XSRZ_USl8H5g3r" /><figcaption>Photo by <a href="https://unsplash.com/@akeenster?utm_source=medium&amp;utm_medium=referral">Abigail Keenan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>⚽🏀 Coaching Tools That Actually Help: Why I Built These Tactical Whiteboard Apps</h3><p>As a solo developer and lifelong sports fan, I wanted to build something <strong>useful</strong> — something coaches and trainers could actually rely on during real sessions.<br> Whether you’re on the sidelines of a youth match, prepping drills in the gym, or sketching last-minute plays before kickoff — <strong>you need tools that are fast, clear, and easy to use</strong>.</p><p>That’s exactly why I created these apps:</p><ul><li><strong>Strike (Soccer)</strong></li><li><strong>Strike Lite (Free Version)</strong></li><li><strong>Hoop Coach Board (Basketball)</strong></li></ul><p>Each one is a <strong>lightweight, no-fluff tactical whiteboard</strong> that helps coaches stay organized, communicate better, and focus on the game — not the tech.</p><h3>🛠 The Problem I Set Out to Solve</h3><p>Too many sports apps are:</p><ul><li>Bloated with features most coaches never use</li><li>Locked behind paywalls and monthly subscriptions</li><li>Frustrating to use in real-time or offline</li></ul><p>I wanted to do the opposite.</p><p>So I built something that:</p><ul><li><strong>Loads instantly</strong></li><li><strong>Works 100% offline</strong></li><li><strong>Keeps things simple and useful</strong></li><li><strong>Costs only $4.99 — forever</strong></li></ul><p>Whether you’re organizing a formation or explaining player movement, it just works.</p><h3>⚙️ What Can the App Do?</h3><ul><li>🧲 <strong>Drag and Drop Players</strong> — Quickly place players on the field or court</li><li>✍️ <strong>Draw Plays with Your Finger or Pencil</strong> — Mark passes, runs, zones, or pressure areas</li><li>💾 <strong>Save &amp; Reuse Tactics</strong> — Plan ahead or revisit strategies later</li><li>📤 <strong>Export to Image</strong> — Share plans with assistants, teammates, or parents</li><li>🌐 <strong>Offline-Ready</strong> — No Wi-Fi needed — great for on-the-go coaching</li><li>💸 <strong>One-Time Price</strong> — Just $4.99 USD to unlock full access, forever</li></ul><h3>💡 What Makes It Different?</h3><p>I focused on real <strong>value for coaches</strong>:</p><ul><li>Designed with <strong>SwiftUI</strong> for modern performance</li><li>Optimized for <strong>iPhone &amp; iPad</strong>, including older models</li><li>Localized in <strong>8+ languages</strong>, so it’s usable worldwide</li><li>No accounts. No tracking. No cloud. Just your tactics, your way</li></ul><p>You open the app → plan the play → close it. That’s it.<br> You’re not dealing with ads or paywalls — you’re focused on coaching.</p><h3>🙌 A One-Dev Project Made for Real Coaches</h3><p>There’s no studio or startup behind this — just me.<br> No investors. No ads. No subscriptions. Just practical tools made with care.</p><p>If you’re a coach who values clarity and speed, I’d love to hear what you think.</p><p>Try one of the apps below. The free version works out of the box. If you like it, grab the full version — it’s my way of keeping things simple and accessible.</p><p>Thanks for reading. More importantly, <strong>thanks for coaching</strong>.</p><h3>📲 Download the Apps</h3><p><strong>Strike — Soccer Coach</strong><br> <a href="https://apps.apple.com/us/app/strike-soccer-coach/id6742800434">https://apps.apple.com/us/app/strike-soccer-coach/id6742800434</a></p><p><strong>Strike Lite — Free Version</strong><br> <a href="https://apps.apple.com/us/app/strike-lite-soccer-coach/id6745530915">https://apps.apple.com/us/app/strike-lite-soccer-coach/id6745530915</a></p><p><strong>Hoop Coach Board — Basketball</strong><br> <a href="https://apps.apple.com/us/app/hoop-basketball-coach/id6744208421">https://apps.apple.com/us/app/hoop-basketball-coach/id6744208421</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb675381948a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Battery Usage in Your iOS App: A Comprehensive Guide]]></title>
            <link>https://medium.com/@edabdallamo/optimizing-battery-usage-in-your-ios-app-a-comprehensive-guide-8203cb074b8a?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/8203cb074b8a</guid>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 22:32:44 GMT</pubDate>
            <atom:updated>2024-10-21T22:32:44.472Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uTj1EDaXxFnLNhHfK0uOGg@2x.jpeg" /></figure><p>In today’s mobile-centric world, users expect their apps to be not only feature-rich and responsive but also energy-efficient. An app that drains battery life quickly is likely to be uninstalled, leading to poor user retention and negative reviews. As developers, it’s our responsibility to build apps that are both powerful and power-efficient.</p><p>In this blog post, we’ll explore strategies and best practices to optimize battery usage in your iOS app. We’ll delve into understanding energy consumption, leveraging system resources wisely, and utilizing tools provided by Apple to monitor and reduce your app’s energy footprint.</p><p>Understanding Energy Consumption in iOS Apps</p><p>Before diving into optimization techniques, it’s crucial to understand how apps consume energy. The primary contributors to battery drain in iOS apps are:</p><p>•	CPU Usage: Intensive computations and inefficient algorithms can spike CPU usage.</p><p>•	Networking: Frequent or inefficient network requests consume energy due to radio usage.</p><p>•	Location Services: Continuous GPS usage is a significant battery drain.</p><p>•	Graphics and Animations: High frame rates and complex rendering tasks tax the GPU.</p><p>•	Background Activities: Unnecessary tasks running in the background can deplete battery life.</p><p>Understanding these factors helps in identifying areas where your app can improve.</p><p>Best Practices for Battery Optimization</p><ol><li>Optimize CPU Usage</li></ol><p>Efficient Algorithms</p><p>•	Optimize Code: Write efficient algorithms and avoid unnecessary computations.</p><p>•	Avoid Busy Waiting: Do not use loops to wait for events; use callbacks or delegates instead.</p><p>•	Leverage Multithreading Wisely: Use background threads for heavy tasks, but avoid creating too many threads.</p><p>Batch Processing</p><p>•	Batch Tasks: Combine multiple small tasks into a single batch to reduce the number of wake-ups.</p><p>•	Deferred Processing: Delay non-critical tasks to times when the device is plugged in or connected to Wi-Fi.</p><p>2. Manage Network Usage</p><p>Efficient Networking</p><p>•	Reduce Network Calls: Minimize the number of network requests by caching responses and using data compression.</p><p>•	Optimize Data Transfers: Send only necessary data and use efficient data formats like JSON over XML.</p><p>•	Background Fetch: Use NSURLSession with background configuration to handle network tasks efficiently.</p><p>Handle Connectivity Changes</p><p>•	Reachability Checks: Monitor network status to prevent failed requests that waste energy.</p><p>•	Adaptive Polling: Adjust the frequency of network requests based on the network conditions.</p><p>3. Use Location Services Judiciously</p><p>Select Appropriate Accuracy</p><p>•	Desired Accuracy: Use the lowest acceptable accuracy level for your app’s functionality.</p><p>•	Distance Filter: Set a minimum distance filter to avoid unnecessary updates.</p><p>Geofencing and Significant Location Changes</p><p>•	Geofencing: Use geofences to trigger location updates only when the user enters or leaves specified regions.</p><p>•	Significant Location Change Monitoring: Opt for significant location change monitoring over standard location services when high accuracy isn’t needed.</p><p>4. Optimize Graphics and Animations</p><p>Efficient Rendering</p><p>•	Frame Rate: Limit animations to 30 FPS if 60 FPS isn’t necessary.</p><p>•	Idle Timer: Disable screen updates when the app isn’t in active use.</p><p>Use Appropriate APIs</p><p>•	Metal and SceneKit: Utilize high-performance graphics APIs for rendering.</p><p>•	Image Formats: Use image formats that are efficient to decode, like PNGs for simple images.</p><p>5. Handle Background Activities Efficiently</p><p>Background Modes</p><p>•	Opt-in Wisely: Only enable background modes that are essential for your app.</p><p>•	Background Tasks: Use BGTaskScheduler to manage background tasks efficiently.</p><p>Notifications</p><p>•	Silent Notifications: Use silent push notifications sparingly, as they wake up the app.</p><p>•	Notification Payloads: Keep payloads small to reduce processing time.</p><p>6. Leverage System Frameworks</p><p>Energy-Efficient APIs</p><p>•	Combine Operations: Use APIs that allow batching of tasks, like OperationQueue.</p><p>•	System Services: Utilize services like Core Data and CloudKit that are optimized for performance and energy efficiency.</p><p>Adaptive Strategies</p><p>•	Low Power Mode Awareness: Check if the device is in Low Power Mode and adjust your app’s behavior accordingly.</p><p>•	Thermal State Monitoring: Use ProcessInfo to monitor the device’s thermal state and reduce activity during high thermal states.</p><p>Testing and Profiling Tools</p><p>Optimization without measurement is guesswork. Apple provides robust tools to help you profile and understand your app’s energy usage.</p><p>Instruments</p><p>•	Energy Log: Use the Energy Log instrument to monitor your app’s energy impact over time.</p><p>•	Time Profiler: Identify CPU-intensive methods and optimize them.</p><p>•	Network Instruments: Analyze network traffic to detect inefficient networking patterns.</p><p>Xcode Energy Reports</p><p>•	Energy Organizer: Access energy reports in Xcode to see how your app performs over time and under different conditions.</p><p>•	Diagnostic Tools: Utilize Xcode’s diagnostics to detect issues like excessive wake-ups or high CPU usage.</p><p>Testing on Real Devices</p><p>•	Device Testing: Always test on actual devices rather than simulators, as they provide accurate energy usage data.</p><p>•	Varied Conditions: Test under different network conditions, battery levels, and device states.</p><p>Optimizing battery usage is a critical aspect of mobile app development that directly affects user satisfaction and retention. By understanding how your app consumes energy and employing best practices to reduce its impact, you can create apps that delight users without draining their batteries.</p><p>Remember, optimization is an ongoing process. Continuously profile your app, stay updated with the latest iOS developments, and refine your strategies to ensure your app remains energy-efficient in the ever-evolving mobile landscape.</p><p>Thank you for reading! If you found this guide helpful, feel free to share it with fellow developers. For more insights into iOS development, stay tuned to our blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8203cb074b8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surviving a Layoff in 2024: Turning Adversity into Opportunity]]></title>
            <link>https://medium.com/@edabdallamo/surviving-a-layoff-in-2024-turning-adversity-into-opportunity-ad39b0b4ecd8?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad39b0b4ecd8</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Sat, 14 Sep 2024 21:58:56 GMT</pubDate>
            <atom:updated>2024-09-14T21:58:56.880Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEvGc4fJ4Z64N8NTAG0W0Q@2x.jpeg" /><figcaption>Photo by Slava Auchynnikau on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In 2023, many developers have faced unexpected layoffs due to economic shifts and industry changes. While this can be a challenging experience, it’s important to remember that a layoff can also be an opportunity for growth and self-discovery. Here’s how you can navigate this period effectively and turn it into a stepping stone for future success.</p><p><strong>1.Reflect and Reassess</strong></p><p>The first step after a layoff is to take a moment for self-reflection. Use this time to evaluate your career goals and aspirations. Ask yourself what you enjoyed most about your previous role and what aspects you’d like to change. Reflecting on these questions can help you identify what you truly want in your next position and guide your job search.</p><p><strong>2. Update Your Skills</strong></p><p>A layoff provides a unique chance to enhance your skill set. Identify any gaps in your knowledge and consider taking online courses or attending workshops. Whether it’s learning a new programming language or mastering a new tool, upskilling can make you more competitive in the job market and open doors to new opportunities.</p><p><strong>3. Network Strategically</strong></p><p>Networking is crucial during a job search. Reach out to former colleagues, join industry groups, and attend meetups or virtual events. Engaging with your professional community can lead to valuable connections and job leads. Don’t hesitate to let your network know that you’re looking for new opportunities; often, the best jobs come through referrals.</p><p><strong>4. Revise Your Resume and Online Profiles</strong></p><p>Ensure your resume and LinkedIn profile reflect your most recent experiences and accomplishments. Highlight any projects or achievements that demonstrate your skills and value. Tailoring your resume for each application can increase your chances of catching the eye of recruiters.</p><p><strong>5. Stay Positive and Persistent</strong></p><p>A layoff can be emotionally taxing, but maintaining a positive mindset is key. Rejections are part of the process, so stay persistent and keep applying. Remember, each application and interview is a step closer to finding the right opportunity.</p><p><strong>6. Explore Freelancing or Contract Work</strong></p><p>If a full-time role isn’t immediately available, consider freelancing or contract work. These opportunities can provide income while allowing you to build new skills and expand your network. They might also lead to permanent positions in the future.</p><p><strong>7. Seek Support</strong></p><p>Don’t hesitate to seek support from friends, family, or career counselors. Talking through your challenges can provide emotional relief and practical advice. Many professionals have faced layoffs and can offer valuable insights based on their experiences.</p><p><strong>8. Plan for the Future</strong></p><p>Use this time to set long-term career goals. Consider where you want to be in five or ten years and plan how to get there. Setting clear objectives can provide direction and motivation during your job search.</p><p>While a layoff is undoubtedly a difficult experience, it can also serve as a catalyst for personal and professional growth. By reflecting on your goals, updating your skills, networking effectively, and maintaining a positive outlook, you can turn this challenge into a valuable opportunity. Embrace the change and use it to find a role that better aligns with your career aspirations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad39b0b4ecd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The “Devil Programmer” vs. The “Clean Coder”: Two Sides of the Developer Coin]]></title>
            <link>https://medium.com/@edabdallamo/the-devil-programmer-vs-the-clean-coder-two-sides-of-the-developer-coin-6a0cf8b5f4be?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a0cf8b5f4be</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Wed, 04 Sep 2024 07:11:40 GMT</pubDate>
            <atom:updated>2024-09-04T07:11:40.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnHyXMpkdt4JQjeEKL_2GQ@2x.jpeg" /><figcaption>Photo by charlesdeluvio on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the software development world, different types of developers emerge depending on their approach to coding and problem-solving. Two contrasting archetypes often come up in discussions: the “Devil Programmer” and the “Clean Coder.” These two represent opposite philosophies in how they approach the art of software creation. Let’s explore both and how their distinct characteristics impact software projects.</p><p>The “Devil Programmer”: Fast but Unforgiving</p><p>The “Devil Programmer” is a term used to describe a developer who works with incredible speed and often appears to be a coding genius. They are the ones who can churn out features or fix bugs seemingly in the blink of an eye. However, their work style can often come with significant downsides. Here are a few key characteristics of the Devil Programmer:</p><p>1.	Speed Over Quality: They value speed above all else. If there’s a problem to solve, they’ll find a quick way to fix it, often through brute force. They love shortcuts and hacks that can get things working, even if it makes the code messy or hard to understand.</p><p>2.	Focus on Immediate Results: Devil Programmers are often driven by short-term success. Getting the job done in the moment is what counts to them. They thrive in fast-paced environments where immediate impact is valued, and long-term maintenance is an afterthought.</p><p>3.	Sacrifice of Code Maintainability: In the rush to solve problems, code maintainability is not a top concern. Their code may work in the short run but can become a nightmare to maintain, debug, or extend later. Other developers might find their code cryptic and difficult to follow.</p><p>4.	Hero Syndrome: Devil Programmers are often seen as “heroes” for swooping in and fixing things quickly. While they can seem indispensable in the moment, their style may lead to more technical debt and issues in the future.</p><p>The “Clean Coder”: Quality Over Speed</p><p>On the opposite end of the spectrum is the “Clean Coder,” also known as a “Craftsman Programmer.” Clean Coders take a methodical, disciplined approach to software development. Their focus is on writing clean, understandable, and maintainable code. Here are the key traits of a Clean Coder:</p><p>1.	Quality Over Speed: Clean Coders believe that writing quality code from the start is more efficient in the long run. They take the time to ensure their code is easy to read, scalable, and free from unnecessary complexity.</p><p>2.	Emphasis on Long-Term Value: They think about the future. Instead of quick fixes, they focus on solutions that will stand the test of time. This means they’re often writing code that is modular, well-documented, and easy to maintain.</p><p>3.	Testing and Best Practices: Clean Coders write code with testing in mind. Unit tests, integration tests, and code reviews are part of their daily workflow. They follow best practices such as the SOLID principles, separation of concerns, and design patterns to ensure their code is maintainable and robust.</p><p>4.	Collaboration and Readability: The Clean Coder values collaboration and writes code that is readable and understandable by the entire team. They recognize that code is read far more than it’s written, so they prioritize making their code as simple and straightforward as possible. Their goal is to make the codebase a collaborative environment, where everyone can contribute easily.</p><p>The Impact on Projects</p><p>Both Devil Programmers and Clean Coders can play significant roles in software projects, but their approaches lead to very different outcomes:</p><p>•	Short-Term vs. Long-Term Gains: Devil Programmers may deliver results quickly, which can be beneficial in crisis situations or for rapid prototyping. However, this can lead to technical debt and more work down the road as quick fixes pile up and the code becomes difficult to manage. Clean Coders, on the other hand, deliver slower but more stable and scalable code that leads to fewer bugs and smoother project maintenance in the long term.</p><p>•	Collaboration vs. Individualism: Devil Programmers often work independently, relying on their own knowledge to fix things. This can create bottlenecks if their code is difficult for others to understand or maintain. Clean Coders prioritize collaboration, ensuring that the code they write can be easily picked up by other team members, making the project more inclusive and scalable.</p><p>•	Crisis Management vs. Sustainable Development: In an environment where deadlines are tight and time is of the essence, the Devil Programmer’s speed can be an asset. However, if this becomes the default mode of operation, the project may suffer from long-term instability. Clean Coders, while slower, ensure that the software is built on a solid foundation, preventing future crises from arising due to poorly written code.</p><p>Striking a Balance: The Ideal Developer</p><p>While it’s easy to think of these two archetypes as opposites, the ideal developer strikes a balance between the two. Sometimes, speed is critical, and the quick, dirty fix is necessary. However, it’s also important to know when to step back, refactor, and focus on writing clean, sustainable code.</p><p>Developers who can blend the positive traits of both the Devil Programmer and the Clean Coder are invaluable. They understand when to move fast and when to slow down, document, and test thoroughly.</p><p>Here are a few ways to achieve this balance:</p><p>1.	Know When to Be Fast: If you’re working on a throwaway prototype or trying to meet a tight deadline, it’s okay to adopt a “Devil Programmer” mindset. Just be conscious that this is a temporary measure.</p><p>2.	Refactor and Clean Up: Once the immediate crisis has passed, take the time to refactor your code. Make it clean, modular, and testable. This shift toward “Clean Coder” principles ensures that your project stays healthy in the long run.</p><p>3.	Test Your Limits: Practice writing clean, elegant code quickly. Challenge yourself to solve problems in a sustainable way without sacrificing speed. Over time, this will help you move faster while maintaining high standards.</p><p>Both Devil Programmers and Clean Coders have a place in the development ecosystem. However, it’s the developer who can balance speed with quality, short-term needs with long-term sustainability, who will thrive in today’s fast-paced yet increasingly complex software landscape.</p><p>Strive to be a Clean Coder at heart, but don’t be afraid to channel your inner Devil Programmer when the situation calls for it. Knowing when to adopt each mindset is what separates a good developer from a great one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a0cf8b5f4be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a SwiftUI Widget with a ViewModel: A Step-by-Step Tutorial]]></title>
            <link>https://medium.com/@edabdallamo/creating-a-swiftui-widget-with-a-viewmodel-a-step-by-step-tutorial-61f5c7cc9d54?source=rss-9d0e3e371a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/61f5c7cc9d54</guid>
            <dc:creator><![CDATA[ASTRO LAB TECH]]></dc:creator>
            <pubDate>Wed, 07 Aug 2024 04:25:39 GMT</pubDate>
            <atom:updated>2024-12-02T02:59:36.859Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R4aFvNLyWrUYRVXB" /><figcaption>Photo by <a href="https://unsplash.com/@casparrubin?utm_source=medium&amp;utm_medium=referral">Caspar Camille Rubin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In this tutorial, we’ll create a widget similar to the one in a rideshare or delivery app that displays the last trip information. We’ll use SwiftUI for the UI and MVVM (Model-View-ViewModel) architecture to manage the data.</p><h4>Step 1: Setting Up Your SwiftUI Project</h4><p>First, create a new SwiftUI project in Xcode:</p><ol><li>Open Xcode and select “Create a new Xcode project”.</li><li>Choose the “App” template under iOS.</li><li>Name your project and ensure “SwiftUI” is selected as the interface, and “Swift” is selected as the language.</li><li>Click “Next” and then “Create”.</li></ol><h4>Step 2: Creating the ViewModel</h4><p>The ViewModel will manage the data and logic for our widget. We’ll create a new class that conforms to the ObservableObject protocol.</p><ol><li>Create a new Swift file in your project and name it LastTripViewModel.swift.</li><li>Add the following code to define the ViewModel:</li></ol><pre>import SwiftUI<br><br>class LastTripViewModel{<br>var amount: String<br>var time: String<br>var points: Int<br>    <br>    init(amount: String, time: String, points: Int) {<br>        self.amount = amount<br>        self.time = time<br>        self.points = points<br>    }<br>    <br>    // Add any additional logic or data fetching methods here<br>}</pre><h4>Step 3: Creating the Widget View</h4><p>Next, we’ll create the SwiftUI view that will use this ViewModel to display the data.</p><ol><li>Create a new Swift file in your project and name it LastTripWidget.swift.</li><li>Add the following code to define the view:</li></ol><pre>import SwiftUI<br><br>struct LastTripWidget: View {<br>    @ObservedObject var viewModel: LastTripViewModel<br>    <br>    var body: some View {<br>        VStack {<br>            Text(viewModel.amount)<br>                .font(.title)<br>                .fontWeight(.bold)<br>                .foregroundColor(.green)<br>                .padding(.top, 10)<br>            <br>            Text(&quot;LAST TRIP&quot;)<br>                .font(.headline)<br>                .padding(.top, 5)<br>            <br>            Text(&quot;Today at \(viewModel.time)&quot;)<br>                .font(.subheadline)<br>                .foregroundColor(.gray)<br>            <br>            HStack {<br>                Text(&quot;Delivery&quot;)<br>                Image(systemName: &quot;diamond.fill&quot;)<br>                    .foregroundColor(.orange)<br>                Text(&quot;\(viewModel.points) points&quot;)<br>            }<br>            .font(.subheadline)<br>            .padding(.bottom, 10)<br>            <br>            Divider()<br>            <br>            Text(&quot;SEE EARNINGS ACTIVITY&quot;)<br>                .font(.headline)<br>                .padding(.vertical, 10)<br>        }<br>        .frame(width: 250)<br>        .background(Color.white)<br>        .cornerRadius(15)<br>        .shadow(radius: 10)<br>    }<br>}</pre><h4>Step 4: Integrating the Widget into the Main View</h4><p>Now we’ll integrate the LastTripWidget into our main view, ContentView.</p><ol><li>Open ContentView.swift and modify it as follows:</li></ol><pre>import SwiftUI<br><br>struct ContentView: View {<br>    @StateObject private var viewModel = LastTripViewModel(amount: &quot;$4.01&quot;, time: &quot;7:23 p.m.&quot;, points: 3)<br>    <br>    var body: some View {<br>        Spacer()<br>        VStack {<br>            LastTripWidget(viewModel: viewModel)<br>                .padding()<br>            <br>            Spacer()<br>        }<br>        .background(Color(.systemGray6))<br>        .edgesIgnoringSafeArea(.all)<br>    }<br>}<br><br>#Preview {<br>    ContentView()<br>}</pre><p>In this code, we:</p><ul><li>Create an instance of LastTripViewModel using @StateObject.</li><li>Pass this instance to the LastTripWidget view.</li></ul><h4>Step 5: Running the App</h4><p>Build and run your app. You should see a widget that displays the last trip’s amount, time, and points. The widget should look similar to the one in the screenshot you provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hd961mk0XqiOi-09E2TwHg.png" /></figure><p>In this tutorial, we created a SwiftUI widget using the MVVM architecture. We defined a ViewModel to manage our data and a SwiftUI view to display it. This approach helps keep our code organized and makes it easier to manage the state and data of our views. You can now expand on this by adding more features and logic to your ViewModel or customizing the UI further. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61f5c7cc9d54" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>