I’ve been working on a small Android app UI concept for a few weeks now, nothing too serious, just trying to improve my design flow and understand system behavior better.

What keeps confusing me is how inconsistent everything feels across devices. On my main test device, animations feel smooth and spacing looks clean. But when I tested the same build on an older Smart phone, everything felt slightly off. Same layout, same assets, but the experience just feels different.

I started wondering if I’m designing wrong or if this is just normal in Android development. Maybe I’m not accounting enough for refresh rates, chip performance, or even how different OEM skins handle rendering.

At one point I was digging through UI references and somehow ended up looking at component listings on Alibaba, just trying to understand what kind of display modules and hardware specs manufacturers are actually using in lower tier devices. I wasn’t looking to buy anything, just trying to connect the design side with real hardware limitations.

I guess what I’m trying to figure out is how much designers should actually adapt their UI thinking for weaker devices instead of assuming a “standard” Android experience exists.

For people who’ve shipped apps across multiple Android devices, do you design with the lowest end Smart phone in mind first, or do you just optimize later when issues show up?

Hi everyone! 👋

I recently completed Kotoba, a UI/UX concept for a secret messaging app inspired by the childhood code languages many of us used with friends. Instead of plain text, Kotoba lets users communicate through emoji, color, and pattern-based codes to make conversations more playful and personal.

I'd really appreciate your honest feedback on the UI, UX, visual design, case study presentation, and overall concept. Any suggestions—big or small—would mean a lot and help me grow as a designer.

🔗 https://www.behance.net/gallery/251827989/Kotoba-Secret-Messaging-App-UIUX-Case-Study-2026

Thank you for taking the time to check it out! 😊

I have released a productivity platform Todolu.

It has getting a good traction, but I feel I am not doing justice to the application by uploading basic screenshots to the PlayStore. I see all other apps have fancy screenshots depicting clear purpose and taglines.

I tried creating some screenshots but Playstore rejected them.

So I need inputs from folks here which tool they are using to build screenshots and what are the things I need to take care of so that the play store accepts the screenshots.

​

https://pashapumadesign.com/news/new-google-icons-style-2026/

After months of work, Vollthex is officially on Google Play. These wallpapers actually react to your phone. Battery draining? The wallpaper dims. Missed a call? The aura changes. Day turning to night? The wallpaper follows.

Some wallpapers work as an overlay , keep your own photo as the background and let the animation breathe on top of it.

Not loops, not gifs, real-time, every frame.

Battery and performance are a priority. There's even a dedicated Eco Mode for when every percentage counts.

Give it a try, maybe you'll like it, maybe you won't.

https://play.google.com/store/apps/details?id=com.vollthex.app

Desde que Google implementó transparencias en su sistema operativo Android, pensé en como se verían los iconos temáticos si tuvieran transparencias, este es mi concepto

The market is now saturated from AI-made standard-looking apps so I was thinking of taking an entirely different approach to get users' attention.

The app is named NeoMusic. It has:

- LCD-style screen that changes color with album art

- Knobs and buttons with haptics

- Fully hand-crafted neon theme

- Equalizer right there in the player screen

- Custom colors

- AMOLED mode

Everything done using Compose Canvas API, without any Material components.

You can check it out here: https://play.google.com/store/apps/details?id=com.tashila.neomusic

I was trying out sth new with this app so I'd love to know what you guys think!

Hey everyone! 👋

I’m currently building an AI-based travel app (startup idea) and we are already in the mid stage of development.

Now looking for a UI/UX designer to help take the app to the next level.

✅ Open to freshers / beginners

✅ Great for building your portfolio with a real product

✅ You’ll be credited as the UI/UX Designer of the app

💡 What you’ll get:

•⁠ ⁠Real startup experience

•⁠ ⁠Strong portfolio project

•⁠ ⁠Public credit (LinkedIn / app / resume)

•⁠ ⁠Opportunity to continue if the project grows

⚠️ Note:

This is an early-stage startup, so I won’t be able to offer payment or equity at this stage.

🛠️ Tools required:

•⁠ ⁠Figma (mandatory)

•⁠ ⁠Basic understanding of mobile UI/UX design

📋 If interested, fill this form:

[👉 https://forms.gle/1TVxwWfzTwDt28HK7 ]

or else you can Dm me

I’ll review your responses and reach out to you directly.

Let’s build something impactful together

Elige la oscuridad

I’m an engineering student and I built EngTools, a clean, practical engineering toolkit for everyday calculations. If you try it out, I’d really appreciate feedback or a quick review:)

https://play.google.com/store/apps/details?id=com.appogeelabs.engtools

Hello, for some time now, on my Realme GT7 Pro, with Realme 7 UI, I've been experiencing some inconsistency in the notification icons. Why does the WhatsApp icon have a background and the Gmail icon doesn't? The same thing happens with Instagram. Is it a problem with Realme UI, the apps themselves, or what? :S Thanks

I’m working on a "Life OS" concept and I’m trying to balance two conflicting things:

​Information Density: Having Tasks, Health, Meetings, and Journaling available at a glance.

​Minimalism: Keeping it from looking like a cockpit.

​I used a heavy dark theme with high-contrast accents for the progress rings. I also added a "Moments" capture flow that’s meant to be one-tap.

​Does the hierarchy make sense to you? Is the dashboard too crowded, or does the "at-a-glance" value outweigh the density?

Hey folks,
I wrote up a concept for an adaptive multilingual keyboard — a keyboard that detects the language you’re typing in (even mid-sentence) and switches autocorrect, suggestions, and layout in real time.

I explain the approach (on-device language model + federated learning for personalization) in a short 1-page PDF:
📄 [Adaptive Multilingual Keyboard — Concept by Emilio De Alba]()

I’d love feedback from developers or ML folks on technical feasibility and architecture — especially around small on-device models for real-time detection.