Starling Blog

In this final week, we have finished our project for the demo and presentation. We have a meeting on Monday to make sure our demo is on track. We tried to make our demo as professional as possible. I think the demo was stressful but it went well in the end.  For our project, we finished with 2 main features and 2 side features. Two main features are notes and expense. Two side features are report and dashboard. They function as we expect but it still has some small bugs to fix. Every software has bugs; if it does not, it is because you can find them.  Our team plan is that we will fix some bugs, improve the Facebook log-in (implement it to backend), make the whole web responsive (changing when using on mobile), make the web's UI more consistent (same color and styling for the whole app), and add one or two features (optional - profile). Finally, we will deploy the project in the summer. We hope it will help our resume look better. Below are some photos of our webs:  ...

 This week's blog will cover the Authentication flow. We have implemented the authentication flow from Week 5, but over time, the flow has changed and the UX has improved drastically. We switched from using the full page to using a modal to display the login and sign-up form, which improves the smoothness of our flow. Here's a quick look at our authentication flow as of now: We also implemented the Google Authentication flow which is accessible via the G button below our main sign-in buttons. We are planning to revamp the UI as the final deadline approaches. Stay tuned for our next blog to see our improvements on the app. 

 This week, we updated the note function when the user can add even and update the complete state in a convenient way. Moreover, we also separate them into different tabs so people can see what they completed easier. Another thing we improved was the graph when it instantly updates about expense condition and to-do list, which you completed or in progress. With this update, people can keep track of tasks in 3 days or in the week, which makes sure that people forget tasks or overusing money.

Hi everyone. Starlings started Week 10 by introducing the Dashboard page to our productivity application. Within this view, the user will get a quick glance at how they are doing during the day. There will be mini summaries for every page in the application, including Expense and Note. Take a look at the image below to see the Dashboard screen: Dashboard screen The way we implement this Dashboard page is simple, yet efficient. We utilized our code from other pages to create information specifically for the current date. While the user has the access to all information on the pages themselves, we intended to provide only a quick snapshot for that day to save the user some time browsing through all pages. We created a separate reducer to store all the data we needed to display the Dashboard instead of using the already-existing reducers for other pages. By doing so, the Dashboard page will be independent and will not break if there are any, even minor, changes to other pages. Card Compon...