Automation has taken over in our world today with huge improvements being made in a wide range of sectors. When you think of automation, you may have a manufacturing plant in mind, but within the mobility space, we have found many companies using mobile applications and software to automate simple tasks and repetitive processes. Apps like Workflow by Apple, IFTTT by IFTTT, and Home by Apple are all great examples of apps that have been developed to allow customers to automate some of their own tasks within iOS. Workflow allows customers to, "build [your own] workflows with a simple drag-and-drop interface. Mix & match hundreds of actions to create quick shortcuts, manage your media, share content, and much more." With hundreds of apps available to automate, your choices and combinations of automated tasks are endless. Or, you can take a more fun approach with IFTTT. If a local sports team scores a goal, your automated task will trigger the Home app and can turn on a certain automated home accessory like your Hue lights. Now, the photo above has nothing to do with automation, but by taking advantage of this new technology, we should all be somewhere taking more vacations to places like this! We have already covered one of our own apps in a previous blog post, which uses ServiceNow's API to update hundreds of records in bulk. It is not an automated app, but it essentially does the all of the heavy lifting in regards to data updates, spreadsheet formatting and uploads for the customer.
Today, we will be talking about leveraging automation within our Twitter accounts. We wanted to build a Twitter following even before we found our footing as an app development company. In order to do that, we would follow many accounts in our industry thinking that those accounts would follow us back in return. Apparently for some, it is sort of just an unsaid considerate thing to do. We now have up to 3,000 Twitter followers by doing simply that. Save your comments for another time, but yes it is possible to gain a following by sending out follow requests. Although, it is important to have an account that feels and looks professional, and actually interacts with the community by sending out Tweets and messages to others. You can find our FileMakerWebandiOS Twitter account here! Of course, all of our tweets, direct messages and interactions and sent by real people, we just found the need to automate certain portions of the account. You can imagine that sending out manual requests gets old very quickly. So, we decided to build a iOS and macOS solution to automate our Twitter account with FileMaker 17! We have out together an exclusive package the includes a step by step guide to help you automate your own Twitter account. This includes how to apply for your own Twitter developer account all the way up to sending a follow, unfollow and mute request with cURL in FileMaker 17! Also included is a FREE 30 Day trial of UnfollowMagic FREE!
We honestly had no idea how to do even get started in the beginning, so of course we started asking questions to the FileMaker Community. Everyone is very helpful and always gives tips or suggestions that will help you along the way. After searching "FileMaker and Twitter", we ended up finding out that we needed to learn how to use cURL with FileMaker to connect to Twitter's API. You can learn more about Twitter developer resources here. There are many resources that Twitter developers can tap into within the documentation, but we were interested in getting started with the "Accounts and users" API section. We needed to learn how to make a successful Twitter API call using cURL in FileMaker.
Interested in learning more about how to automate your own Twitter account? Download our FREE PDF and UnfollowMagic Sample File below!
There are many uses cases for automating processes with FileMaker as well as using cURL to integrate FileMaker with other popular services. Our next project is to automate our Instagram account! We know that this project can be taken a step further to be fully automated with FileMaker Server, but we know that not everyone has access to FMS. If you are interested in learning more about the fully automated solution, contact us here.
For the best results, it is recommend to start following other Twitter accounts within your industry. This is what provided the best results with our own account! We reached 3,000 in one year without automation and have seen a 125% increase in results after we created this magical solution! Mostly due to the fact that no one has time to follow Twitter accounts every day! :) Now, that problem is solved!
For those interested in a sample file that outlines what we covered in this blog post, we would be more than happy to share it with you! It is a starter file that will help you to better understand how to use cURL and FileMaker with Twitter API's.
For those who are interested in a fully automated solution without having to do any following or unfollowing with your Twitter account using FileMaker Server, we are working on a solution for you!
Questions, comments, ideas? Contact us here.
I quickly learned how to use the FileMaker platform through tutorials and breaking down their pre-existing solution file set. Having a developer background from JMU, the FileMaker environment came naturally to me. I was really excited to develop my first app with the best end user possible. Myself! :) Although the end goal was to deploy this app across other IT departments, I was literally developing an app to make my own job easier first. I am still not quite sure what is better than that at this point in my career. The app improved a very time consuming and complicated process that essentially was updating a lot of data in a database. The time it took to complete the process went from hours of work to minutes by using an app with three simple steps. 1. Scan barcode. 2. Update Data. 3. Submit Changes. I have an efficient yet simple way of attacking work, so developing for myself really helped to make the app more intuitive. Some may not agree with this approach when developing for a larger group of people, but placing yourself in your customers shoes is what really helps to understand their workflows and perspectives. I also take the lazy approach in the way that it helps me find the easiest way to do something. I also kept in mind to use the least amount of button presses as possible for simplicity. As you all know, it is all about working smarter, not harder.
But what exactly is an intuitive app you ask? It is an app that customers just know how to use right away. They have a natural sense of how to do things in your app and should be able to do whatever they want without any directions or training. The easiest way of showing you an example of an intuitive app is to introduce you to Robinhood. From their website, "With Robinhood, you can learn to invest in the stock market as you build out your portfolio." The interface is simple and clean, yet quickly conveys important information all on a small iPhone screen. Now, of course the knowledge of investing and stock trading is important to use this app, but you get the idea. It is just easy to use. You already know how to navigate your way around the app because it has been designed that way! Developing an intuitive app is of course very complicated to design and build. Making simple things can be complicated, but the hard work is worth it when then customer experience becomes magical. We always want to make sure that the customer has the best experience possible and that can be done with intuitive apps.
In order to make our mobility experience the best, a lot of work went in on the technical FileMaker side of things. We used FileMaker's ODBC feature to connect to a SQL table that was provided to us by a dev team. Then they took care of the rest to make sure the data was updating correctly. It was impressive enough that we were given permission to work with them in the first place! Eventually after about a year of testing, we needed to start using a ServiceNow API. This was another fun development cycle that helped me learn more about the JSON side of FileMaker. It really helps to dive head first into the FileMaker environment to learn how to use the program. The community was really helpful during this process and members would answer any of the questions I had. The FileMaker community discussion page can be found here. This helped me to develop the features of the apps, but the design portion was drawn out by hand. It was important for me to design the app in a way that everyone else knew how to use the app as well, because as mentioned, the end goal was to deploy this app to other IT departments. In order to do that, I stuck with natural design concepts that already existed in software and in signage around us today.
As mentioned in the previous blog post, "Year 2: 2016 - New 9 to 5 Life and an Unexpected Development Paradigm Shift!" I was able to design the app so that when a barcode was scanned, the data was instantly determined by a red or green color to quickly show the user what was going on. I used Apple's iOS Human Interface Guidelines Documentation for all of the colors that I used in the app. Also, if the user was just starting out with the application, there would be only one button to press that would guide them through the process of scanning a barcode. When a barcode was scanned, they were then guided to proceed to make changes to the data. The app always was designed to flow the user through the process of making data changes and prevented them from making any mistakes. After the success of this app development project, I knew that I could use FileMaker to help other individuals and business to improve their workflows. Luckily, I had an individual that knew I was capable of taking on the challenge and set me up with my first client.
Client #1: Invoice/Proposal macOS solution and iOS Payroll app for iPhone
This client needed a macOS Proposal/Invoice Manager solution and a Payroll iOS app for the iPhone. Both solutions were very easy to use and helped the business owner to focus a lot less time on paperwork. All communications were done over phone and email. It was challenging because I was very meticulious about the details of the project and wanted to understand everything exactly as they wanted. From this I learned to trust my own design and programming knowledge to deliver a product that the user could then revise during a testing period. This helps to guarantee that the user is happy with the application before the final payment is processed. Aside from the programming, project and client management experience, I ended up with a few hundred dollars from both projects. This really got me excited for the road ahead to see what I was able accomplish next. I was thinking to myself, if I am able to sell these solutions for a few hundreds of dollars to one person, how many other people can I sell these exactly same solutions to? This is what has always excited me about software development and I was very excited because these were the first software products that I had built for clients. I knew that my hard work was getting my closer to my goal!
Client #2: Visitor Log and Membership ID generator iOS App for the iPad
For my next project, I was introduced to a non-profit organization called PhillyCam in Philadelphia, by a friend who made sure that their technology was running smoothly. They decided to change the way visitors logged in from paper and pen to a guestbook app to log visitors into a database. This information would then be used to generate membership cards with photos and barcodes for members to later scan in for fast entry. A pain point for them was having to page through the Visitor Log book for reporting. We are changing the way they think about using visitor logs for their business by deploying a FileMaker iOS app for them to use on an iPad! A learning experience from this project was to always double check your work and also set up your environment so that it is as hands off as possible. In this case we should have gone plain and simple by using FileMaker Go instead of using the FileMaker iOS SDK and using a launcher file to open a file on the FileMaker Server. This way, we can always remotely manage the project and recreate it in our own environment for testing.
Client #3: GuestbookGuru iOS App for the iPad
The same friend introduced me to another individual who needed a Guestbook app for her business. At this time, this individual did not have a way to manage, organize and customize multiple guestbooks for events on the iPad. We were able to design an iOS app that did just that and the client was very happy! This iOS app was developed in the FileMaker environment and was deployed to the App Store. A FREE version of this app can be found in the App Store and on our website www.guestbookguru.com! Our next step is to upgrade and convert this application over to a native Swift environment with a team of iOS developers. We are now looking for hungry and passionate iOS developers to work with us on future projects. It will be an extremely resourceful, valuable and education experience for everyone involved. This exciting project can be found here! From this project we learned to use a testing week where the user would use the application and we would iron out any issues. This turned out to be great and we pushed out an update when we found a bug. This application also happened to be in the App Store and the user had a last minute request that could not be implemented in time for her event. Although we had clear communication that all changes would be final after the testing week, these are valuable learning experiences that remind us to have clear communication with the user to make sure they understand the environment. From these experiences we are growing stronger and hope that you can learn from them too!
Client #4: TBD - It might be you!
How to develop an intuitive app - A quick introduction
-Take the lazy approach to help find the easiest way to do something
-Place yourself in the user/customer's shoes
-Very simple step by step functions and workflows that leave the customer impressed
-With design, stick with what users already naturally tend to know
-Use the least amount of button presses possible
-Create a simple, efficient, powerful and magical experience for the customer
-iOS Human Design Guidelines Documentation
-Be clear and direct with any text, buttons, and directions
-Intuitive apps should not require training
Automating Twitter with FileMaker 17!
Questions, comments, ideas? Please reach out to firstname.lastname@example.org
I had finally received the call that I was looking forward to for a long time. I was going to be an iOS Mobile Device Specialist! You are probably wondering what that is, especially since this is an iOS development blog and word "developer" does not exist in the job title!
Well that was perfectly fine with me, because if you read the first introductory blog post called "Soaking up iOS Dev at JMU" you would be able to guess my position on finding a developer job pretty easily by now. Deep down I just knew that I was not quite prepared to be a full time developer or even land a full time developer job. I do not usually promote those types of cynical thoughts, although for me it was the best decision to make at the time. The iOS Mobile Device Specialist position had the potential to provide many opportunities that I was really excited about. I would be able to work with two people that are my mentors and now great friends, who prior to this job had a combined 15+ years of experience at Apple. These two continue to play a impactful role in my professional and self development journey to this day.
One of the guys had created a master plan for our impact in the mobility space and we were more than excited and ready to take on the challenge. Throughout the journey, there were so many educational, career, and self improvement opportunities available to be involved with. I could just tell that I was right where I needed to be. Also, the fact that I would get paid to learn how to support and manage thousands of iPads was pretty awesome! Of course, there were potential iOS development opportunities as well, one of those being that I was introduced to a life changing software development tool called FileMaker, but we will come back to that a little later! There was just one other thing, there would be a decent amount of labor intensive work that went with the job role. But, like I had experienced at my previous internship, I knew that certain things had to be done in order for me to get where I wanted to be. For me, I would be fine doing other jobs outside the role of an iOS developer so that I could potentially find my way into that role or just anything that involved iOS apps!
Now it would be pretty boring to hear about everything I experienced during my first few months getting comfortable as an iOS Mobile Device Specialist, but there was definitely a lot of work to do. At this point, it was important that I understood the job responsibilities and experienced the "grunt" work that went along with them. This would allow for process improvement further down the line by gaining an understanding of how everything was being done at that time. To keep it simple, just one of the responsibilities consisted of managing inventory and a break/fix queue for thousands of customers and iPads. This type of project would be the first of many detail oriented projects that I would be involved with at the company. It helped me to learn how to use different asset management systems and allowed me to understand the importance of data organization and integrity. The iPads would later play a huge role with the call center team and troubleshooting with our customer. If something was incorrect in our iPad deployment process, there would be many issues further down the line that would effect other departments and systems. It was pretty exciting to know that I did play a small role in the company and that these types of experiences could potentially evolve into iOS development opportunities!
The senior mobile device specialist was the reason why I had chosen to accept the job and he was a huge driving factor in bringing me onboard. We had an instant mutual understanding for what needed to be done and that was "all she wrote". The guy is just always exciting to be around and is not only a brilliant mind in the iOS mobility space but in many other innovative technology spaces as well. He believed that I had the ability to help the team by developing apps to improve old processes. No one at the company before had accomplished developing an iOS app and I was both excited and nervous for the challenge. His belief in me to succeed alone was very impactful. He is a mobility visionary, someone who is able to think of innovative solutions to solve problems, but also someone who can create a plan for how our mobility team can change the way our leadership thinks about mobility and also how our customers gain more value by using their iPads. I encourage all of you to find someone who is just as excited and passionate to learn as he is. Those who help you with professional and self development are invaluable and can also turn out to be life-long friends. He is just a top notch guy, mentor and life-long friend.
To bring his forward thinking plan into action, we would need to create a MCOE or Mobility Center of Excellence. Explaining an MCOE is a topic worthy for an entirely separate blog post, but essentially we needed to find a way to create the best mobility experience as possible for our customers using iPads so that they could feel more helpful in their job roles. This would provide more valuable experiences for their customers which would eventually generate more revenue for the company. For us, this meant that a lot of things needed to change for us to even have time to focus on creating an MCOE. This would not only present more difficult challenges but as well as some opportunities for us in the future.
In order to create the best experience possible, we really had to understand more than the just the mobility aspect of the job. Those other areas of understanding are networking, asset management, systems, operations, process improvement, how to get things accomplished through relationships and more. Aside from these areas of understanding, configuring and deploying thousands of iOS devices to our customers, we also had to manage a lot of other projects that dealt with asset management. Along with those responsibilities, there were a few pre-existing challenges surrounding these assets. As you can imagine with only a few individuals available to manage the data in regards to our assets, we had to be efficient. This is where the vision of our senior mobile device manager came in. In order to be better utilized in our job roles so that we could develop an MCOE, we needed to find a better way to manage our assets. As you can imagine, with only a few people supporting thousands of iPads as well as having other a lot of other responsibilities, solving the asset management problem was also a big part in achieving our goal of creating an MCOE.
You now have an understanding for how important it was for us to find or create a helpful tool that would help us to efficiently manage our asset management processes. Luckily my two co-workers had previously been briefed about an Apple owned company called FileMaker Inc, who provides an affordable, flexible and reliable tool called FileMaker. It is a relational database application which integrates a database engine with a GUI, that allows users to modify the database and drag new elements into layouts to create custom apps. FileMaker helps developers to quickly create powerful custom apps capable of scaling in the enterprise. For me, the huge benefit with FileMaker is that is a script based, low code no code development environment which did not require learning, memorizing or staying up to date with with rapidly changing languages. FileMaker's platform was just the paradigm shift in programming that I needed. iOS apps could be created in a significantly less amount of time with less frustration and just as many features. The only downside about FileMaker is that there are less native iOS features to make available to the user. After reading about improvements that FileMaker had made over the years, I knew that the company would eventually evolve FileMaker to provide a more native iOS experience for the user. Now up to FileMaker 17, they have introduced layout transitions, iBeacon support, and local push notifications. I would love to see press and hold or swipe to delete actions! Although less native and elegant than Apple's Swift and Xcode, FileMaker is a very helpful tool for developers to quickly create powerful iOS mobile apps for the iPhone and iPad. With the challenges to solve and the newly introduced FileMaker development tool at hand, I was so excited to get started.
It did not take very long to get up to speed with the FileMaker environment as I was using the suggested "Get Started" documentation, asked tons of questions to the FileMaker Community and spent some time reviewing the starter solutions that FileMaker provided. This is where this blog clearly gets more valuable as we can provide recommended recourses for others who find themselves looking to use FileMaker for developing apps. In our situation, we started out with FileMaker 15 Pro Advanced and FileMaker Server 15. This would allow us to host our apps over a network so that we could use the app anywhere in the building. FileMaker also allows you to host your app locally so you can host an to check your development changes on an iPhone or iPad. There is so much more information to cover, but we will just get started by introducing FileMaker! The best way is to just dig in and get involved! Check out some of the resources below!
Getting started with FileMaker resources:
After the short amount spent time getting used to FileMaker, I was ready to take on our asset management challenge. We needed to use FileMaker to update data in a database. Our iPads had tags on them with a barcode and numbers. We wanted to be able to update data related to each iPads by scanning each barcode into a FileMaker database. From there, the user would be able to make their changes and submit them to the database to update. For a self taught developer like myself, this was going to be difficult. I knew that I had been hired for this challenge and I believed in myself enough to get the job done. Although I was a bit nervous, I was even more excited to have my hands on my own iOS app development project!
The project was to develop an intuitive iOS app used with FileMaker Go on an iPod Touch. The reason for selecting the iPod was because it was the only device able to integrate with a barcode scanner that would scan multiple asset tag barcodes at once. For those of you who are learning and developing with FileMaker, the asset tag numbers scanned from each barcode were then sent to a Number Type field called "Asset Tag" on the body part of the List View FileMaker layout. That was a mouthful, but if you break it down into pieces, it is much easier to understand. We will be developing tutorials in the future that go over the development of this project when our readers express interest. The barcode scanner is called a Linea Pro scanner that integrates to the iPod through the iOS Keyboard settings and the Linea Pro ScanBoard App. The scanner also fits into the lightening port of the iPod which then charges the iPod if it has low battery. Once the data is sent to the "Asset Tag" field, we utilize a very helpful feature that FileMaker calls "Conditional Formatting". This allows developers to change layout objects based on calculations and values. Conditional formatting changes the way an object is displayed, such as changing background colors, text formatting, and other design changes. So, when the asset tag number is placed in the "Asset Tag" field, our scanner is triggered to automatically return to the next field, so we run an OnObjectExit script trigger that checks to see if the asset tag number has an entry in the system or not. If there is an entry, we set a variable to a particular value such as "Yes". If there is no entry we set the variable to the value "No". Then, our conditional formatting calculation on the "Asset Tag" field is set up to check if the variable contains the value, "Yes" or "No". If yes, the conditional formatting feature is set to change the background color of the "Asset Tag" field to green. If "No" the field is set to change to red. This lets the user immediately know if the asset needs to be added to the system or not. Finally, there is an information button that would query the database to get the latest asset information such as location and model type. Although it may seem like we have covered a lot just in this one paragraph, these development tasks are rather simple in FileMaker. As we mentioned, it will be much easier to visually see in our future Youtube tutorials when our readers express interest.
We have just covered a small portion of our iOS development journey and reviewed some intimate development details that others may not choose to include. This is the one of the most important projects that continues to provide value to many people that will help us to develop an MCOE. We will stay on the topic of our iOS asset management app in the next blog as we review further into what it took to have our first small impact on the organization in regards to developing an intuitive app, finding the most efficient way to update asset data in bulk, and using my FileMaker knowledge outside of my 9-5 to start making money.
Coming up next: Year 3: 2016 - Developing an intuitive, efficient and powerful iOS app experience
I had just graduated college from JMU with a B.S ISAT (Integrated Science and Technology) degree, a MacBook and a very strong passion to develop iOS applications; although it did not come naturally to me and was still figuring it out on my own. (There were a few reasons for this other than my programming abilities, but one was that iOS development was not yet being taught in class.) Perhaps an unusual start to introduce myself to a very new audience, but an important fact to be acknowledged at this point in my journey of developing iOS apps. I was just not that great! I provide some of these details because I hope something will provide value to others in many different forms. Sitting on the couch for the first time back at home, I took a moment to think about what I had just experienced in the last year and half of college.
Although these next few posts will be a quick reflection on the past to bring readers up to speed, the entire series of the "Life is full of (iOS) development" will be written during our development adventure as I experience it, rather than a reflection of the past. It will contain everything from gaining website traffic and social media management to learning how to generate passive income in many different forms and much more. I believe that the title itself is pretty self explanatory, but life is truly full of development. I finally realized that life should be all about continuous learning and improving yourself and hopefully others around you. So, yes there will be some underlying messages and I will throw in some sappy life lessons here and there but only because they are important. I hope readers will gain a ton of value in many different forms in every post and will learn throughout the journey of building iOS apps and an iOS software development company from scratch.
So, at this point I still feel like complete trash at programming but it didn’t really matter to me. I knew that the experience I gained through my internship would help me in some form or another. I knew in my gut that Apple's iOS was a very special thing (really no surprise there) and just really wanted to be involved. I also knew that the the potential revenue opportunities were way too great to be interesting in anything else except iOS development, despite my lack of skills, knowledge and experience in the space. Although basically inadequate at everything it took to be an iOS developer, believe it or not, I would actually have some very positive and life changing experiences later on in my iOS app development journey.
Although my program in college did not offer courses to improve my native iOS development skills, I would still find a way to learn more. During my junior year of college I was able to passionately persuade my way into a small startup company called GroMobi, located in downtown Harrisonburg, Virginia. GroMobi consisted of two co-founders and a handful of iOS developers who created educational and well as behavioral recognition iPad apps for private and local educational institutions. Since I did not have very much programming experience, I was willing to do anything to land any role at the company. My first few months consisted of gathering client prospect information for interns who would later cold call the phone numbers that I had collected that day. I was happy to be involved with a new company that could lead to iOS development experience and would even help me land a job in the future.
After about three months went by at GroMobi gathering data, I was getting pretty anxious to get my hands on iOS development. Both co-founders knew I had a lot of passion and interest in developing apps, but they were not too eager to just give me the position. It was getting to be about the end of the second semester when everyone went home for summer. I was renting an apartment in Harrisonburg and decided to take summer classes to "get ahead". Besides wasting rent payments, I knew there was a potential opportunity to keep working at GroMobi. So, I went and asked one of the co-founders if I could stay over the summer to learn everything I could about iOS development and he said that I could absolutely tag along.
GroMobi was using a program called Appcelerator Studio/Titanium Studio, an open source software development tool for cross platform mobile development. The applications were time consuming to build on the development side as well as the interface side. Images are placed by pixels rather than Xcode's advanced Interface Builder. Nonetheless, I was willing to do anything to be involved with the app development process, even if it included pushing images around pixel by pixel. Yes, my summer consisted of moving some images around painstakingly, but I also got involved in the development as well. The gold nugget for me was being exposed to all of the code that everyone else was working on. I had a chance to see how everything worked and was able to ask a ton of questions. Although I did not have a big role in the day to day development process, I got a lot of practice and was able to learn the process of developing an iOS app all the way to finally being able to publish it on the App Store.
After the summer was over, I wanted to keep working at the internship to stay more involved with the development process. I mean, I had just spent a lot of time working for free and I also did not want to lose my spot and relationships with the co-founders. There were other interns at the company who were much more experienced, faster and actually amazing at developing apps, so I would eventually take on tasks to assist them and kept asking as many questions to learn as fast as I could. The more experienced developers would later work on converting all of the applications over to Apple's Swift programming language and usually never had too many issues during development at all. The only challenging aspect for those individuals was juggling school work and the internship. I was very happy to move on from Appcelerator/Titanium Studio to Xcode and Swift but was not too quick to pick up the programming skills. but had developed a huge appreciation and an even stronger passion for iOS apps and app development. The amount of planning, research, design and execution that went into each application was impressive, as well as the rewards in return for having an impact on helping to improve students lives in education was awesome. This experience really made me want to build my own application that would bring a positive change to the community and world. We had the perfect opportunity coming up!
Although I was not even close to being an all-star at iOS development, I was able to apply some of the knowledge that I learned from my GroMobi internship to a senior capstone project that was required to graduate. This project was designed to gain real experience working with other like minded team members to develop a working software product. The only knowledge that I had at the time consisted of Appcelerator/Titanium studio and a little bit of Swift, so development ended up being a little slow. Our project, called AlumniConnect, was positioned to allow students to be more connected with Alumni and would eventually present both groups with opportunities that were never heard of before at the University. We landed ourselves on the front page of the ISAT website and that was about it. For as much excitement that was surrounding our project from fellow professors and our mentor, it was rather disappointing that nothing ever came of it. The disappointing result was a combination of what I believe was novice mentorship, our planning, team member dedication, understanding and communication among team members, and execution. So yes, as a group we had no idea what we were doing. Although things did not pan out, I definitely learned a lesson. Also, I finally realized that my limited understanding of programming actually got us an A! The desktop version ended up being complete garbage and all that we had to professionally present was the iOS app! The UI was a bit rough around the edges and not all of the functionality was present, but the effort it took to think through such a challenge was amazing! Sometimes, when you are hard on yourself and constantly push towards your goals, it is important to step back for a moment to realize the things you have accomplished. But in the end, all that really remained was the knowledge gained from the experience and the poorly made AlumniConnect logo from our ISAT Senior Capstone project.
One chapter ended and another began after I finished college at JMU and moved on to the 9-5 working world. At this point in my life, I had no idea that it would be just the start of a very rewarding iOS app and personal development journey.
Coming up next: 9 to 5 Life and an Unexpected Paradigm Shift!
"In the end, all that really remained was the knowledge gained from the experience and the poorly made AlumniConnect logo from our ISAT Senior Capstone project."