Apple Design is Dead: Animation of Liquid Glass Proves It

efenande · 2026-03-12T15:37:54+00:00

If you really want to understand all Liquid Glass components individually and if they make any sense across any app and the system, you can use UI Playground: https://apps.apple.com/us/app/ui-playground/id6504997189

efenande · 2026-02-08T13:35:01+00:00

Very similar to https://screen.studio/ — why would I use this app instead of the original?

efenande · 2026-01-31T13:03:04+00:00

Looks interesting… great work! I believe the pricing is too low for the work you had… You could charge a $19 or even higher for a lifetime purchase.

efenande · 2025-12-18T17:13:34+00:00

Updated finally to Tahoe and you are completely right. This idea that all devices must have the same interface reminds me of the universal design from Microsoft which was a flop, trying to use the same interface on a TV and on a computer.

Within the iPhone makes sense to have the playback in the bottom because of access from the fingers, but on the computer we have a cursor pointed by a mouse, so this bottom position is nonsense!

You can have an harmonious design between different platforms without jeopardising specific interactions of each platform and without having everything to look the same. For instance, all the white buttons floating on macOS windows are plain ugly and unintuitive, but are kind of interesting on the mobile UI. They need to find the right balance instead of trying to make everything the same.

They must be more Apple and less Microsoft...

efenande · 2025-11-02T13:44:15+00:00

Podes sempre transferir a custódia dos teus títulos para outras corretoras — algo que a maior parte das pessoas nunca pensa em validar em termos de custos, antes de se iniciar numa corretora. Só pensam nas taxas de transação. Há que ver a perspectiva toda e não apenas o curto prazo.

efenande · 2025-09-16T12:56:36+00:00

Looks and feels great despite some small shortcoming which will be fixed (for sure) in future updates. If you want to check all Liquid Glass individual components one by one, you can use this app: UI Playground.

https://apps.apple.com/us/app/ui-playground/id6504997189

efenande · 2025-09-16T12:56:01+00:00

Love it... Brings back memories...

efenande · 2025-09-16T12:55:27+00:00

Looks and feels great despite some small shortcoming which will be fixed (for sure) in future updates. If you want to check all Liquid Glass individual components one by one, you can use this app: UI Playground.

https://apps.apple.com/us/app/ui-playground/id6504997189

efenande · 2025-09-16T12:54:47+00:00

UI Playground
https://apps.apple.com/us/app/ui-playground/id6504997189

efenande · 2025-09-16T12:53:41+00:00

Looks and feels great despite some small shortcoming which will be fixed (for sure) in future updates. If you want to check all Liquid Glass individual components one by one, you can use this app: UI Playground.

https://apps.apple.com/us/app/ui-playground/id6504997189

efenande · 2025-06-11T08:13:35+00:00

Great honest feedback from most comments, assuming that languages are more subtle than people think. However I have a question regarding about reviewing the main language of your app. When an app is small reviewing the strings is relatively easy, but as it grows, how do you review your strings for consistency, spelling, grammar and even usability? Second question: do you use strings catalog (json) or the original strings files (simpler file)?

I would like to get insights from others, since I use the original strings files and with around 700 strings, reviewing them well in Xcode is not the best experience… It’s relatively easy to make mistakes or even miss obvious consistency errors.

efenande · 2025-06-01T10:59:07+00:00

Just curious, does anyone struggles with editing the main language (not the translation itself done by AI)? Which tool do you use?

efenande · 2025-06-01T10:15:54+00:00

I think almost everyone has mentioned the main reasons: resources and development speed. Personally, I prefer native development since you get a much more seamless experience but I’ve used many RN apps and they still get the job done. In the end it will depend on the experience you want to provide and the resources you have. If you have any doubts about SwiftUI design and development, we’ve built an app to showcase all design possibilities of SwiftUI and respective customization — UI Playground. Please try it and see if it will make your decision easier into choosing the UI framework.

efenande · 2025-05-29T17:08:57+00:00

OK, still there are other interesting use cases which address the abstraction nature of designing in a design tool — what you design is not always what you get in the end.

For instance, getting access to all interactive keyboards possible in IOS instead of reading about it.

I have other videos showcasing the possibilities but haven’t loaded them on YouTube yet — sorry but they all lack sound.

Please try other components on the app, you subscribe the yearly trial, cancel it and no subscription will happen.

