metarhia / metacom-ios Goto Github PK

Current version of user interface looks like a prototype. It's not ugly, but not good at all. So I propose to try to create new pretty version of GUI based on a current navigation logic. I doubt that we will look for a graphical designer for this project, that's why I can try to do it myself, but only if you, @GYFK, will approve this task.

We need new functionality: before exit user may want to save history to the text file.
For iOS all files should be stored attached to certain application, so I think we will not store files attached to Metacom. Better export to different apps (registered in system), cloud storage apps, etc. @GYFK

I propose to replace MessageType in Message class with an enum with associated values, something like this (it's only concept and should be discussed):

public enum Content {
	case text(String)
	case image(UIImage)
	case file(Data)
}

Remove property type and replace let content: String with let content: Content.

@GYFK If you are agree, I'm ready to work on this modification.

@GYFK I don't understand a purpose of MessageReceiver protocol. If only notification about new messages, then didJoin() and didLeave() methods are excessive. In other case, it shouldn't be called like MessageReceiver, but ChatRoomDelegate. Also mentioned above methods' names are too short and provide no info about the sender. I suppose we should follow delegate methods naming like chatRoom(_ chat: ChatRoom, didReceiveMessage message: Message).

Integrate application with the server API presented in metarhia/metarhia.com#24

UI for the first version of MetaCom will be created according to the referenced mock (see metarhia/Metarhia#9 (comment)). @GYFK, what do you think? Do we need to create app design in Sketch? Or we can start creating layouts for application in Interface Builder?

I don't know does it implemented for iOS app? @GYFK
See android issue: metarhia/metacom-android#7

Create Controllers relating UI elements developed in process of #1

We need white logo on black. This is not Metarhia logo, this is solar eclipse:

We should decide how user will select files for uploading. There are two common ways:

1. Add MetaCom to the system's share menu to accept any files:
   

2. Allow user to select files from iCloud Drive:
   

I suppose we should provide both options.

The first one is a little bit complicated because we should handle file receiving in any point of an application’s lifecycle (e. g. if there is not an active connection, let user to setup it; or to specify a chatroom, if needed; etc).

The second one requires Apple ID enrolled into Apple Developer Program. So, it can be added later.