Tyrell Downer

An internal Vue-based application using Microsoft Power Apps on the back end, hosted in Microsoft Dynamics CRM. I was the sole developer on this project, tasked with building a place to store all our internal processes as a company.

The end user had to be able to find company processes (such as 'how do I check the status of a client's application') in an organized manner. Using Vue and Dynamics Power Apps, I built a highly scalable system that sorted processes by hierarchical categories to accomplish this.

Admins could add categories via Power Apps. They could then add processes to those categories in a GUI using a HTML text input for the process title, an autocomplete dropdown to select a category for the process, and a Ckeditor input for the 'body' of the process.

End users could easily navigate categories in the front end and find the process they were looking for. I also built a search bar into the front end so end users could search a process or category.

If end users could not find a process, they could seamlessly submit a ticket for that process to be added to the admins.

This allowed the project to be continuously improved by its users while requiring minimal developer resources for maintenance.

This was a project that was originally built as a PWA using Django. It became clear to me when I got to the company this would not be sustainable long term. After communicating with the IT director, I received clearance to rewrite the mobile app in a more maintainable and higher-performing way.

I began my research, and it shortly became clear that React Native was the best framework for us to write our mobile app in.

I got the okay for React Native and began development.

One of the main considerations I had to make was how maintainable this would be in the future by another developer, specifically another developer with the little mobile app experience.

I hedged against this throughout the project in two ways:

1. First, deciding on React Native in the first place, as it's very similar to modern front-end web-based languages.

2. Writing clear, concise code and great documentation.

That way, even though I wrote a lot of custom code, such as the custom navigation system the app has, another developer could still pick it up and be productive quickly.

This project, with some marketing help, brought our mobile app from 300 to 15,000 users per month.

A website for a software development agency. The primary purpose was to develop my full-stack web development skills. The project is fully functional.

A key feature is the schedule meeting feature. It hits an AWS API Gateway endpoint and triggers a lambda function that uses the Zoom API to create a meeting. Then the lambda function uses AWS SES to notify both the end user and the site owner with a link to access it via email.

A Django-based web portal. I was a full-stack developer on this project and built a lot of the front end and back end along with a dedicated back-end developer. This product allows end users to manage their prescriptions, dependents, and many other features.

I was also responsible for building the public-facing website into the web portal. Using Django CMS along with HTML, CSS, and JavaScript, I was able to create a rich experience for end users. Implementing Django CMS also allowed our marketing team to make changes to the website's content without contacting a developer. Overall, this saved a lot of developer time.

A project I built to make scaffolding full-stack applications much easier, removing a large amount of boilerplate while still being fully expandable by a developer.

This framework provided a JWT-based user auth system already integrated RESTfully with a Vue front end.

The main feature was a GUI that took advantage of Django's ORM and allowed you to create entities. An entity consisted of a model, serializer, admin config, views, and URL endpoints.

The GUI mainly contained a form with entity names, fields, and parent app inputs. You could select unlimited fields of various types (text, int, boolean, image, file, foreign key, and rich text field): for example, a text field named 'title.'

Upon submitting, an entity would be programmatically written in the Django app you selected. The fields will be attached to your model for you. Then the database is migrated, so the model becomes available immediately. It also wrote query functions to your front end corresponding with the created endpoints.

The code was written for your project and could be expanded easily. The GUI will organize your code based on hierarchical Django apps containing entities.

To initiate the project, you simply ran an npx command.