Fext
Fext is a subscription-based messaging app that enables users to send personalized, one-on-one SMS messages at scale. Designed for professionals, event organizers, and community leaders, Fext combines the convenience of group messaging with the personal feel of direct communication, eliminating the chaos of reply-all emails and the clutter of group threads.
All CustomersManual Testing
QAwerk delivered thorough manual testing for Fext’s iOS app, covering critical messaging flows, contact imports, and complex device configurations. By uncovering high-impact functional issues and enhancing UX, we enabled Fext to move towards a stable, user-friendly launch across multiple iOS versions and screen sizes.
Learn moreiOS App Testing
For Fext, we tested real-world user flows, such as contact imports, personalized templates, and mass SMS delivery, on five different devices and three iOS versions. Our QA team uncovered critical bugs, UX gaps, and compatibility issues, helping Fext deliver a stable, high-performance iOS app ready for App Store submission.
Learn moreChallenge
Fext approached QAwerk ahead of their anticipated iOS launch, recognizing critical gaps in their internal QA capabilities. The Fext team—though skilled at development—lacked a dedicated tester as well as access to a comprehensive range of test devices. This meant that essential scenarios, edge cases, and device compatibility risks could easily be missed, threatening user experience and product reputation at launch.
The project’s objectives centered on three major focus areas:
- Delivering Quality at Scale: With a product built for mass, personalized SMS delivery, it was vital to guarantee that every message, regardless of group size, template usage, or contact import method, would be sent without error. The absence of reply-all confusion and proper handling of international phone formats were crucial.
- Ensuring Wide-Ranging Compatibility: Fext needed assurance that its app would perform consistently across evolving iOS versions and popular Apple device types, from iPhone mini screens to the latest iPad Pro. This required hands-on testing with real hardware, various SIMs, and locale-specific phone numbers to catch compatibility and UX issues before release.
- Minimizing Launch Risks: The Fext team wanted peace of mind that no critical bugs, performance bottlenecks, or clumsy user experiences would impact early adopters or undermine App Store approval. With no in-house QA resources, they needed an external partner with a structured approach to thorough test coverage, actionable reporting, and user-oriented feedback.
Solution
QAwerk approached Fext’s project with a focus on delivering launch-ready software quality and device compatibility. Given the client’s need for robust, real-world validation, our QA team designed a collaborative, transparent, and methodical process:
- Conducted a thorough review of Fext’s functionality and messaging logic, ensuring all key scenarios, such as group size variation, phone number input, and message templating, were identified for coverage.
- Developed detailed test documentation, including a comprehensive checklist and tailored test data (multiple formats, phone numbers, and import files) to simulate real user behavior.
- Executed 100+ manual test cases across 5 Apple devices, representing today’s most-used iPhone and iPad models and spanning relevant iOS versions, to maximize user coverage.
- Tested with 30 phone numbers from US and EU regions, verifying international formats, mass delivery scenarios, SIM card compatibility, and MMS support.
- Reported and tracked all findings in Jira, producing clear bug reports and actionable user experience suggestions for the Fext team.
- Collaborated closely with the client, providing ongoing feedback to ensure that device-specific issues and user experience gaps were addressed prior to App Store submission.
This iterative and systematic QA process allowed Fext to identify critical bugs before launch, strengthen the app’s cross-device stability, and guarantee that the user experience remained smooth and personal, even at scale.
Bugs Found
During QAwerk’s comprehensive testing of the Fext app, we encountered multiple functional bugs across critical messaging, onboarding, template management, and contact import flows on iOS devices.
Actual result: The message sent to another device is received on the same device.
Expected result: The message should be delivered only to Device 2.
Actual result: The message template with an added picture is saved twice—one copy is untitled.
Expected result: Only one saved template appears, with the given title and message.
Actual result: The app crashes, blocking users who store contact data in Excel format.
Expected result: The file is parsed, and the user proceeds to the field mapping screen. If the format is unsupported, a clear error message should display.
Result
QAwerk’s comprehensive testing enabled Fext to resolve numerous critical bugs before public release, resulting in a substantial reduction in launch risk and post-launch incident rates. According to industry benchmarks, pre-release QA that covers >100 custom scenarios across multiple devices can reduce user-reported bugs by up to 70% and cut support tickets by as much as 50% in the first 90 days after launch.
This not only protects Fext’s reputation and App Store ratings, but also reduces operational costs and accelerates user adoption—helping the business launch confidently, avoid costly post-release fixes, and deliver a streamlined, trustworthy mass messaging solution.
Want a rock-steady iOS launch?
Let’s TalkTools
BrowserStackQAwerk Team Comments
Kristina
Project Manager
Coordinating Fext’s QA project was all about clear priorities, open communication, and agility. By aligning our daily progress with the client’s key launch deadlines, we ensured efficient test execution, quick bug triage, and real-time feedback. The collaboration was fast-paced and transparent, giving the Fext team full confidence that their app would be stable, user-friendly, and ready for App Store review.
Maryna
QA Engineer
We focused on maximizing coverage within the required deadline—validating message delivery, international phone formats, and handling scenarios like mass messaging and contact imports. Every bug found and every test case written brought Fext closer to a successful launch.”












Related in Our Blog
Test Early, Test Smart: Software Testing Phases Explained
Software testing isn’t just a box to tick before launch—it’s a strategic process that scales with your product. If you miss the right testing phase, there’s a risk of bugs in production, slipping deadli...
Read More
15 AI Testing Tools for Smarter Testing in 2025
AI in software testing has become ubiquitous. In 2024, 72% of companies used AI in at least one business function, which is a substantial jump from the 55% we saw the year before. Nearly every tool now leverage...
Read MoreImpressed?
Contact Us TodayOther Related Case Studies
DrAnsay
Set up manual and test automation workflows for online prescription platform, resulting in 15% increase in orders.
BeFamily
We ensured this app had a zero-bug product launch, tripling their projected install numbers
ICONOMI
Optimized the web and mobile onboarding flow for a crypto asset management platform, reducing user drop-off by 15%
