If you’ve forgotten your password, you don’t have to fret anymore. There is now a “Forgot Password” button on the login page. Click this button, enter the e-mail address for your account, and you will be e-mailed a link that will allow you to reset your password.
Here’s hoping this will get users that may have been locked out a means to get back in.
The direct link is right here.
I’m excited here! I did a big code push last night that has the fundamental code in place for groups and sharing of prayers within those groups. Now I’m looking for some extra help.
There’s an old developer saying when approaching new projects is that there are three ways to build it:
- Make it Good
- Make it Fast
- Make it Cheap
Pick two of those (or ask your client to do so) and move forward…
It has taken bit longer than I had planned, but Prayer Journal has made it over to its new home with its new framework!
I’ve mentioned over on my personal blog that one of the reasons why I blog is to “share the love” of experience and code solutions that I’ve come up with. That said, I’m here to share one of the resources I’ve brought off the ground for the platform shift referenced last week.
I’ve really been inspired lately by the active blogging done by the Desk app (of which I am using too 8^D). Throughout the development process (and beyond) there was an open and consistent stream of communication during the process. I’m going to work on following that model and provide more updates, even if you can’t see them. So here is the latest milestone.
While there haven’t been any updates as of late (I’ll make sure this changes after the holidays) there has been some work going on that isn’t readily visible yet. I’m in the process of changing the platform model that Prayer Journal will be built on.
I’m extremely happy with AngularJS and Firebase has been a really interesting dive into the world of fully client based applications that have a realtime update model. However, I’ve started to hit a few little snags with Firebase (namely some added complexity when it comes to the NoSQL model and sharing items with various groups) that while aren’t insurmountable, I believe will take more time in the long run to work with than I find worth it. In addition, I want to stick to a code base that I’m more familiar with to be able to provide a faster turnaround in the long run when new features are added or bugs are discovered. I’ll also admit that in the long run I’m not sure I could handle the financial requirements of the Firebase platform.
With that in mind, I’m in the process of moving to the new ZANS stack. I think I just made that up, plus I like Dr. Seuss a lot 8^D. I’m using the new Zurb for Applications (ZA) stack to handle all of my front end needs. This will still give me the ability to have a single page application and the Zurb controls and layout model that I’ve become quite familiar and happy with. My middle tier is going to be the .Net WebAPI layer, which has some amazing “out of box” integration for authentication and REST compliant queries, all wrapped up in a standard JSON format. I’ll keep the data stored using SQL Server, since there is easy object referencing and Entity Framework object mapping. Ultimately all of this will allow me to host Prayer Journal on the Microsoft Azure platform, which gives me great flexibility when I need to build out services due to demand. I’m quite familiar with it too, which is a big help.
That’s the latest. Hopefully I’ll have everything moved over, with groups fully functional, by the end of next month, but keep working with the latest version and don’t hesitate to drop me a line with any comments, bugs, or ideas.