Our Project

ParKd

Introduction

ParKd is a motorcycle parking app aiming to provide both free and paid parking solutions to all two wheeled commuters within Sydney. The app will be community rated, meaning that residents can provide a two-wheeler parking location on the app, which they feel is secure and safe. The concept of this app is to mitigate the time wasted on searching and locating a safe and secure parking spot. Using geo location, the app will provide suggestions for the closest and safest community rated parking near a chosen location. ParKd goes beyond just finding spots, it allows riders to ‘reserve’ a parking they wish to occupy. Using ParKd will also save money on fuel, as it can show the user exactly where the vacant spots are, reducing the usual time and fuel wasted on finding a parking spot. ParKd will also allows users to pay through the phone, allowing instant payments and reservations. PayPal, direct deposit, and other payment methods are all available through the app.

ParKd offers the user two options when using the app: the choice of either being a rider or a host. Riders are simply those in the community using the app to seek a parking spot for their two-wheeled vehicle. Hosts, on the other hand, are those people who are using the app to either ‘rent out’ their garage, driveway, or any free parking space. These ‘rented out’ spaces will be called bays, or hubs.

Motivation

Currently in Australia, there is a major problem regarding motorbike parking, Sydney itself amounting to almost 1200 thefts in the last 12 months, as shown by NMVTRC. It is especially concerning that more than half of the victims of motorbike theft never see their bikes again. As a result of this, we wanted to develop an application through which motorcyclists could easily find, rent, and occupy parking spaces. We plan to create a safer parking environment for those who ride motorcycles. It is a rapid growing problem in Australia, especially in Sydney, which has the highest rate of motorbike in thefts in all of Australia, and many innocent people are suffering from this selfish act and needs to be solved immediately. With this app, we aspire to minimize, or even eradicate, these horrific theft rates, putting an end to one of Australia’s biggest problems.

Overview

ParKd is a motorcycle parking app aiming to provide both free and paid parking solutions to all two wheeled commuters within Sydney. The app will be community rated, meaning that residents can provide a two-wheeler parking location on the app, which they feel is secure and safe. The concept of this app is to mitigate the time wasted on searching and locating a safe and secure parking spot. Using geo location, the app will provide suggestions for the closest and safest community rated parking near a chosen location. ParKd goes beyond just finding spots, it allows riders to ‘reserve’ a parking they wish to occupy. Using ParKd will also save money on fuel, as it can show the user exactly where the vacant spots are, reducing the usual time and fuel wasted on finding a parking spot. ParKd will also allows users to pay through the phone, allowing instant payments and reservations. PayPal, direct deposit, and other payment methods are all available through the app.

ParKd offers the user two options when using the app: the choice of either being a rider or a host. Riders are simply those in the community using the app to seek a parking spot for their two-wheeled vehicle. Hosts, on the other hand, are those people who are using the app to either ‘rent out’ their garage, driveway, or any free parking space. These ‘rented out’ spaces will be called bays or hubs.

Currently in Australia, there is a major problem regarding motorbike parking, Sydney itself amounting to almost 1200 thefts in the last 12 months, as shown by NMVTRC. It is especially concerning that more than half of the victims of motorbike theft never see their bikes again. As a result of this, we wanted to develop an application through which motorcyclists could easily find, rent, and occupy parking spaces. We plan to create a safer parking environment for those who ride motorcycles. It is a rapid growing problem in Australia, especially in Sydney, which has the highest rate of motorbike in thefts in all of Australia, and many innocent people are suffering from this selfish act and needs to be solved immediately. With this app, we aspire to minimise, or even eradicate, these horrific theft rates, putting an end to one of Australia’s biggest problems.

Landscape

Currently, there aren’t many reliable motorbike parking apps out in the market. There are only a handful of applications in this category, and a few websites that show available parking spots for motorcycles. According to RACQ, there are eight reliable and popular apps that show motorbike parking availability, and they are:

  • Cheap Parking
  • Parkopedia: Known for finding cheap street parking
  • Parkhound: Known for finding best daily parking
  • ParkMe Parking (INRIX): Known for best parking app in Brisbane
  • Kerb
  • PayByPhone
  • PayStay: Known for finding best metered street parking
  • CellOPark: Known for finding best metered street parking