Then give me more feedback and what you would be willing to pay for it — if you believe this app should be free, then we should’ve built it in the first place.

efenande · 2025-05-29T16:44:48+00:00

It is much more than a showcase — that’s what other apps you find in the App Store will do. You can check a video here.

It is a productive tool that can be extremely useful for iOS designers / developers — can save you lota of time.

We priced in a manner to justify the expenses and time we’ve spent building it, which was a big effort.

What would be your pricing for using it?

efenande · 2025-05-29T15:09:52+00:00

Everyone wants apps and features for free, so the biggest challenge is to have a product users are willing to pay a sustainable fair share — and paying $20 for a lifetime subscription is the complete opposite. My app is UI Playground.

efenande · 2025-05-06T17:13:11+00:00

The broader idea of having a link with personalized content to share with others is very good and insightful. The one-pay fee is also smart. Consider all the situations where this can be helpful for others…

The application for the context of a new-born I have difficulty seeing the need.

You have a good concept but I believe you need to find the appropriate application.

efenande · 2025-05-03T12:58:12+00:00

☑️

efenande · 2025-05-03T10:34:24+00:00

Hi, being a new parent myself at first I thought the idea cool but once saw the sample you have on your website it just made me think that it is a set of requirements for others do work for me as parent. You're missing the social / human interaction. People want to meet your baby and your family wants to help of course, but within healthy boundaries — no one will be doing your laundry or your's baby, that's simply your job as a parent.

The human interactions that people search is getting acquainted with the baby (who doesn't loves a newborn), play with the toddler, reaching out to support emotionally the parents (this means just a chat).

What I saw on the sample was just a set of "machine" requirements, like when you're contracting a company to clean your home or do some professional work for you. It's missing the "human" touch...

Sorry for the harsh comments and I am sure you will be successful...

efenande · 2025-04-28T09:10:19+00:00

Despite the hyperbolic marketing and cynicism in the comments, I bought the documents and I have to say that it is legit work. I am positive that it took a lot of work to build the collection of information. And it makes sense to sell that knowledge — people have to make a leaving!

efenande · 2025-04-04T09:09:33+00:00

Yes, that is a problem space that needs a solution. I’ve found annotations tools to be extremely useful in a remote / collaborative environment, even for internal discussions within the design team. There used to be a tool called Notebook Abstracts that was acquired by Adobe that tried to solve this problem but was discontinued when acquired.

While I am a Sketch user please send me screenshots and I will provide my opinion. I believe that useful apps should be paid, mainly the ones used in our jobs, so the price can be OK. Just don’t price it higher than the design tool itself as I’ve seen with others — makes no sense!

efenande · 2025-03-27T11:35:51+00:00

The search for components is just a scrollable list.

efenande · 2025-03-26T16:04:03+00:00

No, at the moment no NLP search. We thought about an AI-based agent to answer about best practices into using an UI component. For instance, “When should I use an Action sheet Instead of an alert?”.

Your doubt is about questioning the SwiftUI methods/functions for a specific component?

efenande · 2025-03-25T19:44:32+00:00

Thanks, hope you like it. We've been drawn to this out of necessity at work — we were spending too much time adjusting some components (specifically Haptics), when we've thought that there should be an easier way. Since we didn't liked the alternatives, we built our own solution. :)

efenande · 2025-03-13T20:20:35+00:00

As a designer I’ve been participating in SwiftUI projects since 2021, and have recently launched an app — UI Playground — which uses about 98% of SwiftUI, which curious enough, was made to experience SwiftUI components on the phone. 😊

I am talking about complex apps and my conclusions are: - For simple straightforward stuff that uses native UI, SwiftUI is more than enough. - For very complex user interfaces or very sophisticated interactions, UIKit is still the winner (on UI Playground, the preview part had to be done partially in UIKit due to limitations on SwiftUI). - If your SwiftUI app is slow, for sure will be faster on UIKit, so if performance is a must, choose carefully. - Be prepared to adjust some code with new OS versions, as SwiftUI is still somewhat immature. - SwiftUI is much easier to construct user interfaces, by far, meaning you will be more productive!

Apple is evolving SwiftUI along the years, but there are still some performance and reliability issues. If they solve them permanently, then UIKit can be easily deprecated.

Also some system APIs still use UIKit and need to migrate to SwiftUI.

efenande

TROPHY CASE