Thank You For Reaching Out To Us
We have received your message and will get back to you within 24-48 hours. Have a great day!

Welcome to Haposoft Blog

Explore our blog for fresh insights, expert commentary, and real-world examples of project development that we're eager to share with you.
android-16kb-memory-page-size
latest post
Jan 08, 2026
15 min read
Android 16KB Memory Page Size: What App Owners Need to Prepare
Google Play is enforcing support for 16KB memory page size on newer Android versions. While most apps are unaffected, Android apps that use native code may fail builds or have updates rejected if they are not updated in time. From November 1st, 2025, all new Android apps and all updates to existing apps submitted to Google Play must support 16KB memory page size. Apps that do not meet this requirement may be rejected during submission, even if they previously worked. This mainly affects apps that include native code. What Is Memory Page Size and Why Android Is Changing It Memory page size is the basic unit Android uses to work with memory. For a long time, this size has effectively been 4KB, and most Android apps, especially those with native code — were built around that assumption. Developers rarely think about it because, until now, it mostly “just worked.” That’s changing as Android starts supporting 16KB memory pages on newer devices. This shift isn’t cosmetic, it’s driven by newer hardware, larger RAM sizes, and the need for more efficient memory handling at the system level. The important part for app owners is that native binaries built with old assumptions may no longer behave the same way unless they’re updated. Which Apps Are Affected by the 16KB Page Size Change This 16KB page size change does not affect every Android app. The risk is mainly tied to native code, because many native libraries were originally built with a 4KB page size assumption that may not hold on newer devices. Usually not affected Apps built purely with Java or Kotlin Apps that do not use the NDK Apps that do not bundle any native SDKs Needs to be checked Apps using the NDK or C and C++ code Apps that include .so libraries Apps using third party SDKs with native code Frameworks with native layers such as React Native, Flutter, or game engines This structure allows teams to quickly identify whether their app is likely affected without digging into low level system details. Being in the “needs to be checked” group does not mean the app is broken, but it does mean native dependencies should be reviewed before the next update. What App Owners Should Do Next For most teams, this is not a large migration project. It is a short verification and cleanup process that helps ensure future Android updates are not blocked by native compatibility issues. Check whether your app includes native code Start by confirming whether the app contains any native components. This includes NDK code written by your team, bundled .so libraries, and native binaries that come from third-party SDKs or frameworks. Even apps written mostly in Java or Kotlin can still include native code indirectly. Review native dependencies and ownership Once native code is identified, list all native artifacts used by the app, including shared libraries and SDKs. At this stage, dependencies are classified into two groups: components the team controls and components provided by third parties. This distinction determines whether an issue can be fixed by rebuilding or requires a vendor update or replacement. Update or rebuild where needed Each native dependency is checked against Android’s 16KB compatibility requirements. SDKs and frameworks are updated to versions that support the new page size where available. For self-built native code, C or C++ libraries are rebuilt using appropriate NDK configurations. If a third-party dependency does not yet support 16KB, it is flagged early so alternatives or mitigation options can be considered. Test and prepare for release After changes are applied, the app is tested in an environment that reflects 16KB page size behavior. Key user flows are verified to ensure no regressions appear at runtime. Once testing is complete, the app is ready for future updates that comply with Google Play requirements. Final Notes The 16KB page size requirement is a platform-level change that mainly impacts apps with native dependencies. The challenge is often not the fix itself, but identifying hidden native risks early enough to avoid blocked updates. To support teams at different stages, we typically help in three focused ways: Impact check to confirm whether an app is affected Native dependency review to identify upgrade or rebuild risks Targeted fixes and validation to ensure future updates can be published smoothly If you’re unsure whether your app needs changes, feel free to get in touch for an initial check.
skype-to-microsoft-teams
Apr 08, 2025
5 min read
We’re Moving from Skype to Microsoft Teams – Here’s What You Need to Know
Microsoft has officially announced that Skype will be discontinued on May 5, 2025. To ensure uninterrupted communication, Haposoft will be transitioning from Skype to Microsoft Teams, which is fully supported by Microsoft and allows for a smooth migration. Here’s everything you need to know about the change and how to continue chatting with us seamlessly. 1. Official Announcement: Skype Will Be Discontinued in May 2025 Microsoft has officially announced that Skype will be discontinued on May 5, 2025, as part of its strategy to unify communication and collaboration under Microsoft Teams. After this date: Skype will no longer be accessible on any platform No further security updates, technical support, or bug fixes will be provided Skype apps will be removed from app stores Users will be unable to sign in or use existing accounts This change affects Skype for Windows, macOS, iOS, and Android. Both personal and business users will need to make the move from Skype to Microsoft Teams. Microsoft explains that this transition aims to deliver a more modern and secure communication experience. They combine chat, meetings, file sharing, and collaboration into a unified platform. 2. What Happens to Your Skype Chat History and Contacts? Your Skype chat history and contacts will not transfer automatically unless you switch to Microsoft Teams. Microsoft has stated that some users will be able to access their Skype history in Teams if they meet all of the following conditions: You are using a Microsoft account (e.g., @outlook.com or @hotmail.com) Your Skype account is linked to that Microsoft account You have previously used Microsoft Teams with the same login If you do not meet these conditions, your data will not carry over. Additionally, files or media shared in Skype conversations will not migrate to Teams. If you need to keep any attachments, we recommend downloading them locally before May 5, 2025. 3. What Changes When You Move to Teams? When moving from Skype to Microsoft Teams, you’ll notice a shift from a simple messaging app to a full-featured collaboration platform. Teams bring together chat, video calls, meetings, file sharing, and document collaboration in one place. Here’s what’s different and better with Teams: Key Advantages of Microsoft Teams (free version) include: One-on-one and group messaging Audio and video calls (up to 30 hours per session) Group meetings (up to 60 minutes with up to 100 participants) File sharing and real-time document collaboration Cross-platform access via desktop and mobile Guest access for external participants Topic-based discussions with channels and communities Bonus: Teams also offers deep integration with Microsoft Office (Word, Excel, PowerPoint), built-in calendar tools, and features designed for teamwork—things Skype never offered. Free Plan Availability Microsoft offers a free version of Teams, which includes: Unlimited one-on-one meetings up to 30 hours Group meetings for up to 60 minutes Up to 100 participants per meeting 5 GB of cloud storage per user Real-time collaboration with Office web apps Unlimited chat and file sharing No subscription is required to get started — users can simply sign up or sign in with an existing Microsoft account. 4. How to Switch from Skype to Teams Moving from Skype to Microsoft Teams is simple. If you're already using Skype, you’ll receive in-app prompts to guide you. Just follow the instructions to complete the transition. Migration steps: Step 1 Open Skype and follow the on-screen prompts to start the transition Step 2 Confirm the move to Microsoft Teams Step 3 Sign in using your Microsoft (Skype) account Step 4 Complete setup within Teams Step 5 Start using your existing chats and contacts in Teams without any loss of data Alternatively, you can download Microsoft Teams directly via the link below: 👉 Download Microsoft Teams for desktop and mobile 5. Mobile Access Made Easy Need access on the go? Microsoft Teams is available as a mobile app for both iOS and Android. To get started: Search for “Microsoft Teams” on the App Store or Google Play Install the official app and sign in with your Microsoft account Once signed in, all your data is synced—chat, join meetings, and collaborate seamlessly from anywhere. 6. Need Help? The retirement of Skype marks a big shift for long-time users. While there are other platforms available, Microsoft Teams is the official and most compatible alternative. We recommend all clients make the switch from Skype to Microsoft Teams as early as possible to avoid any disruptions. If you need assistance at any stage of the process, feel free to contact our team at support@haposoft.com. We're here to help.
cta-background

Subscribe to Haposoft's Monthly Newsletter

Get expert insights on digital transformation and event update straight to your inbox

Let’s Talk about Your Next Project. How Can We Help?

+1 
©Haposoft 2025. All rights reserved