Although these apps are readily available and useful, they only house one or two features within, for example, the app is known for metered parking, or cheap parking. This is where we want to separate our app from the rest, we want to house all those features, ranging from costly and free parking, to renting out vacant spots for parking. This app will be unique, as there is yet to be an all-rounder motorbike parking app in Australia.

Aim

The aim for this project, as mentioned in the Topic section. Is to provide motorcyclists with safe and timely parking for their vehicles throughout the day. One of the biggest problems with riding a motorbike in Sydney is that so much bike theft and damage happens on a day-to-day basis. We aim to create a platform for riders to rent out safe spaces such when they aren’t using it for themselves.

We want to allow riders to rent parking spaces off others and be assured that their vehicle will remain safe for the few hours it spends at a location. Our solution to this is to allow other riders to rent out their spaces while they are gone for the day. This way, safe parking throughout Sydney will not be going to waste and will almost always be in use.

For this kind of project to work we must assume that our users want to look after their community and won’t be using this application maliciously. We can further ensure bike safety by having users sign an agreement that says that all private parking spaces must also provide video surveillance. Further ensuring the safety of our users.

ParKd should also provide an easy way for its users to find this parking. Our main idea for this is to provide our users with the ability to browse an interactive map in a certain area of Sydney and have available parking spaces show up on the map with a price. Similar to how hotel booking applications work.

Plans and Progress

The Story of ParKd

A two wheeled parking solutions app is that of a motorcycle commuters experience of relocating from Melbourne to Sydney.

"It was then admitting the air of shame arriving late, to my first day at a new job that I realized Sydney although beautiful and full of two-wheel commuters was not user friendly by any stretch of a Melburnian imagination. Here I was shocked to find that pulling up and parking on the pavement near my destination was no longer an option. Although there are motorcycle parking bays within the city and suburbs and bike commuters can in fact park in a car space without being required to pay a meter, finding, locating, and securing one instantaneously cost me a first impression and gave me the concept behind what is ParKd." ~Emmet

What our project will do

ParKd is the positive outcome of an uncomfortable motorcycle parking realization crafted by the four minds that make up the group TESS. Project ParKd will address the city of Sydney’s chronic shortage of motorcycle parking bays by creating an app which will act as a platform for renting and leasing motorcycle parking to overcome the insufficient number of overcrowded designated bays within and around the CBD.

How it began

Our project began with the creation of four phases:

Image of the Four Phases



Phase 1 - Stage 1


Stage 1 - Phase 1


To begin with we started by setting a name for our project. To generate a name for our project we used MS whiteboard and bounce ideas around. Our goal for the name was to have one word which would express our intent and scope. Tess polled agreed that ParKd could clearly express our application/platform.

Name Ideas



To drive the vision of the application into reality, we defined the scope working firstly on the key objectives and Functions. We narrowed down our key objective to produce a user-friendly application to automate and decrease the time spent manually searching for optimal parking near a chosen location.

Functions and objectives

How we approached ParKd

To reach our goal of creating a prototype for ParKd we split ParKd into two parts, frontend and backend.

Approach

Backend
We initially planned to build the backend program with python, that should be able to let the user login, sign up, email verification, reset password, save payment, save vehicle data, save user password, save payment info, encrypt payment and password info, show map, show free parking, show paid parking, take a picture of the QR code, and resolve the QR code to an alphanumeric digit etc. We can also use python to create android, iOS, or windows application.

We would need knowledge on Swift, Object C and Java to make a better version of this application available for every platform, such as: Android, iOS, Volla OS or Linux etc.

To get the programs and our servers work with each other, we also need to implement a network. For this, we would need expertise in building servers, router/switch/firewall configuration, packet analysis (e.g., Wireshark), linux, windows server, SQL, troubleshooting etc. Having a deep understanding OSI layer is particularly important. So, someone with a minimum CCNA or CCNP (preferred) would be perfect to handle the networking section.


  • Developer
