The Christ Chapel app is the main app for the multi-site megachurch near Ft. Worth. It integrates with existing user accounts on the website to provide a seamless experience for the church members. 

The app provides access to a variety of features, including live-streaming, note-taking, and event registration. 

In addition, it also includes a habit tracking feature that allows church members to track their spiritual growth. The habit tracking feature allows users to set goals for themselves and track their progress over time. Users can set reminders for themselves and receive notifications when they reach their goals. 

All of this data is stored securely on the church's servers and is accessible to the user across all of their devices.

This was possble by integrating the app with the church's existing database, Rock RMS, and user authentication system. This allowed the app to access the user's account information and provide a seamless experience for the user, as well as keep all data secure and private in their exisiting system.

The app was recognized by Rock RMS with an award as one of the best integrations using their system and featured in their annual conference as a case study for other churches to follow.

![Image](https://github.com/user-attachments/assets/612e8e8f-4867-4c80-8c14-d0ca7bc2e00b)

In addition, Subsplash, the app platform that we partnered with to build the app, recognized the app as one of the best apps built on their platform and features it at their booth in trade shows and conferences to showcase what can be done with the integration of their platform and Rock RMS.

![Image](https://github.com/user-attachments/assets/4e44d19f-b4f4-41e3-83d3-87f9d4be6b1d)




<p dir="auto">The Christ Chapel app is the main app for the multi-site megachurch near Ft. Worth. It integrates with existing user accounts on the website to provide a seamless experience for the church members.</p>
<p dir="auto">The app provides access to a variety of features, including live-streaming, note-taking, and event registration.</p>
<p dir="auto">In addition, it also includes a habit tracking feature that allows church members to track their spiritual growth. The habit tracking feature allows users to set goals for themselves and track their progress over time. Users can set reminders for themselves and receive notifications when they reach their goals.</p>
<p dir="auto">All of this data is stored securely on the church's servers and is accessible to the user across all of their devices.</p>
<p dir="auto">This was possble by integrating the app with the church's existing database, Rock RMS, and user authentication system. This allowed the app to access the user's account information and provide a seamless experience for the user, as well as keep all data secure and private in their exisiting system.</p>
<p dir="auto">The app was recognized by Rock RMS with an award as one of the best integrations using their system and featured in their annual conference as a case study for other churches to follow.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer" href="https://private-user-images.githubusercontent.com/390996/363812988-612e8e8f-4867-4c80-8c14-d0ca7bc2e00b.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzIxNTM3NjYsIm5iZiI6MTczMjE1MzQ2NiwicGF0aCI6Ii8zOTA5OTYvMzYzODEyOTg4LTYxMmU4ZThmLTQ4NjctNGM4MC04YzE0LWQwY2E3YmMyZTAwYi5qcGVnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTEyMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDExMjFUMDE0NDI2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTRiYzZlZTIxMWFkMjIzMDRkMTRlMzZkZTg0NzA2ODJmNjcyNzI0MjVkMmE2YTQzMjBlZDFlZWVjMjUzYTQyYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.ICxNEzMvkpWUtThj0rjy68uDTnr2QIzJpT7RlAI1KIA"><img src="https://private-user-images.githubusercontent.com/390996/363812988-612e8e8f-4867-4c80-8c14-d0ca7bc2e00b.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzIxNTM3NjYsIm5iZiI6MTczMjE1MzQ2NiwicGF0aCI6Ii8zOTA5OTYvMzYzODEyOTg4LTYxMmU4ZThmLTQ4NjctNGM4MC04YzE0LWQwY2E3YmMyZTAwYi5qcGVnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTEyMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDExMjFUMDE0NDI2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTRiYzZlZTIxMWFkMjIzMDRkMTRlMzZkZTg0NzA2ODJmNjcyNzI0MjVkMmE2YTQzMjBlZDFlZWVjMjUzYTQyYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.ICxNEzMvkpWUtThj0rjy68uDTnr2QIzJpT7RlAI1KIA" alt="Image" style="max-width: 100%;"></a></p>
<p dir="auto">In addition, Subsplash, the app platform that we partnered with to build the app, recognized the app as one of the best apps built on their platform and features it at their booth in trade shows and conferences to showcase what can be done with the integration of their platform and Rock RMS.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer" href="https://private-user-images.githubusercontent.com/390996/363813002-4e44d19f-b4f4-41e3-83d3-87f9d4be6b1d.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzIxNTM3NjYsIm5iZiI6MTczMjE1MzQ2NiwicGF0aCI6Ii8zOTA5OTYvMzYzODEzMDAyLTRlNDRkMTlmLWI0ZjQtNDFlMy04M2QzLTg3ZjlkNGJlNmIxZC5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTIxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTEyMVQwMTQ0MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wN2Q0Mzc4ZjVjMWIxMzUxOWNkYjEzODQ3ZjIyMDQyMzYxYzljNWExMDk2NjEyYmFhNzhiNzJkMDJjODdjYzExJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.DPECfKPnSj9l6_ZecXj5WK4777e24aJLpSXpZsQktxQ"><img src="https://private-user-images.githubusercontent.com/390996/363813002-4e44d19f-b4f4-41e3-83d3-87f9d4be6b1d.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzIxNTM3NjYsIm5iZiI6MTczMjE1MzQ2NiwicGF0aCI6Ii8zOTA5OTYvMzYzODEzMDAyLTRlNDRkMTlmLWI0ZjQtNDFlMy04M2QzLTg3ZjlkNGJlNmIxZC5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTIxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTEyMVQwMTQ0MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wN2Q0Mzc4ZjVjMWIxMzUxOWNkYjEzODQ3ZjIyMDQyMzYxYzljNWExMDk2NjEyYmFhNzhiNzJkMDJjODdjYzExJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.DPECfKPnSj9l6_ZecXj5WK4777e24aJLpSXpZsQktxQ" alt="Image" style="max-width: 100%;"></a></p>

The Christ Chapel app is the main app for the multi-site megachurch near Ft. Worth. It integrates with existing user accounts on the website to provide a seamless experience for the church members.
The app provides access to a variety of features, including live-streaming, note-taking, and event registration.
In addition, it also includes a habit tracking feature that allows church members to track their spiritual growth. The habit tracking feature allows users to set goals for themselves and track their progress over time. Users can set reminders for themselves and receive notifications when they reach their goals.
All of this data is stored securely on the church's servers and is accessible to the user across all of their devices.
This was possble by integrating the app with the church's existing database, Rock RMS, and user authentication system. This allowed the app to access the user's account information and provide a seamless experience for the user, as well as keep all data secure and private in their exisiting system.
The app was recognized by Rock RMS with an award as one of the best integrations using their system and featured in their annual conference as a case study for other churches to follow.

In addition, Subsplash, the app platform that we partnered with to build the app, recognized the app as one of the best apps built on their platform and features it at their booth in trade shows and conferences to showcase what can be done with the integration of their platform and Rock RMS.

https://github.com/pbassham/philbassham.com/issues/46#issue-2501754821

published

post

projects

Integrations

Done

CCBC

https://github.com/user-attachments/assets/d39e2d0f-80e3-4ebb-884b-3b6276fbf2b7

Mobile app built in partnership with Subsplash using their Rock Plugin for the multi-site megachurch Christ Chapel in Fort Worth.

philbassham.com

Award winning church app with custom habit tracker

Church App with Custom Habit Tracker

I made a VSCode extension for the niche community of developers working with the [Lava templating language](https://community.rockrms.com/lava) of [Rock](https://www.rockrms.com) Relationship Management System (Rock RMS).

Lava is a fork of [Liquid](https://shopify.github.io/liquid/) developed by Shopify and runs server-side, thus, it is difficult to see the compiled results of your work when you are writing it in a code editor locally. This extension is to solve that pain point and makes the development workflow much better by enabling you to run and preview the results of your code immediately, right along side your code.

You can read more about it in the [Lava Runner Repo](https://github.com/pbassham/lava-runner)or on the [VS Code Marketplace page](https://marketplace.visualstudio.com/items?itemName=PhilipBassham.lava-runner) for the extension.


<p dir="auto">I made a VSCode extension for the niche community of developers working with the <a href="https://community.rockrms.com/lava" rel="nofollow">Lava templating language</a> of <a href="https://www.rockrms.com" rel="nofollow">Rock</a> Relationship Management System (Rock RMS).</p>
<p dir="auto">Lava is a fork of <a href="https://shopify.github.io/liquid/" rel="nofollow">Liquid</a> developed by Shopify and runs server-side, thus, it is difficult to see the compiled results of your work when you are writing it in a code editor locally. This extension is to solve that pain point and makes the development workflow much better by enabling you to run and preview the results of your code immediately, right along side your code.</p>
<p dir="auto">You can read more about it in the <a href="https://github.com/pbassham/lava-runner">Lava Runner Repo</a>or on the <a href="https://marketplace.visualstudio.com/items?itemName=PhilipBassham.lava-runner" rel="nofollow">VS Code Marketplace page</a> for the extension.</p>

I made a VSCode extension for the niche community of developers working with the Lava templating language of Rock Relationship Management System (Rock RMS).
Lava is a fork of Liquid developed by Shopify and runs server-side, thus, it is difficult to see the compiled results of your work when you are writing it in a code editor locally. This extension is to solve that pain point and makes the development workflow much better by enabling you to run and preview the results of your code immediately, right along side your code.
You can read more about it in the Lava Runner Repoor on the VS Code Marketplace page for the extension.

https://github.com/pbassham/philbassham.com/issues/45#issue-2501658748

Automation

https://github.com/user-attachments/assets/5209cb20-706c-4850-98f5-ca6439f0a44d

This extension enables you to run Lava code remotely on a RockRMS server, directly from your local development environment. 

Run server-side Lava and preview results in VSCode.

Lava Runner - VSCode Extension

When Mint shut down, I had to hunt for another site to help manage and visualize my money. I settled on [Monarch](https://www.monarchmoney.com), but it didnt quite have every feature I was wanting, so this was born.


### The Unofficial Monarch Money API

This project might be of interest to those who use Monarch Money for managing their finances. It's the Unofficial Monarch Money API, a JavaScript-based tool designed to offer programmatic access to your Monarch Money data.

#### What Is It?

The Unofficial Monarch Money API is a JavaScript library that allows users to interact with Monarch Money's data through code. It's important to note that this is an unofficial API, meaning it's not endorsed by Monarch Money and might change if the underlying service changes.

#### Getting Started

If you're interested in trying it out, installation is straightforward via npm:

```bash
npm i monarch-money-api
```

You'll need to create a user token to authenticate your requests. This involves running a small script to log in and save the token to an environment file. Once set up, you can access various methods to retrieve account information, manage transactions, and more.

Here's a simple usage example:

```javascript
import { getAccounts, getBudgets } from "monarch-money-api";

const accounts = await getAccounts();
console.log("Accounts:", accounts);

const budgets = await getBudgets();
console.log("Budgets:", budgets);
```

#### Potential Use Cases

This API could be useful for developers who want to automate their financial tracking or integrate Monarch Money data into other applications. 

For instance, I used it to create a chart widget of my flexible budgets using the Charty app for iOS. By deploying the API on Vercel, I have a hosted version always available. I set up a cron job to periodically refresh my financial data and used iOS shortcuts and the Charty app to build an always-up-to-date chart showing exactly how much is left in our flexible spending categories, sometimes referred to as the 'one number' budget. It's a simple way to monitor your expenses.

#### Technical Insights

All of the queries used in the API were derived by introspecting the GraphQL queries on the Monarch Money web application. This approach provided the necessary insights to access and manipulate the data programmatically.

Feel free to check out the project on [GitHub](https://github.com/pbassham/monarch-money-api) for more details and instructions on how to get started.


<p dir="auto">When Mint shut down, I had to hunt for another site to help manage and visualize my money. I settled on <a href="https://www.monarchmoney.com" rel="nofollow">Monarch</a>, but it didnt quite have every feature I was wanting, so this was born.</p>
<h3 dir="auto">The Unofficial Monarch Money API</h3>
<p dir="auto">This project might be of interest to those who use Monarch Money for managing their finances. It's the Unofficial Monarch Money API, a JavaScript-based tool designed to offer programmatic access to your Monarch Money data.</p>
<h4 dir="auto">What Is It?</h4>
<p dir="auto">The Unofficial Monarch Money API is a JavaScript library that allows users to interact with Monarch Money's data through code. It's important to note that this is an unofficial API, meaning it's not endorsed by Monarch Money and might change if the underlying service changes.</p>
<h4 dir="auto">Getting Started</h4>
<p dir="auto">If you're interested in trying it out, installation is straightforward via npm:</p>
<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="npm i monarch-money-api"><pre class="notranslate">npm i monarch-money-api</pre></div>
<p dir="auto">You'll need to create a user token to authenticate your requests. This involves running a small script to log in and save the token to an environment file. Once set up, you can access various methods to retrieve account information, manage transactions, and more.</p>
<p dir="auto">Here's a simple usage example:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="import { getAccounts, getBudgets } from &quot;monarch-money-api&quot;;

const accounts = await getAccounts();
console.log(&quot;Accounts:&quot;, accounts);

const budgets = await getBudgets();
console.log(&quot;Budgets:&quot;, budgets);"><pre class="notranslate"><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-s1">getAccounts</span><span class="pl-kos">,</span> <span class="pl-s1">getBudgets</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">"monarch-money-api"</span><span class="pl-kos">;</span>

<span class="pl-k">const</span> <span class="pl-s1">accounts</span> <span class="pl-c1">=</span> <span class="pl-k">await</span> <span class="pl-en">getAccounts</span><span class="pl-kos">(</span><span class="pl-kos">)</span><span class="pl-kos">;</span>
<span class="pl-smi">console</span><span class="pl-kos">.</span><span class="pl-en">log</span><span class="pl-kos">(</span><span class="pl-s">"Accounts:"</span><span class="pl-kos">,</span> <span class="pl-s1">accounts</span><span class="pl-kos">)</span><span class="pl-kos">;</span>

<span class="pl-k">const</span> <span class="pl-s1">budgets</span> <span class="pl-c1">=</span> <span class="pl-k">await</span> <span class="pl-en">getBudgets</span><span class="pl-kos">(</span><span class="pl-kos">)</span><span class="pl-kos">;</span>
<span class="pl-smi">console</span><span class="pl-kos">.</span><span class="pl-en">log</span><span class="pl-kos">(</span><span class="pl-s">"Budgets:"</span><span class="pl-kos">,</span> <span class="pl-s1">budgets</span><span class="pl-kos">)</span><span class="pl-kos">;</span></pre></div>
<h4 dir="auto">Potential Use Cases</h4>
<p dir="auto">This API could be useful for developers who want to automate their financial tracking or integrate Monarch Money data into other applications.</p>
<p dir="auto">For instance, I used it to create a chart widget of my flexible budgets using the Charty app for iOS. By deploying the API on Vercel, I have a hosted version always available. I set up a cron job to periodically refresh my financial data and used iOS shortcuts and the Charty app to build an always-up-to-date chart showing exactly how much is left in our flexible spending categories, sometimes referred to as the 'one number' budget. It's a simple way to monitor your expenses.</p>
<h4 dir="auto">Technical Insights</h4>
<p dir="auto">All of the queries used in the API were derived by introspecting the GraphQL queries on the Monarch Money web application. This approach provided the necessary insights to access and manipulate the data programmatically.</p>
<p dir="auto">Feel free to check out the project on <a href="https://github.com/pbassham/monarch-money-api">GitHub</a> for more details and instructions on how to get started.</p>

When Mint shut down, I had to hunt for another site to help manage and visualize my money. I settled on Monarch, but it didnt quite have every feature I was wanting, so this was born.
The Unofficial Monarch Money API
This project might be of interest to those who use Monarch Money for managing their finances. It's the Unofficial Monarch Money API, a JavaScript-based tool designed to offer programmatic access to your Monarch Money data.
What Is It?
The Unofficial Monarch Money API is a JavaScript library that allows users to interact with Monarch Money's data through code. It's important to note that this is an unofficial API, meaning it's not endorsed by Monarch Money and might change if the underlying service changes.
Getting Started
If you're interested in trying it out, installation is straightforward via npm:
npm i monarch-money-api
You'll need to create a user token to authenticate your requests. This involves running a small script to log in and save the token to an environment file. Once set up, you can access various methods to retrieve account information, manage transactions, and more.
Here's a simple usage example:
import { getAccounts, getBudgets } from "monarch-money-api";

const accounts = await getAccounts();
console.log("Accounts:", accounts);

const budgets = await getBudgets();
console.log("Budgets:", budgets);
Potential Use Cases
This API could be useful for developers who want to automate their financial tracking or integrate Monarch Money data into other applications.
For instance, I used it to create a chart widget of my flexible budgets using the Charty app for iOS. By deploying the API on Vercel, I have a hosted version always available. I set up a cron job to periodically refresh my financial data and used iOS shortcuts and the Charty app to build an always-up-to-date chart showing exactly how much is left in our flexible spending categories, sometimes referred to as the 'one number' budget. It's a simple way to monitor your expenses.
Technical Insights
All of the queries used in the API were derived by introspecting the GraphQL queries on the Monarch Money web application. This approach provided the necessary insights to access and manipulate the data programmatically.
Feel free to check out the project on GitHub for more details and instructions on how to get started.

https://github.com/pbassham/philbassham.com/issues/44#issue-2501658344

Data

Visualization

Personal Project

https://github.com/pbassham/monarch-money-api/raw/main/monarch-image-blue.png

A convenient npm package that offers programmatic access to Monarch Money's financial data. Perfect for developers looking to automate budgeting processes or integrate financial insights into other applications, this tool allows you to manage accounts, budgets, and transactions with ease.

Programmatically work with your financial data on MonarchMoney.com

Unofficial Monarch API

100% Apple Native ChatGPT client for OpenAI built using SwiftUI.


---
**Update 2024:**  No Longer Updated due to App Store Rules. 

Apple has App Store restrictions on apps that use an API key, because it could be used to circumvent the Apple payment system, and thus Apple is blocking further updates unless I will move it to a subscription pricing model, which I do not want to do.

---

Use **your OWN account and API key** and stop paying for crazy markups of other apps.

### Features:
- Use your own OpenAi Account, not ours.
- Unlimited conversations stored locally on your device only.
- Personas: choose from pre-made chat templates
- 100% Native Apple-only
- Universal: works on iPhone and iPad (Mac coming soon)
- Per-chat settings
    - Choose model, system message, custom prompt, creativity (temperature) settings 
- Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)
- Choose default settings for new conversations
- Adjust display settings
- Light/dark mode
- Token estimation and more message actions coming soon

Much more to come.

[Get it here](https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384) 

[![Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917](https://user-images.githubusercontent.com/390996/226219355-7c135ea4-c2fb-458f-85c1-3f351ddad84a.svg)](https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384)


<p dir="auto">100% Apple Native ChatGPT client for OpenAI built using SwiftUI.</p>
<hr>
<p dir="auto"><strong>Update 2024:</strong>  No Longer Updated due to App Store Rules.</p>
<p dir="auto">Apple has App Store restrictions on apps that use an API key, because it could be used to circumvent the Apple payment system, and thus Apple is blocking further updates unless I will move it to a subscription pricing model, which I do not want to do.</p>
<hr>
<p dir="auto">Use <strong>your OWN account and API key</strong> and stop paying for crazy markups of other apps.</p>
<h3 dir="auto">Features:</h3>
<ul dir="auto">
<li>Use your own OpenAi Account, not ours.</li>
<li>Unlimited conversations stored locally on your device only.</li>
<li>Personas: choose from pre-made chat templates</li>
<li>100% Native Apple-only</li>
<li>Universal: works on iPhone and iPad (Mac coming soon)</li>
<li>Per-chat settings
<ul dir="auto">
<li>Choose model, system message, custom prompt, creativity (temperature) settings</li>
</ul>
</li>
<li>Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)</li>
<li>Choose default settings for new conversations</li>
<li>Adjust display settings</li>
<li>Light/dark mode</li>
<li>Token estimation and more message actions coming soon</li>
</ul>
<p dir="auto">Much more to come.</p>
<p dir="auto"><a href="https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384" rel="nofollow">Get it here</a></p>
<p dir="auto"><a href="https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384" rel="nofollow"><img src="https://user-images.githubusercontent.com/390996/226219355-7c135ea4-c2fb-458f-85c1-3f351ddad84a.svg" alt="Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917" style="max-width: 100%;"></a></p>

100% Apple Native ChatGPT client for OpenAI built using SwiftUI.

Update 2024:  No Longer Updated due to App Store Rules.
Apple has App Store restrictions on apps that use an API key, because it could be used to circumvent the Apple payment system, and thus Apple is blocking further updates unless I will move it to a subscription pricing model, which I do not want to do.

Use your OWN account and API key and stop paying for crazy markups of other apps.
Features:

Use your own OpenAi Account, not ours.
Unlimited conversations stored locally on your device only.
Personas: choose from pre-made chat templates
100% Native Apple-only
Universal: works on iPhone and iPad (Mac coming soon)
Per-chat settings

Choose model, system message, custom prompt, creativity (temperature) settings


Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)
Choose default settings for new conversations
Adjust display settings
Light/dark mode
Token estimation and more message actions coming soon

Much more to come.
Get it here

https://github.com/pbassham/philbassham.com/issues/41#issue-1628108128

SwiftUI

https://user-images.githubusercontent.com/390996/225727818-66ae0617-6bc4-4315-af69-46cdab9d4fe7.png

I threw this project together in a few weeks and was surprised to see it hit **#1 in App Store** within the Productivity category, and #8 overall! At  least until OpenAi released their official client.

The 1st Native ChatGPT Client for Apple Devices

ChatAi Unlimited - 100% SwiftUI

## Why Github _Issues_?
I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.

Ok, I know that seems like the wrong tool for the job, but hear me out. 

I had several goals for my website:
1. Free to host - this site doesn't make money, so I don't want it to cost.
2. Fast
3. Maintenance free-ish 

I went through several iterations:
1. Wordpress - not fast or free
2. Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi. 
3. Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site. 
4. Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile. 
5. Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain. 
5. Next.js + GitHub issues = 
    - [x] Benefits of a hosted CMS 
    - [x] Unlimited users
    - [x] Edit history of posts
    - [x] Reactions 
    - [x] Comments
    - [x] Project Management tools
    - [x] Create lots of Content views 
    - [x] Visualize Content strategy
    - [x] Free Image Hosting
    - [x] Free


### Project management features
Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of [Github Projects](https://github.com/features/issues), but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to _plan_ out writing and _visualize_ the progress.



#### Sprint Planning
I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.

![Image](https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png)


And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.

I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.

For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.


![Image](https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png)

### Content and actual issues (bugs, enhancements, etc) in one system.

Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.

One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.


### Publishing
This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.



### Metadata

Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.

I can even view it in table view to make sure every post has all of the fields it is supposed to.
![Image](https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png)

### Image Hosting
Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.

Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.


## How it works

You can read more on the [README of the GitHub repo](https://github.com/pbassham/philbassham.com), but in summary:

1. Next.js that generates a static, server-side rendered page.
3. [Github Action that makes slugs for issues](https://github.com/pbassham/slugify-issue) - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)
  4. [Cloudflare Key-Value Store](https://www.cloudflare.com/products/workers-kv/) - Allows fetching the GitHub issue by a slug without a rebuild Update 2024: (Vercel now has a Key-Value tool, that didn't exist when I made this. That would put it all under one roof, which would be easier. One day maybe I will update this.) 
5. Hosted on Vercel 
6. Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.  
Fork it on [GitHub](https://github.com/pbassham/philbassham.com) and try it for yourself!




<h2 dir="auto">Why Github <em>Issues</em>?</h2>
<p dir="auto">I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.</p>
<p dir="auto">Ok, I know that seems like the wrong tool for the job, but hear me out.</p>
<p dir="auto">I had several goals for my website:</p>
<ol dir="auto">
<li>Free to host - this site doesn't make money, so I don't want it to cost.</li>
<li>Fast</li>
<li>Maintenance free-ish</li>
</ol>
<p dir="auto">I went through several iterations:</p>
<ol dir="auto">
<li>Wordpress - not fast or free</li>
<li>Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi.</li>
<li>Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site.</li>
<li>Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile.</li>
<li>Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain.</li>
<li>Next.js + GitHub issues =
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Benefits of a hosted CMS</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Unlimited users</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Edit history of posts</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Reactions</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Comments</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Project Management tools</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Create lots of Content views</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Visualize Content strategy</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Free Image Hosting</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Free</li>
</ul>
</li>
</ol>
<h3 dir="auto">Project management features</h3>
<p dir="auto">Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of <a href="https://github.com/features/issues">Github Projects</a>, but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to <em>plan</em> out writing and <em>visualize</em> the progress.</p>
<h4 dir="auto">Sprint Planning</h4>
<p dir="auto">I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png"><img src="https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png" alt="Image" style="max-width: 100%;"></a></p>
<p dir="auto">And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.</p>
<p dir="auto">I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.</p>
<p dir="auto">For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png"><img src="https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png" alt="Image" style="max-width: 100%;"></a></p>
<h3 dir="auto">Content and actual issues (bugs, enhancements, etc) in one system.</h3>
<p dir="auto">Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.</p>
<p dir="auto">One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.</p>
<h3 dir="auto">Publishing</h3>
<p dir="auto">This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.</p>
<h3 dir="auto">Metadata</h3>
<p dir="auto">Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.</p>
<p dir="auto">I can even view it in table view to make sure every post has all of the fields it is supposed to.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png"><img src="https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png" alt="Image" style="max-width: 100%;"></a></p>
<h3 dir="auto">Image Hosting</h3>
<p dir="auto">Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.</p>
<p dir="auto">Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.</p>
<h2 dir="auto">How it works</h2>
<p dir="auto">You can read more on the <a href="https://github.com/pbassham/philbassham.com">README of the GitHub repo</a>, but in summary:</p>
<ol dir="auto">
<li>Next.js that generates a static, server-side rendered page.</li>
<li><a href="https://github.com/pbassham/slugify-issue">Github Action that makes slugs for issues</a> - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)</li>
<li><a href="https://www.cloudflare.com/products/workers-kv/" rel="nofollow">Cloudflare Key-Value Store</a> - Allows fetching the GitHub issue by a slug without a rebuild Update 2024: (Vercel now has a Key-Value tool, that didn't exist when I made this. That would put it all under one roof, which would be easier. One day maybe I will update this.)</li>
<li>Hosted on Vercel</li>
<li>Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.<br>
Fork it on <a href="https://github.com/pbassham/philbassham.com">GitHub</a> and try it for yourself!</li>
</ol>

Why Github Issues?
I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.
Ok, I know that seems like the wrong tool for the job, but hear me out.
I had several goals for my website:

Free to host - this site doesn't make money, so I don't want it to cost.
Fast
Maintenance free-ish

I went through several iterations:

Wordpress - not fast or free
Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi.
Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site.
Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile.
Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain.
Next.js + GitHub issues =

 Benefits of a hosted CMS
 Unlimited users
 Edit history of posts
 Reactions
 Comments
 Project Management tools
 Create lots of Content views
 Visualize Content strategy
 Free Image Hosting
 Free



Project management features
Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of Github Projects, but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to plan out writing and visualize the progress.
Sprint Planning
I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.

And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.
I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.
For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.

Content and actual issues (bugs, enhancements, etc) in one system.
Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.
One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.
Publishing
This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.
Metadata
Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.
I can even view it in table view to make sure every post has all of the fields it is supposed to.

Image Hosting
Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.
Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.
How it works
You can read more on the README of the GitHub repo, but in summary:

Next.js that generates a static, server-side rendered page.
Github Action that makes slugs for issues - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)
Cloudflare Key-Value Store - Allows fetching the GitHub issue by a slug without a rebuild Update 2024: (Vercel now has a Key-Value tool, that didn't exist when I made this. That would put it all under one roof, which would be easier. One day maybe I will update this.)
Hosted on Vercel
Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.
Fork it on GitHub and try it for yourself!

https://github.com/pbassham/philbassham.com/issues/24#issue-1531159848

https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png

This site is built using GitHub issues to host all content for free, including images!

Free CMS with image hosting, comments, reactions, and more.

Projects

Some things I worked on building.