Closes #15

Refactor Plan ViewControllers from objc into Swift.

• Refactor SafetyPlanViewController into swift, add BaseViewController components, Add SafetyPlanItem for data management.
• Refactor EditWarningSignsViewController, create TextField and Button Cells, Update UserDefaults save method
• Add reusable EditSafetyPlanItemViewController for rest of Plan view controllers, update edit vc and user default gateway for personal contacts
• Finish migrating Plan ViewControllers from objc into swift

Closes #19 Implement RealmDB for the data persistence layer

• Updated our use of UserDefaults gateway for personal contacts and SafetyPlanItems to use RealmDB
• Implemented a Gateway protocol template for future gateways, each pertaining to the data we want to query from the DB
• Added AppSettings class to manage our use of UserDefaults for storing app settings

Right now, it looks like the personal contact info is being stored separately as a name and a number in UserDefaults. While this works I believe that there is a better way to persist this information which will make querying it much easier, manageable, and safe.

Some suggestions are: 1.) Model the personal contact info in a Codable class that can be serialized/deserialized into UserDefaults, that way we don't have to check the individual keys (ie "name1", "number1"). This will also allow the user to store an arbitrary number of personal contacts, instead of the hard limit that we are setting 2.) Model the personal contact info in CoreData. If we don't want to rely on UserDefaults we can turn to CoreData to model and manage the persistence of our personal contact info 3.) Model the personal contact info with Realm. This is another Database tool that I use in all of my projects. It is much easier to setup and user (in my opinion) than CoreData. Setting it up in Realm will help if there are things in the future that we want to persist.

There are pros and cons to each, but let me know what you think.

When building the app in XCode 13, there are several UI issues.

• Transparent splash screen

• Transparent navigation bar till I scroll up the screen

The video with 1 and 2: https://user-images.githubusercontent.com/7028613/182032101-e62f3157-217c-4e1d-a312-3a583481197f.mov

• Untappable tip textfield and +Add another button.

#4 Native Dark Mode support for the app.

Notes

• To change the text color of the TextViews with attributed text, I had to do it programatically. Since this is the case, I converted the Objective-C code for those three view controllers (which I am currently working on on a different branch anyway.)
• I did not change the way that the blue color in the app appears between light and dark mode. I don't think that it looks bad in dark mode, but if we are interested in changing the color between light and dark mode, there are a couple things to know. You can do this by adding color sets, but this is not supported the on older versions of iOS that the app supports. It could also done programmatically, but will be extra work and would be best to do after the entire app is converted from Objective-C to Swift.

Testing

• I tested on iOS Simulators with iOS 10.3 (iPhone 5s) and iOS 13 (iPhone 11 Pro Max).

Got this feature request from a therapist:

"Hello, I wanted to say that I really like your suicide safety plan app. I wanted to ask for a recommendation. I’m a therapist and use it with my clients but I usually also want a copy of the plan when they create it. Is it possible to add a feature that would allow users to send their plan to people?"

In order to ensure that contributors are not merging directly into master, and that there are no confusions with feature/bug/enhancement branches I would suggest that we establish a gitflow process.

I recommend that we create a develop branch that all feature/bug/enhancement branches will branch off. All PRs should be made against the develop branch. Only specified admin can merge develop back into the master. The master branch is the final state before the new build is submitted to app store.

Please let me know if there are any suggestions/comments/critiques/concerns.

Closes #26

The previous export plan

Plan

Warning Signs

• Template text

Coping Strategies

• First, Second, Third, Fourth, Fifth

Reasons to Live

• Template text

Contacts

• Emily, Ed

Places for Distraction

• Template text

Other

• mplate text

The fixed export plan

Plan

Warning Signs

• Template text

Coping Strategies

• First, Second, Third, Fourth, Fifth

Reasons to Live

• Template text

Contacts

• Emily: 123456, Ed: 43434434

Places for Distraction

• Template text

Other

• Template text

Currently the app is persisting data using UserDefaults. While not an incorrect usage, it would be better to use a dedicated DB framework to manage modeling, saving, and querying data. After discussion in this issue we have decided to move forward with using RealmDB as our dedicated data persistence layer.

This issue will track the implementation of RealmSwift in the iOS application

Closes #24

First: Combining Xcode 13 and iOS 15 had these bugs

1. Transparent navigation bar until scroll up
2. Transparent splash screen
3. Transparent tab bar until scroll up
4. Untappable buttons and textfields in custom tableview cells

Second: The minimum supported iOS version had been increased to 13 by agreement

Testing

