Building a URL shortner that has a click statistic

"Not All Shortcuts are Bad" Case Study - a 'url shortener'. Have you ever tried to copy a link, and just after you pasted it realized the link contained some "unnecessarily long" characters that made it "unattractive"? What did you do about it? Did you go leave the "unnecessarily long" link that way? Did you find a way out? If you are team "I cannot come and go and kill myself" then this piece is definitely for you.:sweat_smile: After coordinating the efforts of other teams to develop a To-do app, the new week came with a new task - Managing teams to create a URL shortener. Of course, most of us on the Product Management team, before now had never been involved in the process of creating one. Some of us were probably on team "I cannot come and go and kill myself.":sweat_smile: However, that changed this week; we had to get involved in the process.:grimacing: What does a URL shortener do? What the 'URL shortener' does is convert long strings of alphabetical links to shorter versions of the link that can still be accessed. A 'URL shortner' allows you to reduce long links from Instagram, Facebook, YouTube, Twitter, LinkedIn, and top sites on the Internet; just paste the long URL and click the Shorten URL button and it is done. Easy peasy right?:new_moon_with_face: Our team was tasked with creating a URL shortener for a web version. We worked with the Frontend, Backend, and Quality Assurance teams to accomplish this task. Like we did last week, we adopted Trello to manage tasks and track the progress of each team. trello.com/b/JreouYmb/week-3 We then used one of the templates sent to the team by the program lead behance.net/gallery/146169531/URL-Shortener.. Screenshot (71).png Screenshot (75).png Screenshot (73).png The Frontend team was tasked with converting the designs to code. The Backend team had the role of implementing user authentication, shortener endpoint, login and signup end point, while the Quality Assurance team was there to ensure the APIs and designs were implemented. As it stands, we have made considerable progress; however, we are not done. A major drawback is that the Frontend Developer's PC went dead (Godu abeg o..who go epp o?). I believe one thing we have learned as a team is to always have contingency plans in case unforseen circumstances surface. This will help in ensuring deadlines are met. We'll say this week has not been as stressful as last week, but we've learned some helpful things on our journeys to being PMs. link to the url shortner moh922.github.io/BUB-IT