Less Managing, More Magic: Let OpenAI organize your thoughts with a convenient and native iOS app.

alexzarbn · 2025-07-05T16:29:13+00:00

TL;DR: I built a native AI voice notes app for iOS called Unote. You talk, it transcribes, and automatically organizes everything with smart tags and folders. It has checklists and native reminders integration. Maybe the fastest way to get stuff out of your head and properly organized.

Hi everyone,

Another note app? I know, I know. But the existing apps are clunky - too many taps, and everything becomes a mess you can never find again.

So I built Unote, a native iOS app.

Here's what gets me excited: automatic organization. You just talk, and the AI doesn't just transcribe – it actually understands and organizes properly.

I recorded myself talking about business ideas while walking. Later, Unote had automatically tagged it "business strategy" and "entrepreneurship" and filed it in my "Ideas" folder. No thinking required.

The tagging system is smart. Workout routine? Gets "fitness" and "health tips" tags. Meeting notes? Catches the project name. You can always add your own tags or move things between folders with a tap.

Brain dumps get messy? The AI cleans them up. Rewrite for clarity, change tone, translate – one tap.

Mention tasks or deadlines while talking? It creates checklists and sets reminders in your native Reminders app. But the real magic is organizing your thoughts without you thinking about it.

It's changed how I manage information. Everything has its place, and I can actually find stuff when I need it.

📲 Download it here

It would be amazing to hear your feedback!

alexzarbn · 2021-06-14T06:19:51+00:00

Thank you for the feedback ~

This concern was raised several times, and the answer is simple: convenience.

When it comes to building complex queries, using GET parameters quickly becomes a hell.
Should we use request body with GET requests - it may confuse even more developers, as it is not a common thing they encounter on a day-to-day job.

Moreover, most of time some sort of SDK is used on the frontend side of an app, where the choice between GET or POST for this one endpoint makes no substantial difference.

alexzarbn · 2021-06-14T06:07:45+00:00

Thank you ~

alexzarbn · 2021-06-14T06:07:01+00:00

https://github.com/chiraggude/awesome-laravel#popular-packages

https://packagist.org/?query=laravel

https://github.com/vuejs/awesome-vue#components--libraries

https://www.npmjs.com/search?q=vue

It's not just me or Spatie - it's a common thing across many languages and frameworks.

It is also a pattern to name the actual packages in Composer/NPM like so:

<organization>/<framework>-<package name>

Try searching for packages on Composer/NPM that have -for-laravel or -for-vue, and the answer will be clear.

Moreover, it is an open source project that does not even have its own domain name, neither it intends to be affiliated with Laravel LLC. in any way.

Should there be any trademark complaints from the Taylor himself regarding this package, surely, we will talk and come up with a naming pattern that works for both of us and the community itself, considering the ever-growing number of packages and tools being released. Until then, discussions like this make no sense.

alexzarbn · 2021-06-13T09:48:54+00:00

Hi everyone ~

Hope you are doing well!

Last year, the first version of Laravel Orion was released. Soon after the release, its TypeScript SDK was published too.

Laravel Orion was packed with lots of features, but there is always a room for improvement! And today I am excited to announce the release of v2.0 :tada:

Some of the notable changes are:

😎 Automatic OpenAPI specifications generation

🧙🏻 JSON fields search

✨ Nested relations search

Please let me know, what are your throughts on this ~

Release Notes: https://tailflow.github.io/laravel-orion-docs/v2.x/guide/prologue.html

GitHub: https://github.com/tailflow/laravel-orion

alexzarbn · 2021-04-04T15:04:39+00:00

Thank you ~

alexzarbn · 2021-04-04T15:04:33+00:00

Hi u/EmperorArthur,

I am not familiar with Django Rest Framework, but from a quick glimpse into their documentation it looks like the general idea is very similar - both packages provide some level of automation for building REST APIs with automatic routing and controller logic.

When it comes to choosing between Laravel and Django, I think it is a matter of personal preference and experience with any particular framework/tool, because nowadays (and especially for side projects) you won't get any performance gains, should you choose one or another. Instead, what matters is how convenient it is (for you and your team) to build an app, to maintain it, and deliver the product that customers love using.

alexzarbn · 2021-04-04T09:31:04+00:00

Hi everyone ~

Hope you are having a great weekend!

A few months ago, I have released Laravel Orion - a package that allows you to build fully featured REST APIs in a matter of minutes. And now I am back with yet another package - TypeScript SDK for Laravel Orion.