A developer is responsible for the app’s backend architecture. He or she writes the app’s code and integrates it with any external data sources. While all team members are critical, a developer often contributes the most amount of work to an app, especially in the later phases. 

  • Network Engineer
A network engineer is responsible for implementing the back-end routings. After the developer develops all applications, SQL, scripts, webpages etc. the network engineer builds servers, routers, switches, firewalls, SAN, NAS etc. to get the backend applications up and running. Network engineers should be able to create basic programs with a high-level language, such as: Python, Java etc. 



Frontend
There were two approaches to developing ParKd as an application. In the first approach, we would have to develop two separate applications ‘native applications’ for a specific platform for example, IOS and Android. In the second approach we would create/develop a single application called ‘hybrid’ or ‘cross-platform’ app which would be a web-based application.


  • Frontend Developer / Designer
The front-end developer and designer would be primarily responsible for crafting the app’s user interface. For this project we chose to use Figma to design our Prototype. Design, user flow and experience were key, the goal was to create an intuitive experience which would require little thought to navigate and use this application.

The roles we created and established to get ParKd underway

Roles

Design

As every product decision would be defined by our brand, we started by addressing aesthetics. For the branding of ParKd a two-wheel parking solutions app we wanted to create a logo that would set the tone and vision we had. Although this app was inspired by motorbike commuters, we agreed that a scooter could captivate the essence of our two wheeled parking system more accurately and set our visual direction for ParKd. However, here are some of the logo designs that did not make the cut.

Scrapped Logos

Our brand needed to set a tone with a user-friendly voice to reach our core product concept to mitigate unnecessary stress related to insufficient parking by providing an alternative in the form of a community centered parking platform. To achieve this, we played with colours, fonts and illustrations. We chose the colour yellow for its associated qualities, fun, security, trust, and reliability and to keep the youthful vibe we went with the east sea dokdo font.




Product Goals

To create a user-friendly experience centred around effortless decision-making.

Based on our target audience being two wheeled commuters our interface design and user flow had to account for users using this app attached to a bike or scooter and potentially wearing gloves to address this we went for a minimal design with big buttons.

Product Goals



We chose to use Figma to produce a prototype of what we feel our application would ideally look like when the app is brought to life. The better technologies that are available to us and should be utilized would be Objective C/Swift/Java. We currently are not in the developing stage of the frontend and have been playing around in Figma trying to figure out what the best solution would be. Keeping in mind the usability of the app. We do not want our users to be stressing out about what sections they need to click on to find what they are looking for.

We would like to keep in mind the principles mentioned in Steve Krugs book “Don’t make me think” everything developed in the frontend of our app needs to be user-friendly and self-explanatory. We do not want to waste our users’ time by making them click 3 different icons to even begin searching for parking.

These ideas are what lead us to creating such a simple hub screen. A prototype of our app can be viewed below, skip to frame 6 to see the hub screen.



Outcomes of our Project




What we've got so far:





Roles

Due to each of our members having to commit to different schedules and having changes to availability from week to week. Our group found it so much more effective to just leave our roles as dynamic and have the tasks that need to be done get completed on an ‘as needed’ and ‘when you can’ basis.

The biggest hurdle that we had to get over from beginning to end was the availability of each group member. Let us provide an example of what could happen with defined roles.

There are four group members, for the sake of example let's call them Person A, Person B, and so forth.

Person A has to complete the task of writing multiple sections of the document so that Person C can review, Person D can implement it into the prototype, and Person B can add it to the website. However, Person A doesn’t have availability or access to a computer for the next 3 days.

It’s easy to see here how one person's circumstances can delay an entire process by 3 whole days, which, in a project which requires as much effort as this one. This could be very detrimental to the entire group.

So instead, we opted to have the tasks listed in planner, and have our group members take the tasks that they would have completed in that time period. This way it was easier to keep track of doing what, and, since deadlines were already set for each section, we were able to get things done with each member of the group contributing as much as they can.

