spanishqert.blogg.se

Flinto to ios
Flinto to ios











flinto to ios

This would enable us to release an MVP even without animations, if we ended up not satisfied with the result. Since we lacked the experience of implementing animations in React Native, we decided to leave them for the end. Our designer did a great job creating the animations in Flinto, to help the developers know exactly what to develop. Since the design phase is always executed before the development begins, we knew right at the beginning that the app would have quite a few animations. I agree, there is nothing that makes the app look more polished than animations.

#Flinto to ios software#

We are very design-driven and our designers, although very sensible to software limitations and constantly consulting with us developers, rarely let us compromise the design in account of faster-developed, but more ‘default-looking’ user interface. My native-oriented colleagues’ main concern was that the application will not be as smooth as when developed directly in Objective-C/Swift or Java/Kotlin and that we’d especially have problems implementing animations and customized parts of the app. The objective behind creating this app was for our iOS team to get a hands on experience with React Native, since I was the only one with prior experience building React Native applications. Just recently we published Simple Cycle - a mobile application for tracking menstrual cycles, available both for iOS in App Store and Android in Google Play. The goal was aimed at providing users a clean, intuitive screen to interact with and business teams with the best merchandising experience possible.React Native Animations - a quick overview January 10, 2018

flinto to ios flinto to ios

  • Create a global hierarchy with Add to Cart becoming much more prominent and always visible.
  • Improve display with a solid digital font (San Francisco) and increase font sizes for key info.
  • Establish a strong color style for specific actions (pricing, offers, itep options).
  • Modernize the UI & remove unnecessary graphic elements.
  • The result was to design a single PDP using conditional, modular content. The project would reach across key departments (Strategy, Buying, Tech, Product, UX) to form a working group and align redesign goals. The iOS screen worked, but I wanted to design it to work better while providing a contemporary look/feel and a relative feel to other parts of the native iOS app.
  • Simply too much info for users to process.
  • Disconnected experience in styles and interaction.
  • Monotone color scheme minus strong differentiation for calls to action.
  • The old PDP has a high cognitive load issue. Here are some issues I looked to address: The problem with the PDP is an antiquated and "heavy" UI that presented a great opportunity for higher interactions and conversion. Quidi's PDP for iOS is a highly functional screen that sees a steady 15% conversion from its best customers. Redesign the UI for the Product Detail Page (PDP) - The most important page on Quidsi's e-commerce iOS app.













    Flinto to ios