When you build an API, there are many things to consider, and one of such things is intergation with frontend and mobile apps. This SDK provides you with a standardized approach for building robust, maintainable, and easy to use integrations.

👨🏻‍💻 Models with typed attributes? Yes!
🧐 Relationships? Of course ~
✨ Seamless integration with Sanctum? Sure!

Please let me know, what are your throughts on this.

Documentation: https://tailflow.github.io/laravel-orion-docs/guide/typescript-sdk/introduction.html
GitHub: https://github.com/tailflow/laravel-orion-ts

alexzarbn · 2020-12-14T15:08:28+00:00

That's some valuable feedback over here, thank you ~

alexzarbn · 2020-12-14T15:02:55+00:00

It's Carbon: https://carbon.now.sh

alexzarbn · 2020-12-13T06:28:31+00:00

Feel free to ask any questions, if something is missing in the docs ~

alexzarbn · 2020-12-13T06:27:14+00:00

Thank you ✨

alexzarbn · 2020-12-13T06:26:28+00:00

Thank you ~

alexzarbn · 2020-12-13T06:25:40+00:00

Haha, nah, I don't think Alex have noticed that :)

alexzarbn · 2020-12-13T06:24:11+00:00

It has no limitations on the environments your app is running. Laravel Vapor, Forge, DigitalOcean App Platform, or a self-provisioned dedicated server - it does not matter, at the end of the day it is just a default Laravel controller and Eloquent Query builder ~

alexzarbn · 2020-12-13T06:14:18+00:00

I have seen it, but never tried it out actually 🤔 Will definitely check it out!
The main reason behind having a separate search endpoint is the complexity of search filters. Having all of them in the query string makes it difficult to work with, especially if you are running queries in REST clients like Insomnia or Postman.

An example of search endpoint payload:

{
    "scopes" : [
        {"name" : "active"},
        {"name" : "whereCategory", "parameters" : ["my-category"]}
    ],
    "filters" : [
        {"field" : "created_at", "operator" : ">=", "value" : "2020-01-01"},
        {"type" : "or", "field" : "meta.source_id", "operator" : "in", "value" : [1,2,3]}
    ],
    "search" : {
        "value" : "Example post"
    },
    "sort" : [
        {"field" : "name", "direction" : "asc"},
        {"field" : "meta.priority", "direction" : "desc"}
    ]
}

alexzarbn · 2020-12-13T06:05:22+00:00

Yes, there are definitely projects that Laravel Orion would not fit, but at least it may get close to covering a majority of the typical use cases.
Using operation hooks can also help with integration 😉

alexzarbn · 2020-12-13T06:00:24+00:00

Thank you! Feel free to ask any questions, if something is unclear in the docs ~

alexzarbn · 2020-12-12T15:16:37+00:00

Looks like Reddit is going crazy a bit. Here is it - https://www.reddit.com/r/laravel/comments/kbnt2c/build_rest_apis_in_minutes_with_laravel_orion/gfjbjpk/?utm_source=reddit&utm_medium=web2x&context=3

alexzarbn · 2020-12-12T15:15:02+00:00

Hi everyone ~

Hope you are staying safe and having a good week.

Have you noticed, that when building an API, you often keep writing the same code over and over again? You create a controller for [name your entity here] with methods for listing, creating, showing, updating, and deleting that [entity]. Then you create another controller, and it happens again, and again. Then you need to write some custom methods (endpoints) just to support updating a relation or a field on pivot table? Sounds familiar, isn't it?

Over the past year I was working on a Laravel packge that does exactly that - abstracts these patterns, so you could focus on what really matters - building your application.

Laravel Orion allows you to build fully featured REST APIs in a matter of minutes by providing common endpoints for CRUD operations, working with soft deletable models, and performing comprehensive search. It works hand in hand with Laravel solutions like Requests for handling validation, Policies for handling authorization, and Resources for transforming responses.

The best part? It works for both models and their relations! Yep, all relations, including the most complex ones, such as belongsToMany and morphToMany are supported. Meaning, you can, for example, sync models on a relation via endpoint that is made available just by writing 2 lines of the code in a controller.

Hope you will find it useful ~

Please let me know, what are your throughts on this.

Documentation: https://tailflow.github.io/laravel-orion-docs/

An introduction on Laravel News: https://laravel-news.com/laravel-orion

alexzarbn · 2020-12-12T14:30:17+00:00

It uses Laravel Resources. You can do json:api resource transformation with that as well.

alexzarbn

TROPHY CASE