Using this approach to getting the work done, each member ended up writing their own sections of the document, Taylor ended up doing the website, Saajid and Emmet worked on the prototype and Sam worked on getting backend functions up and running. But it’s also worth mentioning that other members of the group helped out with other parts, so while Taylor may have been working on the website, the other 3 members had inputs for things that could change and were able to update their own personal profile sections in the HTML. Or while Emmet and Saajid were working on the prototyping in Figma, Taylor and Sam also had their own input and even helped make their own screens to be used as examples of what they thought would be a good approach to achieve what we were trying to achieve.

Scope and Limits

ParKd was initiated to address motorcycle parking problems within the Sydney Area by creating a two wheeled parking solutions app. Our key objective is to automate and decrease the time spent manually searching for optimal parking near a chosen location. The function of the application is to provide a user-friendly interface with three steps.

Step1# Searching – the rider types in their desired location, ParKd will suggest the closest free and hosted parking to the chosen Location

Step2# Route planning, this is an important feature to address arrival and departure times holding true to our key objective.

Step3# ParKd, the arrival the rider simply parks either in the free or paid hosted bay at said location.

There will be a corresponding web application whereby anyone using the app can log in to view

Pie Chart for Statement of work


Flow Chart

Major Constraints

Scope creep, personal differences leading towards absence of communication thus resulting in ineffective time management and unobtainable milestones.

Tools and Technologies

Web Server/IIS/Apache Server:

Windows have service called IIS or Internet Information Services that can be added as a feature in Windows Server/10/7 etc. which can host websites in the intranet or internet. For Linux, we can use Apache server. It is open source and free to use. It can run on Windows too. XAMPP is also a good tool for hosting website. It has a graphical interface for SQL, so it is a good tool for RDBMS. 

DNS (Private/Public)

DNS is a translator in simple words, it translates a domain name into an IP address. It can be private, or it can be public. Mostly private DNS are used for intranets. Public DNS is used for internet. Such as: 8.8.8.8 (Google), No-IP, DynDNS etc. For name resolution: we can use a static Public IP address or No-IP/DynDNS. DynDNS or No-IP simply keeps a record of updated public IP address, after the lease ends. So, when the domain name is resolves, it gets the updated IP and routed to the host. 

RDBMS

Also known as Relational Database Management System. Such as: SQL, MySQL, DB2 etc. MS Access is also RDBMS. However, it cannot manage large quantities of cells like SQL can. So, for a software like ParKd needs to have SQL database at least. Tools for RDBMS are Azure Data Studio (Hybrid), MS SQL server, XAMPP etc. 
[NB. SQL can hold 524 Petabytes of data at the maximum] 

FTP Server

We can get the FTP service from the windows feature. It is under the Internet Information Services. In simple words, FTP is used for accessing a folder remotely. Permission can vary for user to user. Such as: Read-only, Change and Full control. 

Python

Python is versatile and flexible. It is a high-level language. We can write modules and import modules on-demand.

  • PyQRCode: Generates QR code
  • Cryptography: Fernet, SHA256, SHA512, etc.
  • OpenCV: Can use a camera module to identify objects. The module we will use, will be able to resolve QR code to alphanumeric values.
  • GeoPy: Can get the geolocation, nearest location and farthest location
  • SMTPlib: Can send emails
  • Kivy: A Python framework created for the purpose of creating apps in Python.

HTML/CSS

These are used for creating a document designed to be displayed on the browser. CSS is used for formatting the layout of a webpage. 

CLI/.bat/.sh/.ps1:

Also known as Command Line Prompt. It is another version of GUI or Graphical User Interface. CLI consumes less resources, CLI can be often faster than GUI. CLI is extremely useful when it comes to automation. We can also use CLI to deploy a script in a group of computers. In simple words, we can write bunch of commands in a batch file, shell script or PowerShell script and run them on a machine.

HTTP, HTTPS, SSL, TLS

