290 likes | 411 Views
Android Projects. Luca Bedogni Marco Di Felice Dipartimento di Scienze dell ’ Informazione Università di Bologna. The following proposals must be considered just hints .
E N D
Android Projects Luca Bedogni Marco Di Felice Dipartimento di Scienze dell’Informazione Università di Bologna
The following proposals must be considered just hints. • All the main functionalities listed must be implemented (minimal requirements to have the project accepted). • We strongly encourage to expand/customize the proposal based on your creativity.
Projects described in the following must be deployed by a single student. Group projects are not allowed. • Project implementation must be original and 100% student work (no code share or reuse). • Submit the project by email(lam-projects@cs.unibo.it) includingall code, a technical report and directivesrequired to compile/execute the project.
Best students’ projects will be published on the WILMA-LAB wiki: • http://www.cs.unibo.it/projects/wilma-lab/wiki/ • Read and follow the instructions about projects submission policies (deadlines, validity, etc) on the course website: • http://www.cs.unibo.it/bononi
PROPOSAL 1 (c)
Android Project Proposals • Android Budget Tracking Application • Track current/periodic expenses • Browse data and generate reports • Compute and display useful statistics to keep personal finances in order. (c) Luca Bedogni 2012
Android Project Proposals • Android Budget Tracking Application • Functionality1: Allow tracking of everyday’s expenses • Add information about a current expense (e.g. date, amount, category, description, etc) • Save all the information on a local database • Track location (e.g. shop’s location) • Optional: Save a picture of the item, acquired through the photocamera (c) Luca Bedogni 2012
Android Project Proposals • Android Budget Tracking Application • Functionality2: Manageperiodic/plannedexpenses • Add information aboutperiodicexpenses (e.g. loan) • Add information aboutplannedexpenses (e.g. bill) • Budget must be updatedat the payment date • Periodicremindersshould be shown 1 and 2 daysbefore(e.g. throughnotifications or alertdialogs) (c) Luca Bedogni 2012
Android Project Proposals • Android Budget Tracking Application • Functionality3: Visualize and browseexpenses by date • Visualize and enablebrowsing the list of expensesday by day, weekly or monthly • Allow the creation of PDF report (savedlocally) • Display locations on the Google Maps (c) Luca Bedogni 2012
Android Project Proposals • Android Budget Tracking Application • Functionality4: Provideweekly and monthlystatistics • Compute and visualizeusefulstatisticsaboutweekly and monthlyexpenses (e.g. totalexpenses for eachcategory, budget over weeks, etc). • Charts can be generated to visualize data. (c) Luca Bedogni 2012
PROPOSAL 2 (c) Luca Bedogni 2012
Android Project Proposals • Implement a LaTeX Editor for Android • Provide the possibility to edit a text file. • Provide support for LaTeX commands/syntax. • Enable remote PDF compiling and file transfer. (c) Luca Bedogni 2012
Android Project Proposals • Implement a LaTeX Editor for Android • Functionality 1: Typical Editor Functionalities • Open a text file • Edit the file • Save the file • Close the file • .. (c) Luca Bedogni 2012
Android Project Proposals • Implement a LaTeX Editor for Android • Functionality 2: Support to LaTeX syntax/commands • Highlight the LaTeX commands/symbols (e.g. with colored text). • Help the user in inserting the LaTeX symbols (e.g. math symbols) on the text. (c) Luca Bedogni 2012
Android Project Proposals • Implement a LaTeX Editor for Android • Functionality 3: Enable remote PDF compiling. • The app must transfer the .tex file to a remote server, where a PDF compiler is working. • Once the PDF is ready, it must be transferred back to the mobile device. An Intent should be generated to open the File. (c) Luca Bedogni 2012
Android Project Proposals • Implement a LaTeX Editor for Android • Functionality 3: Enable remote PDF compiling. • (Optional) Manage also the compiler log (e.g. to handle the presence of errors). • (Optional) Allow the users to insert images to the .tex document. In this case, a .zip archive should be produced and sent to the remote server. (c) Luca Bedogni 2012
PROPOSAL 3 (c) Luca Bedogni 2012
Android Project Proposals • Android RSS(Really Simple Syndication)Client • Add new RSS feeds • Display the RSS feeds. • Share a post link on a social media. • Congureparameters (c) Luca Bedogni 2012
Android Project Proposals • Android RSS(Really Simple Syndication)Client • Functionality 1. Addnew RSS feeds • Usersenters web URLscorresponding to an RSS feeds • A service shouldcheck the validity of the URL. • A list of current RSS feeds must be mantained. • Add new RSS feedsbased on Intentslaunched • by otherapplications. (c) Luca Bedogni 2012
Android Project Proposals • Android RSS(Really Simple Syndication)Client • Functionality 2. Display the RSS feeds • Show the list of feedsregistered in the device, with the number of unreadposts. • Show the posts on clicking on a feed. • Enablemarking of a post through long-click (marktype: read, unread, favourite). • Enable off-line readingthrough a local database (c) Luca Bedogni 2012
Android Project Proposals • Android RSS(Really Simple Syndication)Client • Functionality 3. Share a post link to social media • The applicationshouldprovide, via a long click listener or somethingsimilar, an action to post a link in social networks suchasTwitter or Facebook. • Additional text can be (eventually) inserted by the user. (c) Luca Bedogni 2012
Android Project Proposals • Android RSS(Really Simple Syndication)Client • Functionality 4. Configureparameters • Allow a userconfiguring the applicationparameters(e.g. frequency update). • Use AndroidSharedPreferencessystem to savepreferencesvalues, loadthemwhen the applicationis up. (c) Luca Bedogni 2012
PROPOSAL 4 (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Recognizea set of pre-definedcontexts. • Capturea set of pre-definedevents. • Definea list of possibleactions. • Allow the creation of rules: • <Context,Event> Action (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Functionality 1: Recognize a set of contexts • Allow user’s defying context name (e.g. meeting) and characteristics. • Basic characteristics: • Temporal information (e.g. date/time) • Spatial information (e.g. GPS location) • Mobility information (e.g. GPS speed, acceleration, etc) (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Functionality 1:Recognize a set of contexts • Allow user’s defying context name (e.g. meeting) and characteristics. • Optional (fine-grained) characteristics: • Sensor values and patterns (e.g. accelerometer) • Radio interface state (e.g. WiFi state) • Microphone/videocamera inputs (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Functionality 2: Event Recognition • Capture and recognize a list of external events • that might occurr on the smartphone.. • Examples of events: • Phone call incoming • SMS reception • WiFi detected • …. (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Functionality 3: Provide a list of pre-denedactions and noticationsthat can be executed. • Three categories of actions: • Modifythe smartphonesetting(e.g ring tones on/off) • Recallthe user'sattentionthrough status-bar notifications • Performoperationson social media (e.g. publish a state update on Facebook) (c) Luca Bedogni 2012
Android Project Proposals • Android IFTTT (If-this-than-that) Engine • Functionality 4: Allow a userspeciying IFTTT rules. • IFTTT Rule: <Context, Event> Action • Continously monitor context/event and performcorrespondingaction • Optional elements: • Allowcombining multiple contexts/eventsthroughbooleanoperators (AND,OR, NOT) • Allow multiple actions on the same IFTTT rule (c) Luca Bedogni 2012