Our team consists of five passionated guys with different backgrounds.
Alexander Murgoci - Business practioneer with a passion for innovative technologies and Python
(www.linkedin.com/in/alexandermurgoci)
According to competition rules, interims mobile contact until further notice: +49 172 - 626 62 79
Benedikt Jäger - Stark-ish mechatronic-guy with a soft-spot for Java (www.linkedin.com/in/benedikt-jaeger)
Christian Meggle - Originator and Backend/Middleware guru with Java
(www.linkedin.com/in/christian-meggle)
Fei Liu - Multi-Ninja on the Frontend- and IOTA-side
(https://www.linkedin.com/in/fei-liu-380aa7168/)
Stefan Kreißl - Bridgebuilder between business & development, with mobility business and Frontend, Backend, IOTA & Ethereum development experience (https://de.linkedin.com/in/stefankreissl)
We want to enable companies to enter the mobility market. Our idea is to develop a clear & crisp REST API to ease implementation on company and customer UI. Such way we hope more customer and mobility provider hook up in a distributed mobility ledger.
- IOTA
The Java part of this project is heavily driven by maven. There is a lot of prepossessing going on. Just to point out some steps:
- we define our API from a business point of view, so practically we write our business login into an yaml file (api.yaml) and
- let swagger during the maven preprocessor (compile) transform the yaml into Java (by using jaxrs as a framework) code.
- How these Java-files are actually created depends on swagger templates we overwrite in the generator -> resources/RestGenerator, api.mustache is the place where some magic happens.
- to make it even more nasty, we generate by hand a json-file out of your self written api.yaml. We then saved it into the static folder and make it available for our frontend documentation.
- After all, our server get started in its specific sub-project, there you can also find some more REST* implementations
We use the following technologies in pursuit of mobility happines:
- Apache
- Java
- Node JS
- React
- IOTA JS SDK
- SWAGGER (aka OpenAPI)
- Spring Boot
- IntelliJ
- NEOVIM
IOTA part provides 3 APIs
-
publishing provider mobility offer to IOTA tangle net
"node iota/apiPublish.js --payload='{"name": "fei", "test":"again1", "provider": "bmw"}'" -
get payable provider address for end user to conduct transaction
node iota/apiGetAccount.js --provider=bmw // possible providers are bmw, vw and db -
authorize and confirm payment
- App demo -> how a user can interact with our service, e.g. finding a offer on IOTA from different mobile providers and conclude a contract via IOTA.
- Get payable address of mobile provider
- Publish mobility offer on IOTA
- Backend Java API for mobile provider to publish offers