HTTP is a protocol that is user for transmitting the webpages and other files. HTTPS functions similarly but it encrypts all communications between the server and the end user. For example, if we log into “http://www.login.com” using user = “tess” and password = “secret1234”, the communication will be in plain text. Anyone can see the credentials, using a packet analyzer such as: Wireshark. But if it is “https://www.login.com,” then the credentials will be encrypted before the credentials are transferred. So, even if there is MITM attack, the hacker can only see the encrypted version of the password, which is extremely difficult to decrypt as credentials will be using one way hash function. 

To enable HTTPS, we need to install an SSL/TLS certificate.

 

Certificate imgage.

Encryption/Decryption/Hashing Algorithms

Testing

We will know if we have succeeded with this project when all functions are operational and working as expected. So far, we have run tests with the prototype in Figma, asking friends to view the prototype and give their feedback and opinion. We're really happy with how the prototype is looking now and the usability testing went really well. There were a few issues early on but they were quickly fleshed out. In terms of testing the backend, this has been done as we're going along. While Sam has been creating functions in python he has also been testing that they're all working as expecting, and testing connectivity in some cases.

When the frontend has had significant development, the plan is to go back to random users and get them to test again. These tests will again, test the usability and intuitiveness of our application. When a user tests our program we can provide them with a 3 or 4 question survey so that they can provide feeback. such as:

  • On a scale of 1-5, how would you rate the usablity of this application?
  • on a scale of 1-5 how likely are you to use this application for yourself?
  • Any feedback you'd like to provide the developers?


Another method that we may use for user testing is to simply let users play around with an early version of our app and just observe. See what they struggle with, see what they like. Ask the user to think out loud so we can gain a better understanding of how someone picking up this application for the first time might react to it.

We can also use this frontend testing to ensure that the frontend is communcating properly with the backend. If we ask users to create test accounts, we'd be able to heck if that users details are being filled out on all the relevant tables.

The important thing is that we flesh out as many issues as possible, with the use of user testing we are able to do this and in terms of the backend we are able to ensure that the program doesn't bring up any errors and that information is being stored where its supposed to.

Testing 1


Testing 2


Testing 3


Timeframe

Calendar timeline image
Taylor Emmet Saajid Sam
Week 1 Planning Project Idea Planning Project Idea Planning Project Idea Planning Project Idea
Week 2 Research and Development Research and Development Learning Github, researching backend work Research and Development
Week 3 Limited availability - Working on report Learning Figma Learning Figma Backend architecture design
Week 4 Report work Creating wireframe and plotting userflow Helped with the user flow/researching frontend techniques Figma SQL Tables
Week 5 Made some screens/frames in figma and began work on website Started building prototype in figma Marketing research Started building python modules
Week 6 Website development Finish up prototype work in Figma Frontend Design (Figma) Work on Python modules
Week 7 Begin planning frontend development, research frameworks Test the user flow in the prototype Work on the frontend/testing prototype Work on backend modules
Week 8 Install and explore necessary tools used to create application Implement any necessary changes to the prototype Fixing changes and problems on the prototype if need be. Test and update modules
Week 9 Work with Sam and work on the frontend of this application Get external users to test the prototype Learning new helpful techniques to aid in the completion of the prototype/ get external users to test Create a proposal for the network implementation await approval
Week 10 Continue frontend work, Implement login function Implement necessary changes to the prototype / learning the technologies required Extra marketing research, to begin plan for product launch Build SQL server, IIS
Week 11 Continue frontend work, Implement map learning about native based web applications Research Search engine optimisation DNS, Dyn-DNS/No - IP set up
Week 12 Continue frontend work, Start implementing menu learning how to use code libraries for JavaScript UI Frameworks Create social media pages integrate the servers with the contents
Week 13 Continue working on menu buttons and functions learn intergrations in Oracle intergration refine advertisement and product description install N-central agent, probs Auvik collectors etc monitoring.
Week 14 continue working on functions as required Add Request and Response Enrichments Find select test users for beta testing Setup alerts, Autotask platform, Email2AT(RegEx/mXparser and policies), 3-2-1 backups
Week 15 Test current progress and continue work on app Create Routing Paths for Two Different Invoke Endpoints in Integrations Create usability survey for beta testers to provide feedback Test the network(integrity/Pen test)
Week 16 get the beta version ready Map Faults in Basic Routing Integrations Release the beta version for limited people Release the beta version for limited people

