Research Curator Data Models

[nicholasri]

Objective

As an iOS Engineer, I want create our first view, the Curator View. This view should confirm to the details provided in: https://github.com/SanFelipeStudios/RomeTwo/issues/6.

Because this is our very first view, we will have dependencies on Data Models that do not currently exist in our product. Research and implement the necessary changes to load these models via CoreData.

Hades

• Game

  • ID: UUID
  • Title: String
  • Description: [String]
  • Developer: String
  • Publisher: String
  • Price: Double
  • Release Date: String
  • Labels: [Label]
  • Ratings: [Rating]

• Label

  • ID: UUID
  • Name: String
  • Description: String
  • Link: String

• Rating

  • ID: UUID
  • User: String
  • Recommend: Bool
  • Body: String

• User

  • ID: UUID
  • Name: String
  • Address: String
  • Phone: String
  • Cart: Cart
  • Wishlist: Wishlist
  • Payments: [Payment]
  • Library: [Game]

• Curation

  • Game: Game
  • User: User
  • Description: [String]

[nicholasri]

Research and Findings

• CoreData vs Realm

  • https://realm.io/best-ios-database/
  • Core Data is great for relational databases. This is the choice if the relationship between the data is heavily connected
  • Real is owned by MongoDB is an Object Oriented database. Code is often simpler as well due to closeness in structure between the database and object in code.

• Offline Functionality for applications:

  • Discord

  • Absolutely nothing loads

  • Instagram

  • The app has a TON of cached data

  • Much of the app functions as normal

  • Videos play, pictures are shown, search shows cached results, your own page loads

  • Foxtrot

  • The UI mostly loads, buttons work, but no results are pulled up

  • Browse does not work

  • The app has quite a bit of offline functionality

  • Nike

  • Same as foxtrot, the UI loads, but any module that requires data from the internet does NOT load

  • Most views return an error

  • Steam

  • Same as the above, navigation works, but data within the views do not work

  • Displays errors

  • Uber

  • UI Loads, but only displays navigational buttons and other hard-coded elements

[nicholasri]

Additional Findings

Upon further research, I have decided to go with MongoDB Atlas instead of CoreData. From my understanding, CoreData is NOT a database and is used only for local persistence. MongoDB Atlas is a Database as a Service that allows us to sync our MongoDB database in real-time to our mobile applications. Site: https://cloud.mongodb.com

I am also using Studio3T to access the data in the database: https://studio3t.com/ . You can get the URI by going to MongoDB Atlas -> SanFelipeStudios -> RomeTwo -> Data Services -> Connect.

I have sent an Organization (SanFelipeStudios) invite to dusharmrome@gmail.com for MongoDB Atlas and create the project RomeTwo.

The code I will be pushing to our project will be from the Realm SwiftUI tutorial: https://www.mongodb.com/docs/realm/sdk/swift/swiftui-tutorial/#std-label-ios-swiftui-quick-start

Follow up

Following this story a few things need to happen:

• Ability to Authenticate users via Email, Google, And/Or Apple.
• Middle Layer Service to handle Sensitive data and logic
• Modify the existing code to implement our own data models.
• Ability to enter data into the database as a user

Things to consider

While I have defined an object as such

• User
  • ID: UUID
  • Name: String
  • Address: String
  • Phone: String
  • Cart: Cart
  • Wishlist: Wishlist
  • Payments: [Payment]
  • Library: [Game]

I believe Library: [Game] can be Library: [Game.id], same for Payments and all other variables referencing other objects. The example I am going with is similar to ItemGroup in the Realm Tutorial