• [x] Device: iPhone 12 mini, iOS15.5
• [x] Simulator iPhone 13 mini, iOS 15.5
• [x] Simulator iPhone 11 Pro Max, iOS 14.5
• [x] Simulator iPhone 8, iOS 13.7

Checks

• [x] System background color splashscreen: dark for a darkmode, white for a lightmode
• [x] Visible nav bar after launch on all screens
• [x] Visible tab bar after launch on all screens
• [x] Tappable Add another button, one line and two line textfield on EditSafetyPlan screens

Closes #22 The added sharing icon is from SF Symbols app. For this reason, there is no need to add an author info. I've removed the ic_action_share icon, as it doesn't seem to be used in the project. If in doubt, I can return.

Testing

• [x] Device: iPhone 12 mini, iOS15.5
• [ ] Simulator. I have M1 notebook, I couldn't test on the simulator

Checks

• [x] Export empty plan

Plan

Warning Signs –

Coping Strategies –

Reasons to Live –

Contacts –

Places for Distraction –

Other –

• [x] Export plan with the Other section filled in

Plan

Warning Signs –

Coping Strategies –

Reasons to Live –

Contacts –

Places for Distraction –

Other Test filled section

• [ ] Export plan with the first five items filled in (see below)

Important I couldn't check the plan with the first five items filled in, because new Xcode 13.2.1 / 13.4.1 builds with some UI bugs:

1. Transparent splash screen
2. Transparent navigation bar till I scroll up the screen

The video with 1 and 2: https://user-images.githubusercontent.com/7028613/182032101-e62f3157-217c-4e1d-a312-3a583481197f.mov

3. Untappable tip textfield and +Add another button.

The reason is new Xcode 13, but I can't install the previous, because macOS Monterey can't work with Xcode earlier, than Xcode 13.

The project needs an issue with adaptation to Xcode 13 – I can create it. As well, It could be useful to decide on supported iOS versions. The current minimum iOS version is 9. If it's decided to support all older variants, this point can be described in the Readme, as this may raise a question in any issue. In another case, the minimum iOS version could be raised, as this can simplify further development.

There are some minor bugs in the current export

1. There are no numbers in the exported contact section
2. The first two characters of the other section's text are deleted

Example

Plan

Warning Signs

• Template text

Coping Strategies

• First, Second, Third, Fourth, Fifth

Reasons to Live

• Template text

Contacts

• Emily, Ed

Places for Distraction

• Template text

Other

• mplate text

First, great app. I am a child and adolescent psychiatrist and I really value that my young patients can always have this plan on them because they always have their phone. A paper plan is great, but is probably sitting in a drawer at home when they need it. There are some very recent updates to the National Suicide Prevention Lifeline that are relevant for the app.

Over this summer, the National Suicide Prevention Lifeline formally switched to be the "988 Suicide & Crisis Lifeline". See 988lifeline.org. The FCC has now made the three digit dialing number 988 active in all US states and territories, just like 911. Unlike 1-800-273-TALK (8255) number, which is still active, the 988 number works with both voice and SMS, and 988lifeline.org also has a web-based chat. Especially for privacy reasons, some youth prefer the web-based chat because their parents won't see it on the phone bill. 988lifeline.org is also the best single best starting point for the available diversity of crisis support resources that I have encountered, including resources for veterans, LGBTQ+, Spanish speaking, black, native American, hard-on-hearing, sign language lifeline, maternal depression, individuals with autism, and more.

Could we update the crisis resources to the new 988 and 988lifeline.org resources? Please don't hesitate to reach out.

Hello!

I think we should update the app's design to be more modern and have a content first approach. I brainstormed some changes that could be made earlier today and would love some feedback. Please let me know what you think!

https://www.figma.com/file/4jKqQ9V2n0iN3seNA2Ux9v/Suicide-Safety-Plan?node-id=0%3A1

Convert the Guide View Controllers to Swift.

• [X] GuideCopingViewController

• [X] GuideSuicidePreventionViewController

• [ ] GuideSafetyPlanViewController

• [X] GuideResourcesViewController

• [X] GuideOverviewViewController

• [X] GuideRecoveringViewController

Right now the Crisis tab of the app only shows up for users in the US. The Android version already supports other countries, we should do the same here! The primary things that need to be customized to the country is the Suicide Hotline Phone # and a number to Text if it exists in the country targeted.

We could add an extra layer of security for users by giving them the option to set a passcode. Should contain an easy way to reset their password. Ideally, we could have the option for authentication that's pre-built into their phones (Face ID / Fingerprint).