2026-09-18T20:54:47Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/1006262026-06-06T00:49:30Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Harold Abelson.
Sayyaparaju, Vedha
Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science.
Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science
2016-01-04T19:59:59Z
2016-01-04T19:59:59Z
2015
2015
http://hdl.handle.net/1721.1/100626
932752939
Thesis: M. Eng., Massachusetts Institute of Technology, Department of Electrical Engineering and Computer Science, 2015.
This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student-submitted PDF version of thesis.
Includes bibliographical references (page 70).
In this thesis, I describe how I designed and built multiple components and extensions to App Inventor 2 that will allow application builders to create custom services and background tasks and to build applications that can interact with these services and tasks. Previously, the App Inventor platform only supported the creation of applications which had a screen in the foreground at all times. As such, the main abstraction of App Inventor was this notion of a "Screen". These screens could launch certain tasks to run in the background, but they were limited to the few tasks that were exposed by the App Inventor interface. Application builders could not design and customize their own background tasks. This restricted App Inventor users from building certain types of applications, for example, a music player application or an application that has heavy network communication. To enable users to build such applications, I extended the App Inventor platform to expose a "Task" object in addition to the existing "Screen" object. I created a messaging system which would allow Screens and Tasks to communicate with each other. I also developed additional task components that could be contained in these new Task objects. Users can customize the functionality of Tasks by putting together multiple task components. In this way, App Inventor users can now build more functional applications and explore a part of the Android SDK that was previously out of reach.
by Vedha Sayyaparaju.
M.Eng.
70 pages
eng
Massachusetts Institute of Technology
M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.
http://dspace.mit.edu/handle/1721.1/7582
Electrical Engineering and Computer Science.
User-designed background tasks in App inventor
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="4c71b2fa-4002-4add-a384-2bd68f7dbf54">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Language>eng</Language>
<Title>User-designed background tasks in App inventor</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2015</PublicationDate>
<Authors>
<Author>
<DisplayName>Sayyaparaju, Vedha</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://dspace.mit.edu/handle/1721.1/7582</License>
<Keyword>Electrical Engineering and Computer Science.</Keyword>
<Abstract>In this thesis, I describe how I designed and built multiple components and extensions to App Inventor 2 that will allow application builders to create custom services and background tasks and to build applications that can interact with these services and tasks. Previously, the App Inventor platform only supported the creation of applications which had a screen in the foreground at all times. As such, the main abstraction of App Inventor was this notion of a "Screen". These screens could launch certain tasks to run in the background, but they were limited to the few tasks that were exposed by the App Inventor interface. Application builders could not design and customize their own background tasks. This restricted App Inventor users from building certain types of applications, for example, a music player application or an application that has heavy network communication. To enable users to build such applications, I extended the App Inventor platform to expose a "Task" object in addition to the existing "Screen" object. I created a messaging system which would allow Screens and Tasks to communicate with each other. I also developed additional task components that could be contained in these new Task objects. Users can customize the functionality of Tasks by putting together multiple task components. In this way, App Inventor users can now build more functional applications and explore a part of the Android SDK that was previously out of reach.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>