SAP AppGyver Creator Spotlight: No-Code Hackathon Winners build a sustainable solution for power tools
Are there tools with damaged parts that you intend to discard? Do you know, those seemingly damaged parts can be replaced or recycled? The Creator Spotlight series highlights success stories from our global no-code community. Do you have an SAP AppGyver project you’d like us to feature? Please reach out or comment on this post.
In this episode of SAP AppGyver Creator Spotlight series, we are featuring the winners of SAP AppHaus #NoCode Hackathon: Weekend Warriors. The team members from both Mitre10 and Datacom share their experience on working together to create this proof-of-concept app in SAP AppGyver for recycling power tools.
Creators: Abishek Bedi, Guilherme Paiva, Heidi Chung, Daniel Yeom and Glenn Roberts
Team: Weekend Warriors (Mitre10 and Datacom)
Location: New Zealand
Solution: Mitre 10
Tell us about the No-code Hackathon Experience
Abishek Bedi: It was a great and wonderful experience. I collaborated remotely with our working partners-Datacom. We had a couple of online whiteboard session to start with. With all team members being remote, it was quite a different experience than we would have done in the room. So, designing a sustainable solution for the greater good was what we were in for.
Guilherme Paiva: It was a very good experience. Something that was totally new for me. Some really exciting opportunity using solutions like low-code no-code can speed things up. Yes, I’m very excited about this technology.
The fact that we were pitching and applying against other teams around the Asian Pac Region gave us a little bit of a jump start as well, to realize it wasn’t just a very localized event. It was pretty much quite a broad event within our region. We learned working together, but we also learned watching and seeing what the other teams presented in the challenge and in the event.
Tell Us About the Recycler App the Team Developed for this Competition.
Guilherme Paiva: The main purpose behind the app is the sustainability, and basically how we can benefit the community, and in our case, recycling batteries which is a very interesting user case.
Abishek Bedi: It was a proof of concept. We do not have the commercial availability or used case right now, but we would like to pursue this for the greater good of the community in personal capacity or if we go with the organization.
Glenn Roberts: Actually, I had a power drill, the battery worked but the drill broke. While in the brainstorming session for the problem, a team member said what they do at Mitre10. I explained what happened to my power drill and we got onto the mirror board and began to literally spitball and ideate around what solution could look like. We worked out quite quickly within their (Mitre10) domain that got products and product parts.
We agreed on the problem: What if I had a product where part of it was working and the other part wasn’t, what could I do? We came up with quite a broad concept to either recycle, replace or replenish the product. And that meant you could donate part of it or give it away and someone else who had another working part could use it. What worked for us was that the idea came from both the corporate need but also it was a very personal experience I had as a person that likes power tools.
What Was the Design Approach like and What Challenges did the Team Face?
Glenn Roberts: We used the Apphouse design thinking methodology because Datacom is an Apphouse partner here in New Zealand. We had a bit of a play and put together an early prototype. I was helping to guide some of the business problem and the articulation, but the other team members really picked up the product and did the heavy lifting.
For us, me especially, it was a great experience to explore a low-code solution. I have a developer engineering background and I can build this, so going from something I can do to something that is brand new. Designing the solution using SAP’s available tools (because we are going the SAP way at Mitre 10) was really good.
The team’s experience was rather different as it was mainly remote. Although quite challenging, it was interesting the way we did it, as compared to sitting in a room and doing a Hackathon to juggle the timing and processes. But overall, the experience is very good.
From my side, I come from the operations background, so as you can imagine, development is not my strongest point and having something like low-code no-code really makes things easier for any sort of application. If I want to create some internal application, it is easy, and the experience was good.
It took a little while to understand and figure out how to do things, but this got better once I understood it. I helped in building the User Interface, so I had to spend 5-minutes designing. This was good, and I’m happy with the result.
Mitre10 brainstorming session
What were the benefits of using no-code capabilities?
Glenn Roberts: One of my favorite parts was watching and interactions; the three of us were online the one weekend and we were talking about variables. There was a page variable and a variable across the app and the team members were showing each other what they had learned by watching the AppGyver tutorial videos. We tried some things and failed a few times but was able to roll out a solution.
I think one thing we can take away from the great advantages of low-code no-code is that rapid build and that rapid build-fail-build-fail-success, that is what I really enjoyed watching. And before we realized it was a 2-weeks challenge, the bulk of the work happened in 1-week because of work commitments and remoteness. If you think about it, we knocked this out of the park in half the time.
Abishek Bedi: The app development was done in less than 16 hours I would say. While I was attending meetings, I was learning, and the learning element (AppGyver tutorials) was very good. I watched the AppGyver Xano video, but I agree with Glenn that there is limited out of box options. Sometimes, I felt I could just code it. that was the most challenging part for me coming from the development background. Otherwise, it was amazing, and as I said, it was done under 16hrs.
Glenn Roberts: With the low-code no-code product exactly with ABC, you could wax something together in a few hours, get it out to the users and get that rapid feedback. That is a key advantage. Again, to Abishek’s point, he built something that went to both platforms in one hit. To get something fairly quick out the door this is a good fit.
What other SAP No-code challenges to look out for?
Any developer out there or any consultant who happen to sit in certain lines of business and want to pick up the low-code challenge, keep an eye up! SAP is running these App-in-a Day workshops around the globe and if you get the opportunity, you can work or learn from home, or if you got the chance to get in a room with people, it’s a great way to learn and share that experience.
How interesting to know you can provide a solution to your personal or organizational needs by creating beautiful apps with AppGyver. Whether you’re a pro-developer or a beginner, SAP AppGyver is a good fit for you to build applications quickly and faster. To learn more about SAP AppGyver,
👉 follow the SAP AppGyver Topic Page
👉 read and follow other SAP AppGyver blogposts
👉 ask all questions about SAP AppGyver
We are looking forward to your next SAP AppGyver challenge.