Filter
Exclude
Time range
-
Near
A great AI product isn't the one with the most features. It's the one users open and instantly know how to use. What really wins people over is saving time, reducing mistakes, and making them want to use it every day. #UserExperience #MobileApp #ProductInterface #FeatureButtons
2
The real evolution of AI tools isn't becoming more complex, it's becoming more human-aware. It knows you want the result, not the steps, so more products are hiding the complexity and givi... @TheVerge @Engadget #UserExperience #UserFlow #ProductInterface #ShortcutButton #AiTools
2
🚁 Sleek design meets sky-high innovation—explore how drone tech could look Tesla‑style in 3D. This concept reimagines Tesla’s aesthetic for a futuristic drone interface with clean 3D visuals, intuitive controls, and responsive layouts. What do you think of this concept? By Angel Villanueva for Orizon🚀 #UIDesign #UXDesign #UIUX #ProductInterface #TechConcept #UI #UX #Drone #Tesla #OrizonDesign
1
93
10 Jul 2025
Do you keep writing the same fields in multiple GraphQL queries in Magento? If so, just use a fragment, like this one for repeating price fields: ``` fragment priceDetails on ProductInterface { minPrice: price_range { minimum_price { regular_price { value } } } } ``` Then just just the alias name, spreading it like `...priceDetails` wherever you need to use it. It's the DRY principle for GraphQL. Get the full Magento GraphQL course -> go.m.academy/6c5
138
10 Jun 2025
Using Object Manager in Magento code is still a pattern I see way too often in custom Magento modules. Let's fix it. ❌ BAD: ``` $productRepository = \Magento\Framework\App\ObjectManager::getInstance() ->get(\Magento\Catalog\Api\ProductRepositoryInterface::class); $product = $productRepository->get('my-sku'); ``` ✅ GOOD: ``` public function __construct( private ProductRepositoryInterface $productRepository ) {} public function getProduct(string $sku): ProductInterface { return $this->productRepository->get($sku); } ``` // WHY DOES THIS MATTER? Using Object Manager directly breaks dependency injection: - makes your code harder to debug - violates Magento's coding standards - doesn't create explicit dependencies in classes Injecting deps within the constructor keeps your dependencies clear and your code maintainable. The only time you should touch Object Manager? In factories, proxies, or backwards compatibility - and even then, think twice. What other Magento anti-patterns drive you crazy?
2
2
211
So how do we make new image role visible for #GraphQL ? We just need to add a file etc/schema.graphqls that's extending ProductInterface.
That sounds pretty confusing imo. I do like to do the same thing, but with variables, or class properties. (I.e. request a ProductInterface, but call the variable $product.
1
4
Replying to @rajkbnp @MarkShust
I agree with @max_pronko about the typo. However, I like to alias anything with Interface to eliminate that. For example, I’d alias HttpPostActionInterface to HttpPostAction. Or ProductInterface to Product. Interface really isn’t necessary in my opinion.
2
4
Replying to @LBajsarowicz
Import does not work on the level of ProductInterface and service contracts
We collaborated with a #DataMapping platform to enhance their internal processes, #ProductInterface, and codebase through product interface #design, rapid feature #prototyping, and #development. #ThinkRefined21 thinkpo.st/interactive-mappi…
1
@bigbasket_com No use of these images. Please note. High Def images are needed. #bigbasket #productinterface
2
1
How to add custom attribtue in the ProductInterface of GraphQL response? bit.ly/2EiXW4k

1 Sep 2020
hi #magento folks, what do you think about removing dynamic parts from the ProductInterface at GraphQL? github.com/magento/architect…
4
9
Get a dropdown attribute value from ProductInterface, without breaking interface contract bit.ly/2Q7ZjXi

This should help on a PHP framework level without DB reflection: /** @var Magento\Framework\EntityManager\MetadataPool $metadataPool */ $metadataPool->getMetadata(ProductInterface::class)->getLinkField()
6
22