Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(45)

Solar Industry(8)

User Experience(68)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(8)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(146)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(21)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

5 Take Away points from Droidcon 2016

Droidcon is a global developer conference series focusing on the best of Android, supporting the Android platform and creating a strong network for developers and startups. Droidcon covers all aspects of the Android ecosystem from mobile devices, to TV, to cars, to gaming, and so much more.

The idea behind the droidcon conferences is to support the Android platform and create a global network for developers and companies. The platform offers high-class talks from leaders from different parts of the ecosystem, including core development, embedded solutions, augmented reality, business solutions and games.

The speakers of the conference were some of the leaders from Android space, Yigit Boyar- Google Express, Dario Laverde- HTC, Jenny Yuen- Software Engineering Manager – Android at Facebook, Evelio Tarazona Caceres- Lyft, Israel Ferrer Camacho- Twitter, Christina Lee- Hightlights, Huyen Tue Dao- Trello and many others, who spoke about Android Development and the future of Android.

The 5 take away points from this conference were:

  1. Application Architecture:
    An application architecture describes the behavior of applications used in a business, focused on how they interact with each other and with users. It is focused on the data consumed and produced by applications rather than their internal structure.Yigit Boyar explained the need and necessity of Application architecture in developing mobile applications that can work offline as well. Mobile networks are unreliable and if the application does not account for it, your user suffers from the worst user experience, which would in return affect your application; this motivates developers to design an application that can work offline and improve user experience with better architectural decisions from online behavior.
  1. Auto Profiling Apps on Every Build:
    Evelio Tarazona Caceres of Lyft highlighted, not only Architecture alone, but performance also is always a concern when working with resource constrained environments like Android. In addition to that, developers also have to deal with another limited resource: time. It is quite common that adding new features or fixing bugs is way more relevant than ensuring the application works smoothly. Just measuring the performance of certain view takes a good amount of time, so why not automate it?“At Lyft we found that gathering data with every continuous integration build would help us to not only detect regressions but also to ensure a smooth ride for all our users.”, He added.

  1. Borrowing The Best of the Web to Make Native Better:
    Christina Lee while addressing conference, said, “The fast iteration of the web has yielded several very promising paradigms to mitigate problems by thoughtfully separating concerns.” She spoke about how they are exploring ways to borrow principles from React, Flux, Redux and Cycle. JS to bring the best of web data flow management to Android Applications. She provided an overview of the relevant principles, including samples from apps in production.
  1. Fluid Gesture:
    Material design on Android
    has ushered an age of delightful animation and meaningful transition leading to more engaging and sophisticated Apps. Eric Leong laid emphasis on examples of unique, but effective gestures, especially those unique to certain App Categories. To demonstrate the ease of developing a gesture-based interface, even in a production application. Eric used Tumbler Gestured, to show how important is implementing gestures using a backboard and rebound, libraries that help tie user interaction to on-screen motion.
  1. Loving Lean Layouts:
    XML Layouts are a fundamental part of android development at all levels. Getting started is a straightforward but creating an efficient layout while still achieving a high level of control, takes some practice and few tricks

Android powers more than 80% of smartphones worldwide and shipped on over 1 billion devices. However, Android forks now account for over 20% of the global Android ecosystem and 41% of new devices. The Droidcon covered all aspects of the Android ecosystem, provided overview of future of android and revealed statistics and introduced specific strategies to help developers reach a wider audience with their applications.

 

Cancel

Knowledge thats worth delivered in your inbox

Design Systems: Building and Maintaining Consistent UI/UX

In the world of product design, consistency is the cornerstone of delivering a seamless user experience. As digital products evolve and scale, the challenge of maintaining design consistency across multiple platforms, teams, and touchpoints becomes more complex. This is where design systems come in. A design system is a comprehensive set of guidelines, components, and tools that help designers and developers create a consistent and cohesive user interface (UI) and user experience (UX). From a designer’s perspective, building and maintaining a design system requires a strategic approach to ensure scalability, flexibility, and alignment with business goals.

Why Design Systems Matter?

Design systems are more than just style guides or pattern libraries. They offer a unified language for design and development, bridging the gap between creativity and functionality. Here are a few reasons why they are critical:

  1. Consistency Across Products

      One of the primary goals of a design system is to ensure uniformity across different platforms and devices. When users interact with a product, whether on a website or a mobile app, they expect a consistent experience. A well-implemented design system ensures that visual elements, interactions, and behaviors are aligned, offering a familiar and intuitive experience for users.

2. Faster Iteration

      With a design system in place, teams can reuse components and patterns rather than reinventing the wheel for each new feature. This speeds up the design and development process, allowing teams to focus on solving new problems instead of reworking existing designs. For designers, it means less time spent on repetitive tasks and more time dedicated to innovation.

3. Scalability

     As products grow and new features are added, maintaining a coherent UI/UX without a design system can become chaotic. A design system provides a scalable framework, enabling teams to add new elements or modules without compromising the overall consistency of the product.

4. Improved Collaboration

      A design system fosters collaboration between designers, developers, and other stakeholders by providing a shared language and reference point. This ensures that design decisions are communicated effectively, reducing friction and misunderstandings between teams.

Building a Design System: A Designer’s Perspective

Designing a system from scratch can seem like a dau