The MILK API is very flexible in how it can be integrated into an application. In any integration there are 2 parts:
How much UI is developed inside the application is dependent on what point the user is swapped over to the webview.
Regardless of which process is selected, the user flows though the same steps:
Content Selection | → | Product Selection | → | Product Configuration | → | Basket Configuration | → | Shipping Details | → | Payment Details | → | Order Confirmation |
This option allows most of the process to be handled by MILK. This would be a good option if you didn't want to invest in a custom UI and wanted a quick and simple integration.
APP | API | WEB | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Content Selection | → | Product Selection | → | Product Configuration | → | Basket Configuration | → | Shipping Details | → | Payment Details | → | Order Confirmation |
The basic flow would be build via the following integration points:
This option allows most of the process to be handled inside the application. This option would be a good choice if you had requirements to build a heavily custom native UI and have a lot of control over the process.
APP | API | APP | API | APP | API | APP | API | WEB | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Content Selection | → | Product Selection | → | Product Configuration | → | Basket Configuration | → | Shipping Details | → | Payment Details | → | Order Confirmation |
The advanced flow would be built via the following integration points (also see Examples):