The back-end design and architecture of the application should consider a multi-user environment, although this is not required for the moment. The back-end design should consider an extension to iOS later on, however an iOS based front-end is not required for the moment. It must not mess with the phones contact.Īlso it must be usable via browser (Chrome is sufficient). The contact-managers front-end must run on Android devices for now. so the contacts can get imported seamlessly. The contact-manager should be able to authenticate against LinkedIn, etc. I don't want the user to export their LinkedIn contacts to an excel sheet and later on manually import it to the conctact manager. data from linkedin to contact-manager, not the other way round). ![]() ![]() One-way synchronisation is sufficient (e.g. The import mechanism should use the APIs provided by the mentioned plattforms. The architecture design should consider an extensibility for other potential social platforms. The application must be able to import contacts from a) LinkedIn, b) Google Contacts and c) Xing for now. I am going to call this application contact-manager in my further description of the requirements. ![]() I need a web application that can aggregate several contacts together.
0 Comments
Leave a Reply. |