Sched-U App – the first Android application from the Seattle Sela Diamond program

-

 

     The Sela diamond program which took place this summer in Seattle involved the training of CS and Electrical Engineering College graduates from the US. The Entire Course involved OOP training, DB training and the last and greater part of the course – Programming for the android platform.

     The Objective for the course was to train the students and a final project – An Android Application to be published on the play store, and the first app to bare fruit is the Sched-U app.

overview:

College students lead hectic lives. A vast majority now carries smart phones. Sched-U is designed to be an assistant to help college students manage getting to their classes on time, notes and assignments, and final exams.

target audience:

College student who need or want help juggling their class schedule, prioritizing assignments, organizing note materials, and preparing for final exams.

The process

     From the get go, my objective was not only to teach the android echo system and the usage of different API’S or even smart coding. I wanted the students to be able to have an approach for a project, gathering requirements, planning the relationships between the different models and build it modular and easy to maintain, so a fair amount of the time was invested for planning and design, including flow chart, ERD diagrams, and use cases.

    The two partners working on the project are Mark Redden and Nick Huebner. The project involves a lot of coding which includes a modular approach to different aspects in the code and great implementation of OO programming by using managers, each responsible for different actions and data manipulation, along with a fancy horizontal slider with a fine tuned animation between different agendas (day,week) with fade in/out effects, all utilized by a custom View written by Nick and Mark.

   A app well done !

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, create an AutoCompleteTextView
Read more

How to update UI from a different thread

-
     Google has set it’s tone on some tough guidelines for developing android apps, basically there aren’t any strict rules but one very easy to misunderstand. there is a single Thread which is called the “main” thread, or “UI thread” on some places. this is the thread which is in charge on the views and interaction with the users gestures. based on the guidelines of any mobile platform at the moment, all the work that shouldn’t be done on the main thread should be done on background thread. this can be achieved in many ways, you can use AsyncTask, Or A Handler, Or a simple thread with an implementation of the   run() method within the declaration of the runnable. ok, so if I’m pulling some server data, or performing long calculations, pulling stuff from or to the Sqlite database I’ll probably use an AsyncTask. but let’s say for instance that I want to simply update the UI once every couple of seconds (update a TextView or an ImageView’s content etc..), here’s a simple example of i
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched and processed into t
Read more