Holistic B2X Mobile Application Development -- A Reference Model
This paper addresses the gap between existing B2X mobile app development models and practical application by synthesizing a literature review and 28 expert interviews into a holistic reference model that guides management decisions through the integration of technical and communication processes.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to build a custom smartphone app for a business. You have a great idea, but you need a plan to turn that idea into a working product. In the world of software, these plans are called "process models."
This paper is like a detective story where the authors investigated why the "instruction manuals" written by researchers often don't work for the people actually building the apps. They found that while researchers have published dozens of different "blueprints," the people in the trenches (the developers) are mostly ignoring them or mixing and matching pieces to create their own unique solutions.
Here is the breakdown of their findings using simple analogies:
1. The Problem: Too Many Maps, No Compass
The researchers first looked at the library of existing "maps" (process models) for building apps. They found about 35 different ones, ranging from strict, step-by-step plans (like building a house where you must finish the foundation before laying bricks) to flexible, looping plans (like sculpting clay where you keep shaping it as you go).
The Reality Check: When they asked 28 experts who actually build these apps, they discovered a big gap. Most developers didn't even know these fancy maps existed. If they did use one, they rarely used it exactly as written. It's like having a cookbook with a perfect recipe for a soufflé, but the chef in the kitchen just throws ingredients in a pan because the recipe is too rigid for the busy restaurant environment.
2. The Investigation: Talking to the Builders
To understand why, the authors interviewed 28 experts (developers, project managers, and team leaders) who build "B2X" apps. "B2X" just means apps for businesses, customers, or employees (Business-to-Anything).
They found that building a mobile app is like cooking a meal on a moving train.
- The Train is the Mobile Device: The train shakes, the tracks change (different phone models), and the weather outside changes (new software updates from Apple or Google).
- The Meal is the App: You need to serve it hot and fresh.
- The Challenge: If you try to follow a rigid recipe (a strict plan) while the train is shaking, you'll spill the soup. You need a flexible approach that can adapt when the train hits a bump.
3. The Solution: The "REMOB" Blueprint
Since no single existing map worked perfectly, the authors built a new, holistic guide called REMOB. Think of this not as a strict rulebook, but as a four-layer cake that covers everything you need to consider.
Here are the four layers, from the bottom up:
Layer 1: The Management Layer (The Captain of the Ship)
This is about the people in charge. The study found that if the "Captain" (management) doesn't understand the rules of the game, the crew gets confused.- The Metaphor: Imagine a captain who tells the crew to "sail fast and be flexible," but then demands a written log of every single wave every hour. This kills the flexibility. The study says management needs to trust the team and understand that mobile apps need to change quickly, not just follow a rigid schedule.
Layer 2: The Requirements Layer (The Blueprint of the House)
This is about what the app actually needs to do and look like.- The Metaphor: Building a house for a person with big hands is different than for someone with small hands. Similarly, an app for a phone screen needs to be tested on the actual phone, not just on a computer screen. The authors found that you can't just guess; you have to test the "feel" of the app on the real device early on, because what looks good on a computer might be impossible to tap with a finger on a phone.
Layer 3: The Process Layer (The Construction Crew's Routine)
This is the actual method used to build the app.- The Metaphor: The study found that most teams use a method called Scrum (which is like a series of short, focused sprints). However, they rarely use it "purely."
- The Twist: Sometimes, you need a strict plan (like for banking apps where security is everything), and sometimes you need a flexible plan (like for a lifestyle app). The best teams are "hybrids." They might use a flexible sprint system but add a strict "safety check" step for security. They mix the "Scrum" recipe with a little bit of "Waterfall" (the strict plan) to get the best of both worlds.
Layer 4: The Communication Layer (The Walkie-Talkies)
This is about how everyone talks to each other.- The Metaphor: Imagine a construction site where the architect, the electrician, and the plumber are all shouting over each other, or worse, not talking at all. The study found that developers often want to just "code" and ignore the talking. But in mobile apps, the person designing the look (the UI) and the person writing the code need to talk constantly. If the designer draws a button that is too small, the coder needs to know before they build it. The study says constant, honest communication is the glue that holds the project together.
4. The Big Takeaway
The paper concludes that there is no "one size fits all" instruction manual for building mobile apps. The old, rigid academic models are too stiff for the fast-moving world of mobile technology.
Instead, the authors propose REMOB as a checklist for success. It reminds everyone involved—from the boss to the coder—to:
- Make sure management supports the team's flexibility.
- Test on real phones, not just computers.
- Mix and match planning methods (hybridize) based on the specific project.
- Keep the lines of communication open between everyone.
In short, building a successful mobile app isn't about following a perfect textbook recipe; it's about having a flexible framework that adapts to the shaking train of the mobile world.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.