A webapp app for Hatch
Hatch is a budding property company that pairs small, independent retail firms with high street landlords. Hatch provides its clients with the following toolkit.
- Growth intelligence
- Site Appraisal
- Create listing
- Leasing guide
- Community hub
- Directory
Access demographic data and analysis to help you understand where’s best for your business and how many customers you will tap in to.
A one stop calculator to help you appraise the affordability of each potential site and ensure all costs are factored into any decision.
Advertise your business and property requirements to our database of landlords. Then sit back, relax and let them come to you.
It’s easy to get bogged down with property and legal jargon. And hard to project manage an opening. Let us guide you along the way.
Share wisdom, contacts, and tips with other small business owners. Keep up to speed on changes to things like business rates and planning regulations.
Solicitors, architects, design and fit out contractors, planning consultants, recruitment agencies, you name it, we have it. Read reviews and recommendations.
This app can be broken into large-ish sections that are similar to those shown in the toolkit above.
- Website structure
- Users
- Growth intelligence
- Site appraisal
- Create listing/Community hub
- Leasing guide/Directory
- Hatch is now drawing sketches for their desired layout
- These will provide a template for how to structure the website
- This toolkit should only be avaible to registered users of the app
- Therefore there must be functionality for signing-up/signing-in/signing-out
- Fields for signing-up include: Company name, contact email, contact phone number, password
- The app will need access to a database to store user data
- Password encryption
- Email address checking
- The user supplies a location
- The app takes that location and accesses an API
- The app returns API data and presents it in an easily-readable format
- This is a relatively straightforward calculator
- Potentially this data will need to be stored
I have grouped these two together as they have similarities. Both require creating a 'post' which must be stored in a CRUD database and shown on-screen.
These are grouped because (at first) they do not involve user input. They are simply text documents to display on the website.
Down the line, as reviews and recommendations are added to the directory, the directory will more closely resemble the 'Create Listing/Community Hub' structure. However this is low priority for now.
- Initialise a rails project
- Receive sketches from Hatch and create a simple website, displaying given template structure
- Discuss with Hatch whether the preliminary order of priority is appropriate (as above)
- Split these larger sections into much smaller, bitesize tickets and check with Hatch for order of priority.
- Ruby on Rails
- Rspec, Capybara, Rubocop
- PostgresQL (for development)
- AWS (for production)
- JavaScript (for frontend async updates to website e.g. API requests)
- CI/CD: Either Circle CI or Travis.
- Heroku (for development)