iOS, Android UI for telemedicine conversation service

iOS and Android UI for a telemedicine conversation service. The customer for this Project is a company offering medical staff the possibility to engage in conversation with their colleagues. The ability for doctors, nurses and other professionals working in healthcare to be able to chat, “walkie-talkie”, text, send images, or even to engage in a video call during a procedure will make patient care more efficient, effective and safer.

A version on iOS already exists in AppStore. We are looking to enhance that version considerably  and to introduce a brand new app on Android.

Patient privacy is a high mandate for this app. It is built to adhere to The Health Insurance Portability and Accountability Act (HIPAA) on Privacy, Security and Breach Notification Rules. New versions must be compliant with these regulations. In order to ensure the compatibility the customer is going to write the plumbing themselves in a cross-platform manner.

We are looking for a developer team to handle the entire UI layer (consumption layer). We want to create a messaging app that rivals iMessages/Facetime or the Facebook Messenger apps – except this app is secure. The customer is going to use Xamarin (formerly MonoTouch) to write the plumbing themselves in a cross-platform manner.

Your team must be able to design UI and UX/interactions, write animation and gesture controls, non-standard UI, possibly use bindings to make open source UI controls work with Xamarin as well as optimize performance threads etc.

The cooperation between you and the client will be done in MVVM style. We will give you a view model mock/stub objects that provide data so you can begin development before the code developed by the customer is complete. This will allow the customer to handle the architecture layers while your teams handle the consumption (UI) layers for both iOS and Android.

Here’s a simple example of doing cross platform with Xamarin and MvvmCross. This design pattern helps push the shared code closer to the UI than you would get without it.

The 3 pages on iOS, Android, and Windows phone UI show how the model view view-model pattern works. The main goal is to bind your UI to the view-model properties that update the UI when the values change. IOS binding is different in that it is done in code during the ViewDidLoad event but Android and Windows both use XML based and bindings are declared in the markup. In all of the platforms you can add additional view logic as well but you want to work to minimize it as much as possible.

ANDROID all new:

Download app from GooglePlay.

Register with your name, phone number, email.

Send invitations to your friends in Facebook, by emailing, or by sending a text message.

Phone will ask for permission to access your Phonebook. If allowed it will list All contacts under one tab and Contacts registered in the app in another. Contact names under “All “ will appear in grey color with those who have registered in the app highlighted in black.

Contacts active in the chat have a small green circle next to their name.

Once you have active contacts you can initiate a new message. A new message is text or email by default you can also click a microphone and open a walkie-talkie session and send images.

A videocall can be initiated by going into your stream of conversation with a person and clicking a videocamera icon.

Images and text will appear in the conversation stream.

Settings icon will open 5 alternatives: Logout Help (takes you to website) Send Feedback (opens email)   About NN Chat Cancel.

Tell a Friend icon will open 3 alternatives: Message Email Cancel.

Introduce in-app purchasing capability.


The current iOS app features all of the capabilities listed for Android. We are looking to launch a new version with considerable number of improvements including in-app purchasing “”fly-out”” menus for settings/navigation UI and many more.

The new work for iOS will also include bug fixing of some of those existing features.

Screenshots of the existing iOS app attached. We are looking for a top-notch team to bring this      and the Android app to a whole new level. The app must be smooth logical and appeal to the user. Ease of use is imperativeas the app may be used in highly stressed situations. The look&feel must bring users back and make them recommend the app to their professional peers.

We will share a backlog of dozens of future requirements under NDA with the selected developer. Similar: Tango iMessages/FaceTime Facebook Messenger Kik.

Offering medical staff the possibility to engage in conversation with their colleagues.

Please give a binding bid on your hourly rate and provide a best estimate for the overall project price.