Risks

There are quite a few risks that should be considered heading into a project like this. To name a few:

  • Difficulty learning relevant libraries to make this app come to life
  • Time constraints
  • User Error, People not checking out of parking spots, people not keeping their own parking spots updated, etc.

The first thing we need to consider is that this app could be a lot more difficult to create than we anticipate. It is all well and good that we’re all comfortable with writing code to create programs, but as for any experience each of us have creating an application from start to finish, none of us have the full stack of skills required to make this come to life. Which will inevitably lead to a time crunch toward the expected end date of this project. With the timelines that we are given, honestly, it is unrealistic to have this project complete from start to finish in the allocated time.

It is entirely possible that each member of our group spends so much time and energy learning how to create these types of things that by time we feel ready to start working on it, it could be weeks or months down the line. At the very least we are comfortable with creating a prototype with tools available to RMIT students such as Figma, but beyond that our skills are limited.

Figuring out a bunch of different Python libraries to make an app can be time consuming and, you do not know exactly how each function works until you have applied it to something and seen it in action

Another risk that comes along with the creation of an application such as this one is that there is always going to be room for user error. We need to consider every possibility. It might even be worth getting some users to test out our high-fidelity prototype and make sure that the design of the application is intuitive.

It is probable that users are going to forget to check out of parking spots or say they will be renting a parking spot from someone else for 1 hour and exceed that time limit. A workaround for problems such as these would be to send a notification to the person's phone asking if they will have left by the expected time or if they need to add 15 minutes to their booking.




Skills and Jobs

Supposing a group of venture capitalist hears about TESS and our parking application ParKd. Below, we've provided four of the positions we would be advertising immediately in order to bring out product to market with an addional 9 weeks of work (or more if necessary).

Backend Development Engineer

The role

Is often described as a the “server” side of development. Essentially, we are looking for a back-end developer to makes sure that everything on the front-end connects flawlessly with “back-end” databases, and other third-party services.

Responsibilities

We are looking for a backend developer to mitigate any code failures, bugs, or bad requests that prevent a customer being able to use our app by designing, developing, testing, deploying, maintaining, and improving software currently written in Python.

Working in teams and individually to deliver functional components and services related to ParKd a motorcycle parking app.

Managing individual task priorities, deadlines, and deliverables, the ability to use a variety of standard tools to maintain great working practices.

Our Expectation

Passionate about being at the forefront of change, you’re ready to help deliver meaningful value to our clients/users. You’re collaborative and enjoy working in an innovative environment. You’re a problem solver by nature and want to help take a start up to the next level. Most importantly, you act with integrity and show care for the people you work with.

Qualifications - Essential

  • A bachelor’s degree in Computer Science, or similar technical field of study, or equivalent practical experience.
  • Ability to demonstrate competence with one or more general purpose programming languages, particularly Python.
  • Previous experience in a backend development using Fernet cryptography, Opencv-python PyQr code, SMTPlib, Geopy, SSL certificate,

Desirable

  • Experience in creating software using Python
  • Knowledge in frameworks such as Laravel
  • Familiar with database design using SQL
  • Experience in successful delivery of project documentation
  • Experience with Git and collaborating with other developers
  • Experience in start-up industry is highly regarded

Level 3 Network Engineer

The role

We are a private company. Our company was established in 2021 by 4 Friends. Despite, being very new in the industry, we have received multiple sponsors for our upcoming application “ParKd”, which is like Airbnb for bikes in simple words. So, we are recruiting System engineers now. If you enjoy building network infrastructures, testing, researching, improving and troubleshooting the network, you are the person we are looking for.

Responsibilities

  • Submit the project before the deadline
  • Coordinate with the backend and frontend engineer.
  • Prepare a plan and share with everyone on Monday morning meetings.
  • Request changes during the morning meetings, wait for approval from a director
  • Build a network of multiple SQL, IIS, NAS, Client Applications, ftp servers, etc.
  • Test, research and develop the network

Skills and Experience

