Initial objectives – these evolved as the project grew. In the end, an important objective was realised in creating a list of strengths and limitations for the purpose of determining the RAD tools suitability to a project on a case-by-case scenario.
The vehicle for assessing these objectives will be the reproduction of two successful apps with the tools.
Initial observations – App Inventor seems quite limited. Misleading – API’s and implimented within code. This is the only sort of information that is avaialble to people looking to see if RAD suits their needs.
Mention Blocks editor. Use example of VARIABLE and IF
Educate the user. One click publish. Also mention code hinting and syntax highlighting.
Explain process and briefly describe Doodle Jump and FourSquare.
The development of each app brought its own set of challenges.
Expand upon ‘abstract complexity’.
Emerging trends, tools and techniques in mobile2
Emerging Trends, Tools and Techniques in Mobile Software Applications Development<br />Seamus Mc Gurgan<br />
Background<br />Enormous demand for applications.<br />Made with complex SDK’s which required a considerable time investment. <br />Emergence of Rapid Application Development (RAD) Tools which claim no programming experience is necessary.<br />This study aimed to assess the effectiveness of RAD from the non-programmers perspective.<br />
Problem Statement<br />“Using both Google App Inventor for Android and Adobe Integrated Runtime as examples of emerging Rapid Application Development Tools, to what extent can a person with no programming experience be realistically expected to become successful in app construction and at what point will they face complexity so great they cannot continue without seeking the aid of an expert programmer?”<br />
Objectives<br />Identify what these emerging tools offer to a person without a background in programming.<br />Determine how successful this type of user can be at constructing apps with RAD tools.<br />Assess the design on the tools and how they cater to their audience.<br />
Objectives<br />Investigate the methodology of RAD – marketing buzzword or genuine method of producing quality results quickly?<br />Record how the tools influence the non-programmers’ thought process while building apps.<br />Discover limitations of tools and their scope for providing key application features.<br />
Methodology<br />To measure the effectiveness of RAD, two emerging tools were chosen and two popular mobile apps were recreated in these environments.<br />Google App Inventor<br />Adobe Integrated Runtime (AIR)<br />Doodle Jump<br />FourSquare<br />
Challenges App Inventor – Doodle Jump<br />Jumping mechanic implemented by pixel displacement, counter or timer? Blocks showed options.<br />Bouncing platform – discovery of if else.<br />Spring and Doodler navigation – success by experimentation of numbers.<br />Saving score to TinyWebDB – purpose of lists unknown to the non-programmer.<br />HCI – screen arrangers, no customisable components and workaround for multiple screens.<br />
Challenges AIR – Doodle Jump<br />Installing AIR on phone required command line argument entry.<br />Publish settings were unreliable.<br />Discovering the structure of the language with little feedback – how to define variables, name controllers, order of commands, syntax. <br />Disabled property – confusing syntax highlighting.<br />Co-ordinates VS stage width – mixture of both had to be applied.<br />Score – glyph embedding.<br />Unsolvable – shooting sprite overlap, establishing connection to database.<br />
Challenges App Inventor - FourSquare<br />Tag–value system unpractical for intricate database – complete dependence on position in list.<br />Limit to number of friends – unable to dynamically create components via code.<br />Inability to search values of TinyWebDB – location co-ordinates had to be stored within code.<br />Adding friends– had to be manually selected from device contacts while also being unable to import Twitter friends.<br />
Challenges AIR – FourSquare<br />Connecting to the database – Microsoft Access database was made, but a full connection could not be established.<br />The barrier of SQLite proved too challenging and without its implementation, much of the functionality of FourSquare could not be recreated.<br />Translating the equation to calculate distance into Actionscript – puzzle structure of App Inventor replaced by brackets.<br />External API had to be manually installed – maps function not available by default and contacts API was not compatible.<br />
Development of the Non-Programmer<br />The development process of each app educated the author on the basics of programming.<br />Use of variables to make large quantities of code manageable.<br />Application of if else statements and lists.<br />App Inventor’s conceptual metaphor of puzzle pieces aided trial and error construction.<br />On the whole, much more was learnt about the fundamentals of coding through experimentation with App Inventor than was gleaned by reading the comments provided by AIR’s code snippets – this was an unexpected finding.<br />
Key Advantages Found<br />App Inventor:<br />This study proved that the Blocks Editor helped a beginner programmer to learn the structure of code.<br />The sensible categorisation of components and blocks made finding objects intuitive. <br />The TinyWebDB’s method of storing data as a tag and a value was seen to be an easy concept for the user to understand. <br />AIR:<br />Code Snippets provided rapid design of complex methods and their comments acted as a translation into common English. <br />Timeline frames allowed for the easy development of multi-screen apps.<br />Invisible buttons promoted good design capabilities.<br />
Key Limitations Found<br />App Inventor:<br />Not able to freely position components.<br />Limiting to one screen apps meant good design was sacrificed to find a workaround for multiple screens.<br />Poor emulator performance.<br />Inefficient database system that does not permit searching, ordering, saving of images or multiple simultaneous calls.<br />Orientation sensor demanded powerful phone to achieve realistic results.<br />Sprite collisions were not able to be accurately defined.<br />GPS functionality not able to be replicated on connected device.<br />Zoom and Undo features are rendered unusable.<br />
Key Limitations Found<br />AIR:<br />At times functionality was heavily dependent on the overall structure of the code. <br />No search function provided for the library of methods and calls. <br />Installation of Adobe AIR on the phone was frustratingly difficult.<br />SQLite was not accessible to a new user.<br />Feedback from failed publish attempts was often indecipherable to a person who does not understand the jargon of programming.<br />Emulator was visually inaccurate.<br />
Comparing the Tools<br />Scope for design - App Inventor’s methodology of screen arrangers pales in comparison to the freedom offered by the stage in AIR.<br />App Inventor outshined AIR in terms of code construction and ease of learnability. <br />App Inventor simplified data storage to a paired tag and value system – this was found to sacrifice functionality and data integrity in its efforts to make the tool more accessible.<br />Poor emulators meant a real device was required to produce applications that depend on mobile functionality for both tools.<br />
Comparing the Tools<br />The overall order of the code had no bearing in App Inventor but had great influence in AIR.<br />AIR’s comments can be used as a notepad and unused code can be placed within them, while App Inventor only allows the deactivation of blocks.<br />SQLite allows expansive controller over data, but at the cost of the excommunication of new users.<br />
Objectives Met<br />This study concluded that App Inventor was the easier tool to learn via trial and error for a beginner.<br />It was shown that a both tools allowed an inexperienced user to create functional applications within a short amount of time.<br />While most of the functionality for both apps could be recreated with Google App Inventor, AIR struggled to provide the tools necessary for a beginner to create these applications. <br />AIR makes no effort to abstract its complexity, and this repelled the user.<br />
Objectives Met<br />Neither tool can be considered ‘rapid’ – App Inventor required time spent finding workarounds to absent features and AIR demanded the learning of additional languages.<br />Confirms RAD is a marketing buzzword, but still has a place in rapid development of smaller projects.<br />List of recommendations to be made to tools was made – App Inventor updated with two of these changes.<br />
Future Work and Implications<br />To assess the effectiveness of RAD tools as a whole more tools would need to be examined, such as AppCat and Visual Basic.<br />Another worthwhile expansion on this research would be to have an expert carry out the same tasks with the RAD tools and comparing findings – allowing for a more accurate identification of strengths and weaknesses.<br />Using these tools in academic studies at both secondary and higher level education could provide an excellent source of learning - allow for the teaching of more complex concepts earlier in the course. <br />RAD tools are limited by subjectivity - if a project specification is within the confines of the limitations presented within this study, the tools can be more cost effective than more conventional environments. <br />
Conclusion<br />Both beginners and experts alike can gain much from RAD tools, but new users will be misled by the tools’ claims to be rapid.<br />The author learnt how to program mobile applications to a good degree without receiving teaching.<br />Validates the ‘no experience required’ claims of the tools and shows how they successfully removed the intimidating barrier of learning code. <br />RAD tools have much potential for both educating beginners and quickly developing smaller projects.<br />