• Albert Bennett

Tweet Posting: Introduction

Updated: Jul 12, 2021

Now as with most other code samples that I have posted about, I have added a link to the project at the start. Feel free to follow along with the samples but, if you are looking for a short-cut here it is:​ CLICK FOR GREATNESS​


Alrighty then, this is the first project that I will be starting on my blog. The use case is this;

As a user, I don't want to be constantly going into linkedin and Twitter to post about my post. Therefore the requirements are as follows:

. It should be a native application

. It should be able to connect to Twitter

. It should be able to connect to linkedin

. It should be able to post on behalf of the user

. It should allow the user to set the text for the post/ tweet

. It should be able to generate text for the post/ tweet

Restrictions:

. The content for posts and tweets should be the same

. The posts need to appear to come from the user


Sounds simple...​


Now, we could integrate with Twitter and linkedin, get the access tokens and send the message. Or, now bear with me... We use Storage Accounts, KeyVault and a whole mess of other tech to create a much better experience. On board? Excellent! Now here is a run-down of what this series of blog posts will be covering:

. Setting up our project environment​

. Using Azure​

. Integrating with Twitter​

. Integrating with Linkedin​

. Scheduling posts

. Improvements​

On top of this, I will be hitting on several different topics such as TDD (Test Driven Development) and DI (Dependency Injection).​


This should be fun :)


Part 1: Setup>>

18 views0 comments

Recent Posts

See All