Ideal candidate will have:

  • Experience working as a L3 Network Engineer or a System Engineer for at least 3-4 years.
  • Extensive knowledge on servers and routers


  • Good knowledge of protocols such as:

  • WAN, LAN, VLAN
  • IPv4, IPv6
  • ACL
  • OS
  • Windows Server (2016)
  • IIS or Apache Server
  • DNS
  • DHCP (Reserve IP Pool)
  • Exchange Server or Office 365
  • FTP Server
  • Basic knowledge in Cyber Security for testing
  • Kali, Parrot OS or Commando VM
  • NMAP, Zenmap or Open VAS
  • SQL Server
  • Azure, GCP, AWS
  • Good with CLI (CMD, Terminal)
  • Python for automating complex network configurations
  • SSL/TLS Certificates
  • Encryption/Decryption Methods
  • Layer 3 Switches
  • Cisco IOS (Cisco Certificate Preferred)
  • NAS backup, Cloud Backup, SAN
  • Configuration and Monitoring Tools
  • N-Central and Auvik Probe, Agent installation and all required configurations for monitoring our implemented network
  • Putty
  • Cable patching
  • Router, Server migration
    •

Marketing Manager

The Role

The Marketing Manager is responsible for the development, management, and delivery of the marketing plan, within the budget restrictions, to achieve the company’s overall objectives, including:

  • Increasing market awareness of ParKd capabilities.
  • Developing and delivering an ongoing digital strategy.
  • Developing, maintaining, and ensuring compliance with ParKd branding.
  • Providing marketing input into product positioning and development activities.
  • Maintaining an overview and providing guidance with marketing and market development activities to teams including future and current product activity.
  • Managing designated exhibitions, conferences, and customer events.
  • Management of contractors and associated budgets to achieve the marketing plan

Key Challenges

  • Management of resources to achieve appropriate outcomes
  • Gathering, and ensuing use of, internal and external market intelligence
  • Working within tight budget constraints

Key Responsibilities

  • Safety
  • Marketing and Sales Materials
  • Product development and management
  • Market Intelligence
  • Website
  • Social Media
  • Social Media

Qualifications - Essential

  • Tertiary qualifications in Marketing or Communications or a related field or significant experience in several different business sectors.
  • Advanced verbal and written communication skills.
  • Strong creativity skills.
  • Ability to identify and communicate brand attributes and values

Desirable

  • Skills in a PC environment in a combination of: Adobe Creative Suite, Dreamweaver, Flash, Photoshop, Illustrator, HTML raw code, and Office Corel Draw.
  • Ability to manage projects
  • Market research projects
  • Advanced problem-solving ability
  • Excellent attention to detail
  • Sound understanding of brand, business, and marketing objectives

UI / UX Developer

ParkD is looking for a UI / UX developer to join the team. ParkD is an application created for mobile devices that allows users to book or advertise private parking spaces for motorcycles in Sydney and surrounding suburbs. It also allows its users to mark points on a map which they deem safe for other motorcyclists to park.

The Role

As a UI/UX Developer you will be working alongside our backend engineer to develop the user interface of the app to really make it come to life. You will also be responsible for creating wireframes and prototypes which can be used by our Marketing/Research Lead

Responsibilities

  • Lead and Support activities across UI and UX design
  • Look at concept designs and help bring them to life
  • Developing new features as well as improving existing features
  • Writing and testing frontend code
  • Creating App prototypes using tools like figma to show our marketing lead
  • Making suggestions for App improvements in line with standard design principles
  • User analysis - We want our app to be as intuitive as possible
  • Other Duties as required

Qualifications - Essential

  • Proven Experience in UI/UX Development (2+ years)
  • Tertiary Education in IT or other relevant fields
  • Ability to write clean and re-usable code
  • A willingness to learn

Desirable

  • Experience in the use of tools used for prototyping such as Figma
  • Native iOS and Android development (Python, C++, Swift, Java)
  • Experience with web app development (Python, JS)
  • Experience with Google APIs
  • Excellent written and verbal communication skills
  • A Passion for Technology