Which one do you prefer? Ignore the "following" text for now - that's a WiP.

Left image:

Or right image:

Here is a more refined version of the profile view. I'm thinking of adding the image to the right section and flowing the bio full width below the initial data. Will report back with a different version.

What would a great way to write this line shorter?

"Following 486 users you aren't following" - I know it's pretty much on point, just trying to think if that can be made shorter. "Following 486 unique users", "Following 486 other users". They all seem to miss the mark though.

I'm about to start another round of Gluon coding, so feel free to ignore my rapid fire posts. I'll be working on the conversation view and some other tweaks. Maybe I'll even do something totally different. I won't have too much time today as I also need to work on some actual client work 😋

Today’s plan is to add the Conversation view into Gluon. As a stretch goal I’ll also add the currently logged in User Profile view.

I fixed the profile view bug very early AM and added the “Follow/Unfollow” button on a profile. Pretty happy with that.

That would leave the reply functionality and image viewer. I’m hoping I get to that tomorrow.

There is also some work required on my HTML parser... as it’s not working as I want it to - it sometimes just misses part sentences and images.

This means that the next TestFlight should be ready for end of this week.

Fixed a crashing bug when not logged in, kept going with loading data for the profile screen. I do need to make a few changes here, with the way I navigate to another profile (as I load a new Author Profile model, which overrides the last profile I was on - oops).

For the login part of the app I decided to also load everything else but in the background, so that Mentions, Favourites, and Discover are available straight away (within a few seconds anyway). Important, though, is that I don't hold you up initially.

I added more spacing to the feed item, so it doesn't look so condensed. Think it looks good.

Just getting back to work with the Profile screen. I'm using colours inspired from my own site, just to keep it simple. There will be more themes down the line.

Right, time for a break now until the evening. Thanks for reading and I'll see you perhaps tonight.

Starting to mock up the profile screen. I use the red so I can see the header area nicely. Ignore the posts, they are just the normal feed for now.

There are some technical limitations with grabbing the data first time around. Here is the API call, which grabs 40 posts (although I set a count of 20) - just a bug.

That would be 7 seconds of waiting for seeing any type of profile information and posts. Setting the count to 10 (which returns 20 post items for the user) has a similar response time. That's not super great. I've spoken to Manton about this already and I'm hoping there will be a few updates to this soon.

To mitigate this, on first time load, I'm actually passing the data that I do have, from the post, to the view - this way I can show the avatar, name, username and website address straight away. Then my plan is to fire off two requests, one empty with no posts (count = 0) and one with posts. The count = 0 request usually returns under 2 seconds, which means I can grab the profile data and all other related things that I'll need to show like the following count and, of course, the bio. Then we just need to wait for the posts to come back. Once we have this data, I'm going to keep it in the cache, which means it will load from cache as soon as you come back to the particular profile. This should keep loading time to an absolute minimum.

With it loading from cache I'll do a normal request to the API, with posts, in the background so I can update it if it changes and rewrite anything we have in cache.

Full belly. Digesting. Here is my Profile screen sketch. Now to implement.

Next task will be to work on the User Profile screen. I'm going to be using a different design, but I need to sketch it out first on a piece of paper. However, first I'm having a break and lunch.

And now testing Android quickly. Had a few issues as I'm also playing with swipe-able actions on each cell. Fixed that now, mentions working. The text is grey on Android if you set no colour, kinda weird - but I will tackle that.

Let there be Mentions:

Here I'm saving the User Mentions. Of note, you can see I pass in the 'Account.currentUser' to the AsyncStorage call. You can guess why I do that :)

Here is a code snippet where I go about grabbing all the Mentions. Not perfect, but nothing ever is. It works and I'm happy with it. For info, the 'Account.currentUserToken' is the currently set/selected user account model. Oh and I don't use "count" just yet - I need to refactor that params stuff.

Size matters! 5MB so far, gives me room to play. And yes, I've been publishing regularly up to the internal TestFlight, just so I can test it and keep an eye on it. Actually found a few fatal "TestFlight only" bugs.

WWDC Wishlist - iMessage "Message Extensions" so you don't have to download some horrible third party app to go about keeping in touch with everyone.