Break Free from VDI Vendor Lock-in with Cameyo

Proud of pushing the norm once more 👏👏 If you haven't, check the Fairphone Gallery as an alternative to the Photos app (https://lnkd.in/eR28vq84) Built with the community, for the community + User friendly + Works not only on Fairphone devices + No ads + No bloat + No unnecessary "gimmicky" AI features + No user data tracking + Your photos stay only yours + It is open-source Read the full article here: https://lnkd.in/eGXjEMAD

Here's how we built the Fairphone Gallery app 🤳🏼 How do you design software aligned with sustainable and privacy-focused values? We share in this post (see the link in the comment) the design story behind the newly built Fairphone Gallery app. In an era dominated by cloud dependencies, intrusive tracking, and unnecessary feature bloat, we took a minimal, user-centric approach to local media management with an offline-first architecture to ensure absolute user privacy by keeping media strictly on-device without cloud sync dependencies. It was engineered to be lightweight, preserving both storage overhead and device longevity. 🙌🏻 And rather than building an app completely from scratch behind closed doors, we turned to the open-source ecosystem... if you want to know more, read the full post linked in the comment 👇🏻 Thanks Eduardo Pinar Menoyo Jeroen Keij for making this happen 👐🏾

THE PAIN: Slow SaaS applications kill user experience. Users expect instant responses, not lag. THE INSIGHT: This slowness often stems from repeatedly fetching the same data from the backend. Every request incurs network latency and server processing time. We forget that desktop apps have immediate access to local data. THE FIX: Implement caching strategically. * Cache frequently accessed, less volatile data client-side. * Consider server-side caching for common query results. * Use appropriate cache invalidation strategies. THE OUTCOME: Responsiveness. Familiarity. A SaaS that feels like a desktop app. Faster interactions. Happier users. #SaaSOptimization #PerformanceEngineering #Caching #WebPerformance

We are building apps faster than ever. But nobody is sticking around to use them. The problem is there are no unique solutions! Let us explain how #MobileAppDevelopment #AppDevelopment #UserRetention #ProductManagement #AppDev #US #BUSINESS

170+ app targets. One CI/CD pipeline. Zero Macs required to trigger a release. That's what our release process looks like now at Mobiuso. It didn't start that way. We had a suite of 170+ app targets across healthcare, education, and construction (the Medpresso suite). Every release meant someone tracking down a free Mac, opening Xcode, and running it manually, one target at a time. I configured per-target Xcode Cloud workflows across the whole suite. Now any teammate, technical or not, triggers a release straight from a browser. No Mac, no Xcode, no waiting on whoever's laptop was free that day. The CI/CD config was the easy part. The harder part was realizing the bottleneck was never the code. It was that shipping depended on one specific machine being available. What's the single point of failure in your release process right now? #iOSDev #SwiftUI #MobileEngineering

"Make sure it looks good on mobile." I hear this every time I build software. But judging a web app purely on a phone screen misses a massive reality: Desktop users and mobile users are NOT the same. When someone opens your web app on a laptop, they are usually: • At work or focused on a desk • Looking to solve a serious problem • Tech-savvy power users who value deep workflows over simple tapping Most importantly? Desktop power users are usually the first ones to pull out a credit card and pay. Mobile users want fast, passive consumption. Desktop users want leverage, speed, and productivity. That’s why I almost always build for desktop first. I treat desktop as the ultimate proof of concept. If power users love the product, see the value, and pay for it—then optimize and streamline it for mobile. Stop crippling powerful desktop tools just to make them look like simple phone feeds. Build for the people actually doing the work. Are you building mobile-first or desktop-first? Let’s debate below. 👇 #WebDevelopment #ProductDesign #SaaS #SoftwareEngineering #StartupStrategy #BuildInPublic

The Next Mobile Performance Upgrade May Start With Architecture—not Optimization. As apps expand across phones, foldables, tablets, and resizable windows, UI architecture has to become adaptive by design. Jetpack Compose Material 3 Adaptive now provides patterns for list-detail and supporting-pane experiences based on window configuration. Flutter is moving in a similar direction. Its 2026 roadmap emphasizes Impeller, native-level performance, multiplatform quality, and multi-window support. But adaptive UI alone isn't enough. A scalable mobile architecture should keep state, business logic, rendering, navigation, and platform concerns loosely coupled. That makes it easier to change layouts without creating another layer of technical debt. Then validate the result with production data. Firebase Performance Monitoring can track startup time, rendering, network requests, and custom traces across Android and Flutter. The goal isn't simply to make apps faster. It's to make performance predictable as the product grows. 💬 What architectural decision has had the biggest impact on your app's performance? #Android #Flutter #JetpackCompose #Firebase #MobileEngineering #MobileArchitecture #PerformanceEngineering #AdaptiveUI #SoftwareArchitecture #EngineeringLeadership #DeveloperExperience

A useful tool i learned about on Reddit and now I get to see the author. This saves so much time when drawing network diagrams!

Are you looking for an alternative to #Visio? This summer I started to vibe this app together, #Drawbridge. I didn't like how all applications #network #architects was flowchart apps, focusing on that type of diagrams. So I started to build #Drawbridge from scratch, making it compatible with both #Drawio and #Visio files, making the conversion simple. The app also contains a good set of general icons so the need for messy 3rd party or vendor just isn't there. The app itself runs either locally as an app on your computer (100% offline, no data leakage) or directly in your browser (No data lands on the server). It's currently in beta with quite a rapid development of versions, so feel free to join in and be a part of the development. Link is in the comments!

The Mobile Architecture Advantage Is Becoming Multi-Window Ready. The mobile app is no longer guaranteed to live inside one full-screen window. Flutter is actively expanding multi-window and multi-view capabilities, while Android and Jetpack Compose continue evolving adaptive layouts for larger and resizable surfaces. That changes how we should design mobile systems. A screen-centric architecture can work well—until product requirements introduce split-screen, foldables, tablets, desktop windows, or multiple views. Strong architecture keeps state, business logic, navigation, and UI responsibilities separated so the same product can adapt without duplicating logic. Performance should evolve with it. Flutter’s Impeller focuses on predictable rendering performance, while Firebase Performance Monitoring lets teams create alerts around real production metrics. The future isn't “mobile vs desktop.” It's one product adapting across surfaces. 💬 Is your current architecture ready for multiple windows—or still optimized for one screen? #Android #Flutter #JetpackCompose #Firebase #MobileEngineering #MobileArchitecture #PerformanceEngineering #AdaptiveUI #Multiplatform #EngineeringLeadership #StartupEngineering #DeveloperExperience