Week 14 - Submission and showcase

Following Wednesday is the tradeshow, we are now preparing for the tradeshow.

Previous week I,
1. New Features: Add Billing Info;

2. Create a GeneralLibrary for functions that use across many ViewController;

3. Able to show information about a presentation session;

4. Add totalPrice as last section in confirmationView;

5. Fix bugs for calculating totalPrice;

6. Automatically populate user data for the first entry ticket user purchase if user is logged in;

7. Separate Entry and Session Tickets with little tricks;

8. Constraint for select tickets, enter user details;

9. View Attending Events by segment

Week 13 - One more week

Previous week I,

1. Help Matthew to solve the issue that messages for each conversation don't save and retrieve correctly.

2. Merging Matthew work into the newly designed Storyboard

3. Fix bugs in EventsViewController

4. Remove misrepresented actions

5. Rename show of the assets with proper naming

Week 12 - "Showcase is Coming"

This week, Matthew and I consulted Louis(CSCI342 lecturer) about our app for 321. Louis have a some useful input for our project. For example like using gmail as our email platform to send email.

The previous week, I had worked on,

1. Fix the user detail fetching procedure

2. Fix the localisation issue for not translating some component texts

3. Scan QR code with API call, to check ticket validity

4. Add show all ticket and each ticket details

5. QR code generation
6. Separated Storyboard by Tabs
6. Redesign the Storyboard for better user experiences.


Next week, I will be continue to work on Ticketing process as we had agreed on using low level APIs for purchase and generate tickets. Below are some reason why I prefer high level API instead of low level,

Week 11 - Have to boost up the progress for development

This week, I am working on some of the dependency for purchase ticket progress, there is only a few weeks left until the end of semester, we have to boost our speed of development, but before I do that, I need to get other assignments done, so that I don't have to worry about it.


The previous week, I had worked on
1. Add another view to edit user profile
2. Add the ability to view user payment history
3. Modify the procedure of Password hashing
4. Modify the User summary Information
5. Translate more keywords for Chinese Languages
6. Ability to update the personal information and sync with server.


The coming week I will be working on Ticketing progress, I should work on it this week, but because of the dependency is too much. For examples, I need to get User profile, Get Ticket for Event, Get Ticket for Session, TimetableView done before I can work on it.

Week 10 - Post Prototype Presentation

This week, we presented our project to supervisor. The feedback we get is as our group is a huge group, so that we need to separate into smaller team internally, and that's what we are doing. Basically, Micheal in charge of the RESTful API server, Toby in charge of the database, Matthew and I worked on the iOS app(I will be more focus in UI and solving logic issues), and then another three guy(Loo Yee, Sandon, Blithe) working on the web front-end. One of the issue of working in the small team is that we are not pretty sure what others are doing as we are not interacting with their system at any way.

The previous week, I had worked on
1. the QR code scanner for event organiser to scan participants ticket,
2. added security and location button to every tab in the Event View
3. redesign of the Event Dashboard
4. redesign of Login and Register View
5. edit the Login process, user don't have to login for viewing events anymore, but they still need to login for purchasing ticket, and viewing event they joined.
6. create draft process of purchasing ticket
7. add third-party library for HUD, and in app notification
8. solved all the storyboard warning
9. redesign ExploreView cell

The coming week I will be continue to work on ticket process, redesign the app architecture and using exploreView as example to show Matthew how to actually get data from CoreData and update the CoreData in the background.

Week 9 - Prototype Presentation

This week, I re-do the process for ticketing, but as we don't have data to produce yet, so basically it is just making the user interface looks better and improve the user experience. Beside that, the UI design has modularisation, so that I can run any part of the app without bother of error caused because of the view is depended on another view.

Next week I will continue to change the login process and also the events process, in order to present a better looking solution for the presentation we are having at next meeting.

I had suggested to use Github Issues Tracker to discuss about the problem we faced. Using Issues Tracker can help the one who ask question organise developer question and sometime during the organisation of issue, developer might be able to find the solution. Instead of asking question without providing enough details for others to help out.

Week 8 - Merge Conflicts

We faced a merge conflicts on Storyboard, this is due to both Matthew and I are working in some part in the Storyboard. Storyboard is not like any coding file, basically we design in WYSIWYG(What you see is what you get) way and Xcode will automatically generate the code.

Because I have working on Storyboard for weeks, so that I didn't notice that there is some changes in Storyboard by Matthew as he have too many branches and not merge back to master.

link about storyboard merge conflicts,

1. http://mbehan.com/post/77229582565/storyboards-multiple-developers-and-git

2. http://stackoverflow.com/questions/29263725/ios-best-practice-for-managing-code-merge-in-a-storyboard

The solution provided is not suitable for our cases, as we already have every view in storyboard. For now, we agreed that if there is any changes in storyboard, we will use another temporary branch to modify and merge back to master.