Spryker Developers – We Want Your Feedback!

Hidran Arias
Hidran Arias Senior Technical Trainer Sprykee Posts: 95 🏛 - Council (mod)
edited March 21 in Spryker Development

Hey Spryker devs!

At Spryker Academy, we’re constantly working to improve our learning materials—whether it’s how-to guides, instructor-led training, or other educational content. To make sure we’re addressing real-world challenges, we’d love to hear from you:

What have been your 5 biggest pain points when developing Spryker projects?

Are there specific areas where you’ve struggled—project management, setting up your environment, debugging, understanding module dependencies, performance tuning, or something else?

Your insights will help us refine our content, create better learning experiences, and support the community in tackling common challenges.

Drop your thoughts in the comments!
Thanks!

Answers

  • KFrw
    KFrw Developer Posts: 3 🧑🏻‍🚀 - Cadet
    1. Boilerplate code. You have to write so many files and code to do the simplest things.
    2. Too many modules that are all of very different quality and various states of what was a Spryker standard as they where build or upgraded.
    3. Too many rather useless transfer objects. And everywhere just fromArray toArray transformations for this.
    4. Dependency Injection is a pain to write and not used everywhere. Sometimes its just the factory I have to use. Somethings are just created by new. I really would love to inject everything everywhere and with a lot love and magic.
    5. More centralized code. Reuse of constants. More Services. Please don't just tell me I can do in my project what I want. Because we want / have to use spryker and it's common patterns.
    6. So many more 😅 Sorry

    Cheers Karsten

Categories