How to organize a custom Android interface to select the type of connection?

Develop a simple chat with a choice of podkluchenie via Bluetooth, USB or TCP/IP. How best to organize the interface so it looked natural for the platform? The sequence of user actions is the following: select the type of connection (MainActivity), configure the connection for the selected type (for example, choose a bluetooth device for pairing (BtConnectionActivity)), to enter in chat (ChatActivity)


Interface to the MainActivity so far


but I think it looks somehow clumsy. Are there any standards/recommendations?
July 12th 19 at 17:11
2 answers
July 12th 19 at 17:13

Anyway, take a look at the application from the point of view of the user first started the application. What kind of buttons? What will happen after clicking on any of them? In this case, IMHO, can help a brief description, select the type of connection and the "Connect"button.
July 12th 19 at 17:15
1) Obligatory padding (internal fields on all sides activity)

2) Buttons should not be too large, it is confusing on any platform. For mobile phones (NOT tablets), it is sufficient to make them standard height and length to the screen (all at center), or horizontally placed, each 1/3 of the screen (+padding). Alternatively, the standard dialogs are to try, then maybe the tablets will be from the rules without crutches, do not try.

3) there Should be a brief explanation of what it is and what.

4) ...And then we gradually come to the main observation on this issue:
And why do we need it? What is the purpose of the 3 modes and what is the purpose of this dialogue at this point?
What is chat via Bluetooth or USB, you really need such a miracle to the user?
If all that is really necessary to burden the user, the captions on the buttons (or the explanation) should be done on this basis, and our jargon about "TCP" user do not know it is required.
Maybe not necessary, just make option 1 the default, then in the settings?
If you do everything topsy-turvy first to invent a solution, and then try to harmonize it with the task (instead of having to first put the problem, and then to solve it) - the convenient interface will not work.
Actually it is more complicated than chat, but for example, I took a chat. About the option "by default, and the rest in settings" I have considered, but then users don't immediately find out about alternative options for connection. - Verla_Fay commented on July 12th 19 at 17:18
: design should be functional = to match the task. No problem all this has little meaning.
And so, you can only throw ideas. For example, in the dialogue to use RadioButton instead of the usual buttons, then one of them by default already selected and if the user doesn't want to penetrate, it just presses the "OK"button. - delta_Bart commented on July 12th 19 at 17:21
> in the dialog to use RadioButton instead of the usual buttons
Yes, there are several alternatives. I'm more interested in how it will look on different screens? On the phone seems to be fine, but a few items in the corner (or middle) and plenty of space? I tried to draw an analogy with the tethering setup, you can also choose the connectivity options. But there is a user purposefully enters the settings, because he knows what he wants to do. And if I start your application from activiti with the settings, but will not really understand what to do. - Verla_Fay commented on July 12th 19 at 17:24
: > on the tablet of elements in the corner (or middle) and plenty of space?
In the middle.
What's wrong? Noob you green, under Windows, probably not wrote, just started with mobile-linuxce OS. If I wrote, maybe you would know that the MessageBox in the middle is great, but sucks when he's not in the middle, and if he swells up the entire screen, then the user generally will not know that this huge area is a button and press it.

> And if I start your application
If Yes, if it grew mushrooms in his mouth. Without tasks it's pointless to discuss. - delta_Bart commented on July 12th 19 at 17:27

Find more questions by tags Android