Kryptronic Software Support Forum

If you're passing all the auth logic through to K9 to do the authentication, then you've covered the bases you need to in order to ensure proper user auth.  You're basically replacing the token logic in K9 with your JWT, which is fine.  I'd like to see this app once you'd done with it.

Rob:  You impress me with most of what you do, but this is AWESOME!  That £100 from five years ago is probably more like £200 today, so you did very well on the cost-front.  I'm wondering what the £58 in expenses was for.  Soda and candy bars? 

I really like the look and feel of the app - it mirrors the native OS well so it should be very user friendly.  What you've done to your K9 site is great - most people leave it styled stock - but you've changed most of the displays (and for the better).  The address book looks implemented very well - which I know wasn't the easiest thing to pull off.  If you've got it working at this level this well I have a feeling everything else will wrap up easily for you.

One thought I had while viewing the videos is that guest functionality is missing (or not evident in the videos).  At first I thought that made sense as you're tying one to the other, but you could technically support guests on both frontends and there wouldn't need to be any crossover unless a guest logs in with a new account (but K9 handles that).  Of course the whole guest thing might go against your intended app flow/marketing scheme.  FYI: You figured out user accounts (acct info in core_users, tied to core_session), guests are similar but everything exists in core_session (session data contains most of the same fields from core_users relating to user info).

The fact that you've needed no support and had no questions while developing this blows my mind.  Although you have been using our stuff for a very long time.

Right on!