Mobile app presentation
Transcript: way to locally and cloud store data GET, POST, PUT, DELETE took a look at similar software Mobile group management app Security Concerns What is the goal of our product? server-side: iterative method access control Assigning Guidelines Tablets and Holo UI Tasks GET taskmanapi.appspot.com/download/TaskMan.apk Encryption, UserID & APIkey Client: linking fragments TaskMan /project Database Back-end Datastore: from pool of unassigned tasks Backward-compatible Java Android SDK Apache HTTP library (JSON) Classes are broken up by Activities, Utilities, or Adapters GET, PUT, DELETE Follows Holo UI guidelines create the views for phone using fragments Creating the server Server: Return Code: 200, 201, 400, 401... aka research Modification permissions push-notifications from server API - RESTful Examples of similar apps: - Group SMS & Scheduler - Groupme - Group Connect Actions: HTTP Methods: Administrative Console Level Zero Data Flow /project/projectid Entities API Not RESTful Modifiction Times /user/userid Modification Times Emphasis on concurrency, ease of use Software Engineering Methodology /project/pid/task/taskid basic UI skeleton Returning data: JSON, XML Stateless, Client-Server, Cacheable, Uniform Interface - Has a free form design that can be implemented for any type of project REST HTTPS: SSL/TLS, RC4_128 It should be simple and user-friendly, so it relieves not adds stress. And is able to not only track the project as a whole but individual progress as well. What if we make it a mobile app so, it's easy to access from anywhere at anytime? that exists task pool Could create projects/users Server: /CreateUser /Create Project /GetProjects REpresentational State Transfer - what we felt they were lacking Designing the datastore /user Need User ID, API Key Iteration 3 Database/ other requirements: Functional Builtin HTTPS /apikey Google App Engine ViewPageIndicator on phone All Activites load Fragments Google Play Services for authentication ActionBar Sherlock AsyncUtil - Reduce server calls from 150 lines of code to 1 Generic HTTPPut, HTTPPost, HTTPGet, and HTTPDelete calls ability to sync apps across phones/ platforms Garbage collection How we came up with the idea Go Language GET, POST Activity – a collection of views which make up “one focused endeavor the user can undertake” Group SMS & Scheduler Google App Engine Tasks can be marked as either client-side: Static Files server-side: Creating the Android app 3 years old GET, PUT, DELETE Split action bar Create Projects and add users Google userinfo API GET Go Language Group project mobile management app - we took a look at what they did Task Messages/Updates Implementation Using "up" navigation Works on phones and tablets Brainstorming Compiled Language Access Permissions size requirements? Size of screens small, medium, large, x-large? Iteration 1 Google authentication Server Memcache RESTful Systems programming language Stewart, Nate, and Puja Creating the App Why not make something that can make group projects like this easier? assigned, started, submitted, Future Iterations Iteration 2 Keys: Ancestor+ID Security Concerns together for tablet UI By doing this we came up with ways to improve it and came up with our requirements Google Userinfo Access Token Oauth2 Creating Single-pane and Multi-pane Layouts GET, POST HTTP Handlers POST High Scalability Server Access Statically typed /project/projectid/task Any user can assign tasks to themselves - It is meant for a group of individuals working as a team. (It works for anything from class projects to work assignments) Server Activity designs based on fragments client-side: personalized to-do list Create and Modify Tasks The Action Bar Beginning point Resources: /collection/ /element Project Manager can assign tasks and make other users project managers - This tool can be used for more effective on the go communication Users have access to pool of tasks (and task status) Designing the app Requirements due dates 2 2 1 1
Prezi Present
Prezi Video
Prezi Design
