There was once a man. We shall call him Joe. He didn’t know how to get assets for his Unity projects very easy. He scoured the internet for open licensed items, built his own 2d sprites with ms…
As a college student, I have attended various events that present the opportunity to network and make connections. Every connection we make can be invaluable to us in the future in ways we may or may not expect. Thanks to LinkedIn, it’s very easy to connect with people and establish your network. However, as I was expanding my network and having interesting conversations with people, I realized, down the line, I probably won’t remember these conversations or whether I even really met these people or just added them to my network from the “people you may know” page on my LinkedIn.
So, I decided to develop an app that allows users to keep track of their connections and make them easily available in the future. This was my first experience developing a mobile application, so ConnectionLog is currently a relatively simple application. Users can add new connections, which get inputted in a dynamic table view. For each connection the user can input information such as job title, phone number, company, etc. In the “Talking Points” section users can input information about where they met the connection, what they talked about, and personal information about the person such as their interests. Thus, users can reach out to these connections in the future without feeling like they’re talking to complete strangers. Users can search through their connections based on any keyword, rather than just names. So, say in the future you become interested in jobs in the clean technology industry. A quick search for “clean tech” can show you connections you have made who could provide you with advice for your endeavors. ConnectionLog also allows for uploading images, making calls, sending emails, setting connections as favorites, and creating custom calendar events within the app.
The following videos display some of the functionalities of the current version of the app:
I stored all the connections (including all their information) in a database using SQLite. The application’s table view is loaded by reading in the data from the database. Users can add, edit, and delete connections. After any of these actions are executed, an insert, update, or delete statement is sent to execute the change in the database. Then, the table is reloaded.
For organization, I created a different file for each view of the app. So, I had to pass the necessary information from one view to the next when the app switches views. For instance, when the user selects a connection from the table view, the program has to pass the details about that connection onto the new view that displays the details. Also, when a new connection is created, the connection’s details have to be passed back to the table view so that the database and the table can be updated with the new content. This was one of the more difficult concepts for me to implement effectively and efficiently.
Some ideas on how the new Apple MagSafe Charger can be improved.
No one can love me as I need. “No One” is published by Jazalyn 🎭🎵💔💧✍🏻🗣.
This your last day to check out the Tribeca VR films for free on Oculus headsets. This year due to COVID-19, the Tribeca VR folks teamed with Oculus to release several of the VR films they programmed…