This article is part of the MultiViewAdapter cookbook series. With this Cookbook series, you can learn about various recipes of building most complex RecyclerView adapters.
Adding the selection/choice mode to an adapter is complex. It is more complex when you have to implement both single-selection and multi-selection into a single adapter. Not anymore. With MultiViewAdapter you can build the most complex selection mode inside a single adapter. In this cookbook recipe, we will learn how to build the following screen.
Bob is working in a product based start-up. The start-up is fast-moving place where people are building different products and everyday there is a release for one product or another. Bob is currently responsible for building a news feed app. In this app users will be able to see news headlines from different news sources. …
First things first. So what is ItemDecoration? This is how official doc puts it.
An ItemDecoration allows the application to add a special drawing and layout offset to specific item views from the adapter’s data set. This can be useful for drawing dividers between items, highlights, visual grouping boundaries and more.
We can not simply say that ItemDecoration is just a divider with a fancy name. It’s much more than that. A divider, as the name suggests, can only be drawn between items. But ItemDecoration can be drawn on all four sides of the item. ItemDecoration gives full control to the developers in measuring and drawing the decorations. …
RecyclerView is an important widget in the Android framework and a large percentage of the Android apps out there use it. It’s a powerful tool that covers many generic use-cases. However, because of this flexibility, there’s a bit of work involved to create an adapter.
The support for multiple viewtypes was one of the advantages of RecyclerView over legacy listview. But displaying multiple viewtypes requires a lot of boilerplate code. It can quickly get out of hand if you have more than three viewtypes. You may have multiple if-else conditions, switch cases, and so on. …
Recording all the thought process involved.
For the past few days I was working on redesigning an android app. The Project is still in closed beta stage, so I can’t reveal more information about it. Recently I joined the team, and my first job was to improve the current app design and redesign every screen. In this post I am going to explain all the thought process involved in redesigning a particular screen. Enjoy Reading.
That particular screen was so simple. There is a listview, each list item has a Title, sub text and an Icon. Each list item represents a content, say a news agency, which can be followed/un-followed by clicking that icon. …
It looks too simple
Don’t you think it has too much space
Ah! There is nothing here. It looks empty
These are the reactions usually visual designers get while designing an android app or probably any other software product with the flat design approach(I could vouch for android apps because i work on that platform). I, personally, love flat designs and reason is simple. It can be directly attributed with the minimalist design. No Chromes or gimmicks, just the content.
While designing apps with such flatter approach you will get the above criticisms, not from the users, but from your team. From your co-designers. From your co-developers. Even from someone who is called conscience. And that is the problem. …
Post intended for Mobile App Designers & Developers, UI & UX Strategists, App Owners and Splash screen lovers. The post shows how I usually explain my clients to avoid annoying splash screens.
Its been almost a year, I started out as an android developer after my graduation. Since working as Freelance Android Designer and Developer apart from my full-time job, I usually face this critical situation. All my clients when briefing their requirements usually start with this requirement.
—“Show a screen with our logo/icon for five seconds while opening app”
—“Oh! A Splash Screen.. But, why?”
—“It will make the app look professional..” …