Fully invested into the React ecosystem since 2015, I have specialised in building technologically advanced business applications. I guide you from writing user stories all the way through coding up to product release. Here is a more structured breakdown of what I do.
Build your very own component library w/ React
Oftentimes a company has structured its business into multiple microservices maintained by a number of developers across various divisions. If every project team implements its own version of a Accordion component we would not just waste resources on re-inventing the wheel, but we would also end up with an inconsistent look and feel across all of our products. Importing what you need from a standalone, agreed upon, tested and feature-rich component library unleashes a lot of potential. It encourages rapid prototyping, reusability, and last but not least plays well with agile workflows.
sushi is the corporate component library of soosap GmbH. It is heavily used throughout this website.
Convert mockups into code: Let's get real!
At this point we have passed the decision-making on what to build. Careful thought processes in early product development cycles have produced a fully mocked and ideally clickable dummy. Fully designed and sound wireframes are a tremendous first step. You avoid developer hours being spent on non-tech related questions on how your business works. Once you have put your vision on paper, all you need is a dev team that is capable of bringing these mockups to life. I use React and atomic design principles to breakdown a large application with all its requirements into approachable, testable, and reusable components. Not just will I fully comply to design guidelines set out by the product team, I can also step up and lead the engineering team if you so wish.
Make the switch to GraphQL: A trade-off analysis
When Facebook open-sourced GraphQL in 2015, not many were able to fathom the widespread use, the growth, the influence, and the value this piece of technology would unfold just half a decade later. Every React developer that has had the pleasure to interact with the declarative syntax of a GraphQL query or mutation would unlikely return to whatever existed before. The list of benefits is long: auto-generated API documentation, type-safety, developer experience, no over- or under-fetching of data, subscriptions, third-party toolings, etc. However, there is an initial investment required to set it all up. My guidance will not stop with a recommendation on whether or not the switch is necessary. I help you to implement a fully functional and scalable GraphQL server.
Lean product development: From ideation to MVP
You have identified the problem your company faces, but you are not sure on what exactly to build and how to prioritize your resources? Prior entering the tech space I have completed the M.A. in Economics (MBF) at the University of St.Gallen (HSG) and worked in the finance industry for quite some time. That is to say that I am very aware of how to bridge the gap between a pure tech perspective and entrepreneurial considerations. Let's identify the features that are most vital to your business. Articulate these features in form of user stories. Sketch these stories into visual mockups. Sync with management and sync with your customers, too. Once we have settled on what to build and once we fulfill rapid prototyping prerequisites, we are ready to call React 🤙🏾