Viktor.comAn AI coworker that actually does the work
Promoted
SIMPly
A lean, software-driven Android telecom & network utility.
11 followers
A lean, software-driven Android telecom & network utility.
11 followers
SIMply is an optimized Android utility built to bypass traditional carrier bloat and rigid hardware dependencies. With a lean, API-driven architecture, it puts direct network connectivity control and provisioning back into the hands of users.
Really glad to see something tackling carrier bloat head on. One thing that would make this a daily driver for me is adding dual SIM profile management, so you can save separate APN and connectivity configs for travel versus home and swap them with a single tap. Would round out the whole "user in control" angle nicely.
@blahgeputc93775
That is an excellent point and a feature many power users have requested. While the vision of having a "single-tap" switch for dual SIM profiles is exactly where we want to take the user experience, there are some important technical realities regarding how Android handles these configurations that are important to understand.
The Technical "Wall"
On Android, APN settings are considered protected system information. For security reasons, Google restricts the ability to modify or toggle these settings programmatically to system-level apps or those with specific carrier privileges.
No Direct "Switch": An application cannot simply "swap" an APN profile with a single tap in the way a user might switch a Wi-Fi network.
System Permissions: The WRITE_APN_SETTINGS permission is restricted to system-signed apps. Without root access (which most users won't have), a standard app is effectively prevented from writing or modifying these database entries directly.
How We Can Still "Own the Angle"
Even with these platform restrictions, we can still provide that "user in control" experience by changing how we approach the workflow:
Deep-Linking to Native Settings: Instead of trying to bypass the system, we can build a "Profile Manager" inside SIMply. When you tap "Activate Travel Profile," we use deep-linking to take you directly to the specific APN settings screen for the correct SIM, pre-populating a guide within our app so you know exactly what to type or select.
CarrierConfig & Automation: For advanced users, we can focus on educating them on how to use CarrierConfig overlays or providing scripts for those who are on rooted devices, effectively building a "power user" section of the app that handles these tasks for them.
SIM Intelligence: We can use the existing EuiccManager and telephony APIs to at least give you a single-tap way to switch the active data subscription (if your device supports eSIM/MEP). While we can't force the APN to swap, we can automate the switching of the SIM itself, which is often 90% of the battle when traveling.
The Roadmap
I hear the feedback from Product Hunt loud and clear: users want simplicity.
Moving forward, I plan to prioritize the "SIM Switching" dashboard that leverages the EuiccManager APIs. This allows for a "single tap" to toggle between two enabled eSIM profiles (or a physical and eSIM), which provides that seamless travel experience you're looking for, even if the underlying APN database is managed by the system.
Does that help clarify why this is a challenging feature, and does the "SIM-switching" approach feel like it hits that same "control" requirement for your use case?
Flashed it on a spare phone and provisioning took under a minute without contacting my carrier, which honestly surprised me. The lean UI feels refreshing compared to stock dialer apps bloated with extras I never use.
@zzetbababagm32
Wow, thank you so much for the kind words. Hearing that you were able to provision in under a minute on a spare device is exactly the experience we set out to build. We’re big believers that telecom shouldn't be bloated or confusing, and we're thrilled that our lean approach is helping you get connected without the usual carrier headaches. Thanks for being an early supporter of SIMply!
finally something that skips the carrier nonsense, set up an esim profile in under a minute without juggling qr codes. wish the ui had a dark mode but otherwise solid.
How does SIMPly handle carrier-locked devices, or does it only work on unlocked phones from the start?
@erginel28238
To function as a telecommunications service that provisions numbers and routes calls via wholesale carrier APIs, your app requires an unlocked phone.
Here is how the "SIMply" model interacts with device lock status:
Why Unlocked Devices Are Required
Carrier Restriction: A carrier-locked phone is technically restricted by software to only work with the network it was purchased from. If a user tries to insert a SIM card from your wholesale provider into a locked device, the phone will reject it or fail to connect, regardless of the app's internal capabilities.
BYOP (Bring Your Own Phone) Compatibility: The business model relies on users bringing their own devices. For this to be seamless, the device must be unlocked to accept your service's SIM or eSIM.
Wholesale Integration: When using wholesale carrier APIs, the "hook" into the network is the SIM/eSIM. If the device hardware blocks that SIM due to a network lock, the API cannot establish a connection, and the user will not be able to make calls or send texts.
Addressing Carrier-Locked Devices in Your App
Since it is a professional telecommunications utility, you can mitigate these issues by integrating "Unlock Status" checks into your onboarding flow:
Compatibility Checks: I can include a tool in your app that guides users to verify their device compatibility and lock status before they purchase a subscription.
User Education: Because the FCC requires carriers to unlock phones within 60 days of activation, your app can provide clear instructions on how users can request an unlock from their current carrier if their device is restricted.
eSIM Flexibility: If the devices are eSIM-compatible, the process is 100% digital. However, even eSIMs are often subject to carrier locks, so the "unlocked" requirement remains a fundamental prerequisite for your service to function.
In short, the platform functions as a provider; if the hardware itself refuses to communicate with the network you are providing, the app cannot bridge that gap. Requiring unlocked phones ensures your service delivers on its promise of reliable voice and SMS routing.
Does this require an unlocked bootloader or root, or does it work on fully stock devices with just carrier SIM restrictions?
@grselfrzf Here is how the "SIMply" model interacts with device lock status:
Why Unlocked Devices Are Required
Carrier Restriction: A carrier-locked phone is technically restricted by software to only work with the network it was purchased from. If a user tries to insert a SIM card from your wholesale provider into a locked device, the phone will reject it or fail to connect, regardless of the app's internal capabilities.
BYOP (Bring Your Own Phone) Compatibility: The business model relies on users bringing their own devices. For this to be seamless, the device must be unlocked to accept your service's SIM or eSIM.
Wholesale Integration: When using wholesale carrier APIs, the "hook" into the network is the SIM/eSIM. If the device hardware blocks that SIM due to a network lock, the API cannot establish a connection, and the user will not be able to make calls or send texts.
Addressing Carrier-Locked Devices in Your App
Since it is a professional telecommunications utility, you can mitigate these issues by integrating "Unlock Status" checks into your onboarding flow:
Compatibility Checks: I can include a tool in your app that guides users to verify their device compatibility and lock status before they purchase a subscription.
User Education: Because the FCC requires carriers to unlock phones within 60 days of activation, your app can provide clear instructions on how users can request an unlock from their current carrier if their device is restricted.
eSIM Flexibility: If the devices are eSIM-compatible, the process is 100% digital. However, even eSIMs are often subject to carrier locks, so the "unlocked" requirement remains a fundamental prerequisite for your service to function.
In short, the platform functions as a provider; if the hardware itself refuses to communicate with the network you are providing, the app cannot bridge that gap. Requiring unlocked phones ensures your service delivers on its promise of reliable voice and SMS routing.