Appcelerator Mobile+ 2015 (português)

Notas do Editor

• #7: If we return to this mobile landscape of many devices on one hand and many data sources on the other, and imperative to connect them in a way that’s seamless and elegant and delivers a great user experience, we see three necessities emerge. First, you’ve clearly got to have the means to create superior apps that will deliver the best possible experience and do it across a range of devices and OSs (no more Wintel monopoly). In the ideal world this means being able to reuse code vs. creating dedicated code bases per device or OS, and it means being able to leverage widely-available developer skills vs. having to find and recruit a bunch of new, narrowly specialized and expensive experts. Second, you need true, mobile-optimized APIs that provide open access to all the necessary data sources. Now, this is different from the legacy days of middleware and SOAP protocols, because of course these mobile devices have a different form factor, they display less data in one go and so require a different payload, they may lose connection and need to work offline and then sync when they reconnect, and so on. Finally, given the imperative around great user experience, you need proper, real-time analytics that tell you at a glance how it’s all working: are the apps being used the way we hoped? Are they crashing or throwing exceptions? What’s our service usage like? How’s our own efficiency in building and delivering new app capabilities? And so on.
• #8: If we return to this mobile landscape of many devices on one hand and many data sources on the other, and imperative to connect them in a way that’s seamless and elegant and delivers a great user experience, we see three necessities emerge. First, you’ve clearly got to have the means to create superior apps that will deliver the best possible experience and do it across a range of devices and OSs (no more Wintel monopoly). In the ideal world this means being able to reuse code vs. creating dedicated code bases per device or OS, and it means being able to leverage widely-available developer skills vs. having to find and recruit a bunch of new, narrowly specialized and expensive experts. Second, you need true, mobile-optimized APIs that provide open access to all the necessary data sources. Now, this is different from the legacy days of middleware and SOAP protocols, because of course these mobile devices have a different form factor, they display less data in one go and so require a different payload, they may lose connection and need to work offline and then sync when they reconnect, and so on. Finally, given the imperative around great user experience, you need proper, real-time analytics that tell you at a glance how it’s all working: are the apps being used the way we hoped? Are they crashing or throwing exceptions? What’s our service usage like? How’s our own efficiency in building and delivering new app capabilities? And so on.