ufosc / alarm-clock Goto Github PK

Add a time picker to select the alarm clock time.

The footer tab needs some icons. I'll leave the choice of Icons to you but make sure they match with the tab name.

Refer to https://www.npmjs.com/package/react-native-vector-icons to get the icons.

When the alarm goes off, the user should be able to click on the notification and be redirected to the screen to shut off the alarm.

All the components under the Components folder are still in JS. Eventually we want these to be converted to Typescript

Create a footer tab that separates the clock, settings, and alarm features.

Add a section about running "npm run tunnel" in the event that a contributor cannot run npm run start because of networking issues. This should be under running the application.

The current footer navigator does not contain any logic to navigate to another screen. The task is to create the logic behind switching between the clock, alarm features, and settings tab.

For the settings tab, there are two settings button on the home page (A floating button and one on the navigation footer). Move the logic for navigating to the settings page from the old button to the navigation footer settings button.

You should use the react navigator library to do this.
https://reactnavigation.org/docs/bottom-tab-navigator/

Some parts of the readme still need to be filled out like the Contributing and Installation sections. We also need a proper description.

The last pull request placed the add alarms where the clock tab is placed. We need someone to move the add alarm functionality to the alarm tab while maintaining functionality.

The current home page for the alarm clock is really messy. We could improve the overall user interface.

This git clone link "git clone https://github.com/ufosc" should be changed to "git clone [email protected]:ufosc/Alarm-Clock.git" or "git clone https://github.com/ufosc/Alarm-Clock.git" using http

In the settings pages, create re-usable components to add different settings. Later ideally this will take in a JSON file or objects full of settings and will be mapped to these components.

When the alarm clock goes off, a notification and sound should go off for the user.

Implement a local storage system using async storage to store local data.

I will be merging the project code base to TypeScript. Having strict types will help us read and write code more clearly. TypeScript is a super set of JavaScript so you can still write plain JS and it should not be that hard to pick up if you are already family with JS.

If this is your first time learning TypeScript here are some resources that you could use.

TypeScript Docs: https://www.typescriptlang.org/docs/

We're looking to add SMS integration if a user misses their alarm:

https://docs.expo.dev/versions/latest/sdk/sms/
This link should provide some info on how to incorporate texting for both IOS and Android.
Note that we will also need some way to provide a number to text (perhaps the user can enter it somewhere, or even select a contact)

Adding styles for elements that use darker colors will likely be appreciated by our CS-student user base.
(The specifics are up to you)

Currently the README lacks color and I think badges could fix that. Could someone please go to https://shields.io/ and create appropriate badges for the page such as open issues, version, and README style.

Create a basic settings screen to hold the settings for the alarm. It can just be a screen with the settings as a header and an option to toggle between light and dark mode. Eventually, this will expanded upon but for now this is a good start.

When adding a new alarm, the time picker is there but not visible until you press on it. Currently an issue for IOS however I do not know if it works on Android. A fix for this would be helpful.

Create an add alarm feature similar to the IOS alarm app where you can set the time (using the time picker), and add a sound. This could show up in a separate tab that stores the alarms and the user should be able to toggle on and off the alarm. Ideally we would also need some way to store the user's alarms in local storage on the phone but for now just focus on the UI.

The README still links to the repo owned by me, but the repo is now owned by the OSC account