with (axokxi) /collab/Exploring Delayed Communication
- Paying attention to Time-axis Oriented Communication, aiming for a chat app that is not time-axis oriented, like a game of “tamaire” (a traditional Japanese ball game).
- Aiming to break free from dependence on the time axis.
Implementation policy:
- Architecture:
- Interested in MicroViewController.
- For now, just focus on Clean Architecture and think about the details myself. It seems interesting to try even if it collapses later (I’ll be the only one struggling).
- Something like this? (The left is the current understanding of MVP, and the right is a possible alternative)
- Well, either ① it already has a name or ② there is some problem, but I’ll try it with this anyway.
- UseCase:
- The ones for getting and posting.
- In the current specifications, once sent, it cannot be edited, but if it changes in the future, it will be added as a UseCase.
- Data storage:
- People.
- Cards.
- It seems that it will be more common to refer to them by following the network rather than in chronological order.
- Interested in Graph Database.
- Well, maybe it’s not necessary.
- What would be the best way to store data with a structure like GitHub commits?
- In the end, is Firebase Realtime Database the most suitable?
- UI:
- /collab/Cards UI Design 0524
- Want to make it Fluid Interface-like.
- Hero.
- List of things to create:
- LINE login.
- Scrollable UI for the home screen.
- Editing screen.
- Various things related to Firebase.
- Creating Things That Work Even When Small is important.
- Want it to work by the end of Saturday.
- (axokxi) (/icons/thank_you)
- Things the view needs:
- Information about the cards to display on the home screen.
- Arrange them in chronological order.
- Want card information from the ID.
- Want to know if it’s new.
- Information about friend users.
- Information about the cards to display on the home screen.