KarParc — OST KIT Alpha Phase III- Final
This is our final blog post on the Proof of Concept app created for KarParc.
We are a small team consisting of:
Moiz Iqbal — Project Manager
Wali Ganatra — Tester
Hamza Younus — Developer
In this blog we will attempt to answer some of the questions from OST Alpha III Challenge:
What problem does your project solve for and what was the user need for creating your token economy?
In our busy city of Karachi, the car parking is hard to locate and when found there are numerous problems including theft, over booking and incorrect charges. We wanted to implement Blockchain solution which will help resolve many of these issues.
What was your key goal behind doing the challenge?
We aimed to create a token that can be transferred between our KarParc company, Carpark owner and Carpark consumer.
How did you plan the design for your wallet features?
We created few mockups first and between the team discussed what data would be essential for the user. We also looked at existing wallets for inspiration. In the end we want to keep it simple and were limited to what can be retrieved by the API.
- What APIs did you use: Ledger, Balance, Actions, Token Details, etc.?
— For the wallet view we used Ledger, Balance and Token detail API. Token detail was used to convert for $ value.
- What information did you show to the end user and why?
— We felt that wallet view should have the current Balance clearly visible and its $ value. In future we want to be able to show PKR (Pakistan Rupee) value or other currency based on user choice. It should also show previous transactions, this should include date time, status of the transaction and amount involved. When user want further details, it should show a link to the blockchain receipt (the OST View).
- How did you use design (UX/UI) for how to display this information?
— Since the Ledger API allows us to query transactions with paging, we took full benefit of this feature due to the small real state on mobile app. If the user decides to drag up (ie wants to view more records) then only we send the next query. We also felt that link to OST View is required but should be displayed only if user is interested on the record.
What did you like about using these APIs?
Using OST Kit we were able to prove our concept was not only feasible but we have been able analyse that it can be profitable business. Ost Kit API was quite easy for our developer to integrate into our Android app. The community is also very helpful and we were able to resolve any technical issues through the community quickly. The API documentation is awesome and very easy to follow. Furthermore the API itself follows the standards therefore we can anticipate the communication easily.
What did you learn about designing these wallet features?
Some of the things that we learnt was that for our customers PKR equivalent value is critical for the success of our idea if we want to implement it in Karachi. We also learnt that some users may want to know the gas costs without having to goto OST View and that may be something that can be shown on the app.
We would like to thank OST team for their dedication to making OST Kit business friendly specially for startups like ours. We hope to see OST Kit going live soon.