MobileAppBox™
No standard language communicates universally among mobile platforms. This creates a significant limitation for developers intending to efficiently distribute content across different mobile platforms. Apple’s iPhone SDK uses an Objective-C foundation. Application development on Google’s Android and RIM’s BlackBerry platforms are exclusively Java-based. Symbian, supported by Nokia with widespread US deployment projected in early 2010, is C++. No signal framework dominates the marketplace resulting in a fundamental constraint for application expansion.
Although the minutia of each framework varies, the root concepts behind many applications remain consistent. Variations exist among background color, character size, and font. Dynamic text is syndicated from a web feed and aggregated on an application. Video and audio content is downloaded from a source and syndicated to an application.
These concepts are central for any mobile application regardless of the platform.
MobileAPPBox patent pending technology is built to standardize frequent root processes, and generate custom libraries for specific development environments by editing only a small subset of manipulations. A programming protocol interprets dynamic data structures through common file types to efficiently deploy applications across all mobile platforms. A simple layout developed through Adobe FLEX, interface for each specific application platform including (but not limited to): Android, BlackBerry, iPhone, Java ME, Lazarus, Palm OS, Python, and Symbian. An MXML, or equivalent, mark-up language uses application libraries through two-tier architecture. The user interface, functional process logic, and data access act as independent modules for user input and functional libraries as output.
On the user interface tier, the user can to select from any number of standard functions including text creation, image layout, audio input, video display and popular application programming interface integration. Standard application layout and interchangeable markings further this process. Application programming interfaces included: YouTube, Flickr, Facebook, Twitter, Amazon, Google and others. File types and data structures necessary to obtain content are expansive. File types include (but are not limited to): MOV, MPEG, MP4, WAV, BMP, PNG, and JPG. Data structures include (but are not limited to): RSS, XML, PLIST, or JSON. The function process logic combines the resources necessary to build libraries for the specific application. Due to file-type restrictions per specific platform, automated conversions will facilitate particular queries.
Using custom Flex modules and server-side processes, standard inputs are converted to platform-specific functions. Data output features custom libraries specific per platform. Foundations include (but not limited to) C++, Java, Objective-C, and Pascal depending on the platform. Rather than attempting to generate code that competes with an integrated development environment, libraries are manually installed inside the environment dependent of the logic process. Thus, a module can be customized to nomenclature and style to each of the seven mobile platforms.
Moreover, modules adapt best practices. For example, an XML input of textual content is converted to the preferred PLIST for the iPhone Objective-C platform, whereas it maintains original form for Android and BlackBerry Java platforms. Unlike other approaches that utilize classes across all platforms, individual modules can be highly tailored the particular platform.
Cross-platform applications will become widely available at a fraction of the cost and time and provide unparallel abilities to update content across all your mobile APPS regardless of the platform.