{"id":18,"date":"2022-01-28T02:48:30","date_gmt":"2022-01-28T02:48:30","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/born2code\/?p=18"},"modified":"2022-01-28T02:51:22","modified_gmt":"2022-01-28T02:51:22","slug":"firebase-and-ios","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/born2code\/2022\/01\/28\/firebase-and-ios\/","title":{"rendered":"Firebase and iOS"},"content":{"rendered":"\n

When it comes down to it, mobile apps are all about data. Displaying data, manipulating data, adding data, and so on. For the iOS Bike Kollective app, that data involves users and bikes. In crafting our project plan, our group decided to store this data in a cloud utilizing Google’s Firebase<\/a>.
<\/p>\n\n\n\n

As I am implementing the List View for the app this week, I will need to find a way to retrieve and display bike data using a Table View<\/a>. That means understanding how Firebase and Swift can work together.
<\/p>\n\n\n\n

Getting Firebase Up and Running
<\/h2>\n\n\n\n

Once the Firebase NoSQL database is set up, the proper Firebase SDKs will need to be in place in order for our app can interact with the database. That means installing the proper Swift Package Dependencies, such as the Firebase iOS SDK<\/a> via Cocoapods.
<\/p>\n\n\n\n

Once that is complete, we will need to ensure Firebase is imported into the relevant Swift files, in particular, AppDelegate.swift. Then, an instance of FirebaseApp will need to be declared and configured using the following method in AppDelegate.swift:
<\/p>\n\n\n\n

FirebaseApp.configure() \n<\/pre>\n\n\n\n
While Firebase is set up, our database will be running as a Cloud Firestore database. To get this set up, I will follow the various steps as outlined by the Firebase documentation<\/a>.
<\/p>\n\n\n\n
To sum up, I’ll need to add Cloud Firestore as a pod to the Podfile and then add the following line to AppDelegate.swift:
<\/p>\n\n\n\n
let db = Firestore.firestore() \n<\/pre>\n\n\n\n
Retrieving Firebase Data
<\/h2>\n\n\n\n
With Firebase and the Cloud Firestore database properly connected to the app, I will need to code the means of retrieving bike data from the database.
<\/p>\n\n\n\n
Luckily, Google has provided a code example on Github providing a general outline of how this process may work here<\/a>. I’d first need to declare an instance of the database as so:
<\/p>\n\n\n\n
var db: Firestore!\n<\/pre>\n\n\n\n
And then adding the following line in the viewDidLoad() function:
<\/p>\n\n\n\n
db = Firestore.firestore()\n<\/pre>\n\n\n\n
Firebase refers to tables as Collections and entries as Documents. For the bike data, I would then need to access the Bike Collection to display individual Bike Documents. 
<\/p>\n\n\n\n
This means running a method called getDocuments() on the collection and then iterating through it to apply the relevant data from each Bike Document to each Table View Cell as such:
<\/p>\n\n\n\n
db.collection(\"bikes\").getDocuments() {(snapshot, err) in \n    if let err = err {\n        print(\"Error getting documents: \\(err)\")\n    } else {\n        for document in snapshot!.documents {\n            \/\/ Add data to objects in Table View Cells\n        }\n    }\n}\n<\/pre>\n\n\n\n
As we can see, this also provides the iteration needed to apply the retrieved data to each individual Table View Cell.
<\/p>\n\n\n\n
Wrapping Up
<\/h2>\n\n\n\n
With the above in mind, I can now work on simply implementing the above code into the relevant Swift files. While I will need to figure out the specifics of inserting the data into the various objects on the storyboard, I can at least rest easy that the Firebase data can be retrieved.<\/p>\n","protected":false},"excerpt":{"rendered":"
When it comes down to it, mobile apps are all about data. Displaying data, manipulating data, adding data, and so on. For the iOS Bike Kollective app, that data involves users and bikes. In crafting our project plan, our group decided to store this data in a cloud utilizing Google’s Firebase. As I am implementing… Continue reading Firebase and iOS<\/span><\/a><\/p>\n","protected":false},"author":11919,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-18","post","type-post","status-publish","format-standard","hentry","category-uncategorized","entry"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/posts\/18","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/users\/11919"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/comments?post=18"}],"version-history":[{"count":5,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/posts\/18\/revisions"}],"predecessor-version":[{"id":24,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/posts\/18\/revisions\/24"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/media?parent=18"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/categories?post=18"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/born2code\/wp-json\/wp\/v2\/tags?post=18"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}