Laravel development for companies in Ludwigsburg

Of the towns around Stuttgart, Ludwigsburg has the most unusual mixture. Automotive supply and mechanical engineering are here as they are everywhere in the region. Alongside them stands a creative economy you would not expect in a town of this size.

The Filmakademie Baden-Württemberg tipped the balance. A film and media centre has grown up around it, with dozens of firms settled there. Animation, visual effects, games, advertising, design. Add to that communications agencies working for clients far beyond the region, and the whole lot is a few minutes away on the S-Bahn.

Who gets in touch

Two very different kinds of enquiry come from Ludwigsburg. One comes from industrial businesses and looks like it does everywhere around Stuttgart: a line-of-business application, an integration, a portal for customers or field staff.

The other comes from agencies. Concept and design are settled, often down to the detail, and somebody is missing who can turn that into an application that can still be updated in three years. That is a brief we are glad to take, because the hardest question has already been answered: what the thing is actually supposed to do.

What is regularly missing in projects like these

A fully designed concept almost always describes the good case. The list is full, the image is there, the name fits on one line. In the application the rest arrives.

What does the empty list say before the first entry exists? What does an error message look like that does not sound like a crash? What happens with a name eighty characters long? These states can be added afterwards, but they always look slightly stuck on. So we ask about them at the start. How we go about it is under Laravel development.

Media make storage a subject

On projects from the media world, the underestimated part is rarely the interface. It is the files. An image archive grows quietly until the storage is full or a page takes three seconds to load because a photo is being served at print resolution.

All of that is manageable, but it wants thinking about at the start. Where do the files sit, in which sizes are they served, who may delete, and what happens to the material of a project that has finished. How we cut backends for that is under API and backend development.

After launch

A portal is not finished at launch, it starts there. Content arrives, user numbers rise, somebody asks for a report nobody needed before.

We carry on looking after applications like these, with security updates, monitoring and a named contact rather than a mailbox. What that involves is under maintenance and support.