Allow a user to submit an article to Weekly Xamarin

Probably via a share target.

As suggested in this review: https://play.google.com/console/u/0/developers/6368784618035709134/app/4976087531830244264/user-feedback/review-details?reviewId=gp%3AAOqpTOFPRhjQcxaXXoQFfhGHeFYG5tv95uxD1Sl8sfd_tG7233guOcf220jlr-7Lp1ltftXckapCuGMUyBUI1w&corpus=PUBLIC_REVIEWS

If you go to the bookmaks screen before you've liked anything it looks broken.

Maybe we should say something like "There's nothing here yet, swipe on an article to heart it and it will show up in your starred list".

Read the data from json files located on Github under WeeklyXamarin.Content

SwipeView swipes little bit when scrolling vertically.

Solution:
Investigate and apply threshold to SwipeView.

Do we need authentication to see if a user is streaming?

Create the model objects for the project.

Note: Given we are probably going to move away from Curated, we probably don't want to adhere too closely to what they are using, so we should just create a nice clean set of Model objects that suit our app.

Issues

• Issue Number
• Issue Date
• Issue Description
• List Curators

Articles

• Article ID
• Title
• Author (Reference to an author object?)
• URL
• Description
• Issue Published
• Category

Author

• Author ID
• Author Name
• Profile Photo URL
• Github URL
• WebPage URL
• Twitch URL
• YouTube URL
• Twitter URL

Event

• Event ID
• Title
• URL
• Date
• Event Type (Conference, User Group, Live Stream, Webinar)

For example Issue 265 doesn't have an updated time that matches the index.

When an edition page is initially loaded and not in the cache, we should add some kind of indicator of loading/progress until it is pulled down.

Thanks to @MdeBruin93 for this suggestion on the live stream

Are there going to be any restrictions on using an MVVM framework vs INPC with a BaseViewModel? same question about DI container? I see this as a teaching opportunity to show how to do VM functional testing with Xamarin.Forms.Mocks.

What about cool infrastructure-y things like Fody, to cut down the property noise? (Assuming Simon will let us use it in a demo project. I am Patron in OC, if that makes a difference.)

Looks very different to search text

• Different icon
• Different position
• Different font weight.

Requires a refresh of the first screen

For more information check out this blog post from @tpcware - https://ncarandini.github.io/2020/06/17/UserSecrets-With-XF.html

We've already got Shell in the App, why not leverage the URL engine?

Some links from JonP333 and @adenearnshaw

https://gridbyexample.com/examples/example1/
https://stackblitz.com/edit/css-grid-basic
https://www.w3schools.com/howto/howto_css_cards.asp

I hope you apply infinite scroll to the search page instead of loading the whole result for better performance.

On a suggestion from @smabuk might be a good idea to include this on all outbound links.

Ref:
https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/noopener

VortexCDN: I noticed that when I get a notification from the weekly xamarin app the notification icon in the top bar of my android is slightly smaller then other icons, I just wanted to make you guys aware.

Harrison464: that blank icon on notifications is something with not having the right image. after some version you have to use a different image

Provide a cache of the json source data so.

1. It can work disconnected
2. faster startup and access to data

There isn't sufficient data that storing all of it locally would be a problem

• Github
• Twitter
• Youtube
• Twitch

Given that the data does not update often I think an index file with a LastUpdated dateTime would probably be a workable solution.

Based on feedback from this review in the Play Store

https://play.google.com/console/u/0/developers/6368784618035709134/app/4976087531830244264/user-feedback/review-details?reviewId=gp%3AAOqpTOFPRhjQcxaXXoQFfhGHeFYG5tv95uxD1Sl8sfd_tG7233guOcf220jlr-7Lp1ltftXckapCuGMUyBUI1w&corpus=PUBLIC_REVIEWS

Every hipster needs theme support - and we are no different.

My suggestion is just keep it to Light/Dark using the fancy new features of AppThemeColor objects

I like to keep models, viewmodels and services in a separate project.

This is fairly trivial to do now but will be a pain if we leave it to later in the project

I'm not sure how many of these ideas will end up being implemented but this will make implementing any of these much easier when we get to it:

• Unit Testing
• Dependency Injection
• Adding more platforms
• reusing code on a server

Currently, the list of previous editions is oldest first, we want to have this in descending order so the newest edition is shown first.

Now that GH is free for Teams any thoughts about setting up a team with a board for tracking tasks?

Check this reference: https://mobilebuildtools.com/manifests/versioning/

Seems to be an issue when adding a bookmarked item.

Doesn't display the correct items

Whats the process for doing CI / CD for project with multiple authors possibly working on the YAML? (I am thinking of any Secure variables we might want to keep (just as a teaching point)). I have never had shared owners of CI in a non corp / Active Directory situation.

I am assuming we just do it on our Azure account with our fork and see what the PR reveals in hard coded / relative paths. I can see Badges in the Readme.md possibly being "path-y / specific URI" based.

Can we use Xamarin.BuildTools? Will we will track with the latest XF release?

In dark mode you can't see it

Seem to be having issues (although we can't reproduce it) where we can't reforce a refresh of new content.

Here is some background reading
https://blog.jeremylikness.com/blog/implement-progressive-web-app-hugo/

Steps:

1. Go to search
2. Select a category
3. Go to another page
4. Come back to search

Category should still be the same value as selected, but is reset.

Requirements:

• Latest version of Xamarin.Forms, Essentials
• Using Shell
  • Basic Tab setup for the various sections (Issues, Saved, Events, Settings)
  • Tab Images
  • Search bar