Jim Cowart is an architect, developer, open source author, and overall web/hybrid mobile development geek. He is an active speaker and writer, with a passion for elevating developer knowledge of patterns and helpful frameworks.
Everlive isn't just capable of storing data - it can store files as well. In this post we examine how Everlive stores files, and a simple working example on uploading & retrieving files from Everlive.
This is Part 4 of a four part series where we explore some of the tools available to detect and manage online/offline connectivity in web/mobile applications. In Part 1 we looked at the available APIs for detecting connectivity state (and the woes associated with them). In Part 2 we wrote a hand-rolled abstraction to manage using these APIs together and began to see elements of a state machine emerge from the chaos. In Part 3 we explored how we can keep our FSMs from violating SRP, and set the stage for using multiple FSMs together to model more complex application behavior. In this final part of the series, we look at setting up hierarchical FSMs to manage more complex behavior.
There is no shortage of confusion around the question of which path to take when targeting mobile devices. Entire white papers cover this topic and are still incomplete. With that in mind, my goal with this post is to provide, perhaps, a starting point. Getting answers is critical, of course - but knowing the questions to ask is the first step.
If naming a thing is hard – getting used to a name change is even harder. "PhoneGap" is a recognizable name to most developers that have been involved in (or at least aware of) hybrid mobile application development. "Cordova", on the other hand – what's that? For me, it invokes images of the famous Spanish general, or Italian food, and sounds like a new sports car....or driving a sports car at high speeds to an Italian restaurant (always a win-win)...