For a private project I want to create a purely platform-independent conceptual design for a native mobile app that – in the end – can be used for a platform-specific (Android and/or iOS) implementation.
As preliminary consideration for the data and information architecture I would
-
use different UML-diagrams for describing the back-end (like data storage, pseudo-classes & class-members, data exchange between class instances and methods) and
-
use wireframes, high fidelity mockups and an interactive prototype for describing the GUI.
For visualization purposes and saving time I would lay out the GUI-design for one specific platform, like Android (complying to the Material Design Guidelines). A developer whose target platform (and therefore its design guidelines, like for iOS) differs from the used wireframe design in this app concept should be able to adapt parts of the UI-Design by himself.
For describing certain important methods, like retrieving data from a dabase and working with them, I would use the UML-Activity-Diagram. Will this suffice or are there better options for describing (concurrent) processes and its interactions with a database?
With all of this considerations, would this project in total be a feasible platform-independent app concept? Am I missing something?
