applin-ios
mui-toolpad
applin-ios | mui-toolpad | |
---|---|---|
5 | 10 | |
1 | 796 | |
- | 8.7% | |
9.0 | 9.9 | |
3 months ago | 3 days ago | |
Swift | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
applin-ios
-
FastUI: Build Better UIs Faster
> Beyond Python and React ... Implementing frontends for other platforms like mobile ...
Shameless plug: I built a mobile version of this: https://www.applin.dev
-
Strada Released
I built a thing that makes it much simpler to make apps: https://www.applin.dev
You make a web server that returns JSON defining your UI. Then you make a native iOS app by copy/pasting the provided Main.swift file and adding the URL of your server. The app uses an iOS client library, fetches the JSON page definition, and builds/updates the page with native widgets. I'm planning to eventually build Android, web, and desktop clients.
- Applin™ Server-Driven UI Framework for Mobile Apps
- Applin Server-Driven UI for Mobile Apps
-
Show HN: Applin – define mobile UI in server code
Hi HN, I'm a backend engineer who made an app and didn’t like the tools. Then I made the thing I needed: a mobile app toolkit for backend engineers. I'm calling it Applin™. :)
https://www.applin.dev/
How it works: You make an HTTP server that returns JSON objects that define page content. Then you make a mobile app that calls the server and renders the pages using native widgets. Applin is the server and client libraries that make this easy.
Server libraries: Currently there's Rails https://rubygems.org/gems/applin-rails and https://github.com/leonhard-llc/applin-rails-demo . Which languages shall I add next?
Client libraries: Currently there's iOS https://github.com/leonhard-llc/applin-ios . Which platform shall I add next?
They say, if you're not embarrassed by the quality, then you're launching too late. Applin is usable and not yet pretty and not yet comprehensive. I need customer feedback on priority and requirements.
To try it out right away, use https://apps.apple.com/us/app/applin-tester/id6464230000 and tap the rails-demo link.
The hardest part of this project was making the client update the page without losing keyboard focus and scrolling to the top. To do that, the code must pick the correct existing widgets for each new version of the widget tree. The current (working) version performs five passes over the widget tree: first picking focused widgets and their ancestors, then focus-able widgets, then other stateful widgets, then widgets with matching attributes (label, URL, etc.), and finally former siblings of the correct type. Then it creates any new widgets. Now that it has widgets for the new tree, the code updates the widget tree without removing any sub-widget that will be added again. This prevents losing keyboard focus and prevents resetting scroll positions. Here's the code:
https://github.com/leonhard-llc/applin-ios/blob/main/Sources/ApplinIos/page/widget_cache.swift
Please try out Applin, use it at your company (buy a license), and let me know what features to build first! Post a comment here, add a GitHub issue, or email me at [email protected] .
To get updates, join https://groups.google.com/g/applin-announce .
Thanks for reading! :) --Michael
mui-toolpad
-
FastUI: Build Better UIs Faster
This seems to mainly be useful for spinning up quick and dirty internal tools.
But for that use-case, isn't it easier to use something visual and established like Retool (https://retool.com/) or that generates nice react code, like MUI Toolpad (https://mui.com/toolpad/)?
-
Plasmic.app – the visual builder for your tech stack
How does it stack up against MUI's Toolpad? (https://mui.com/toolpad/)
All things considered, they seem pretty similar - visual UI to generate React code that works alongside existing codebase, open-source & self-hostable, etc.
- just discovered MUI and...
- I hate CSS: how can I build UIs?
-
Show HN: MUI Toolpad – Open-source, local-first, admin app builder
- All configuration is stored in local files which you can version-control, edit, and deploy in any way you want.
You can check out our live demo [1]. If you find it useful, you can support us by giving a star on GitHub [2]. We released our public beta [3] this week. We are happy to answer any questions/feedback in the comments.
[1]: https://stackblitz.com/fork/github/mui/mui-toolpad/tree/mast...
[2]: https://github.com/mui/mui-toolpad
[3]: https://mui.com/blog/2023-toolpad-beta-announcement/
- MUI Toolpad: Turn Your APIs, Scripts, SQL into UIs
-
Ask HN: How can a BE/infra developer handle the FE side of personal projects?
- Vercel for hosting, because they take a Git repo and host it for you in a couple clicks and manage everything. Free or cheap ($20/mo) at MVP stage.
- Next.js (Vercel's open-source React framework) will handle frontend tooling, routing, type checking, and linting for you with a single command (`npx create-next-app`). Starting the server is one more command (`next dev`) and your page is up and running.
- For the UI layer, I'd recommend either starting with one of their prebuilt templates (https://vercel.com/templates/next.js) and modifying it as needed
OR using a modern component system like https://mui.com/ or https://ant.design/ or https://chakra-ui.com/ instead of trying to learn and write your own component and JS+CSS code. Using one of these systems will allow you to compose complex apps out of well-made, well-documented, easy-to-use primitives, making it much easier to focus on business needs rather than basic frontend components and infra.
The basic MUI system, for example, is totally free. You can find third-party apps built on top of it (https://mui.com/store/#populars) and pay a one-time license fee to essentially "fork" them, getting a prebuilt working app that you just attach your backend API calls to.
There are also low-code extensions of these frameworks (meaning you start with a GUI, plan out your app that way, but still have access to the source for future advanced changes). Examples are https://mui.com/toolpad/ and https://retool.com/use-case/dashboards-and-reporting
----------------------
Is this a lot? Yes and no. React has a learning curve of its own, but it can take the place of having to learn raw HTML and CSS. (Yes, you eventually should know those things for debugging and polishing, but they are largely a level of abstraction below what you really need for a basic MVP).
Once you learn React, its primary value isn't that it's a great language (opinions differ) but that it has a humongous ecosystem of third-party vendors, free open-source libraries (basically any component you might think to build is probably already available on npm), and a wide availability of devs from hobbyists to full-timers.
Others in this topic will suggest going away from Javascript as much as possible (and using things like HTMX or backend-to-HTML solutions like the old days). That's fine, but you lose out on the rich ecosystem of React and Javascript, so you end up having to build more yourself -- which is what you're trying to avoid in your case.
My own 2¢: As someone who grew up with HTML and made websites since the birth of Javascript and CSS, the web has always been messy. It's always been a semi-open ecosystem controlled by a few major companies (whether that's Netscape or Microsoft or Sun or Adobe, or these days Google and Apple), so it very much suffers from design-by-bullying. Whoever is the power player of the decade gets to add their favorite technologies that everyone else is forced to adopt. Thus the web became a hodgepodge of document markup systems poorly fitted for modern apps, with various hacks on top of hacks built to satisfy some big company or another's in-house needs. Sadly, that means going "vanilla HTML+JS" doesn't leave you with much, just the shattered legacy of poor historical decisions.
React at least helps by encouraging componentization and abstraction of UI elements to functions, using cleaner data models (actual variables and objects) vs direct DOM manipulation (storing page content as state).
We've gone through many generational shifts in approach, from the raw HTML days of Geocities to the you-build-it, we-host-it approach of Godaddy and its ilk, to the "all in one" CMSes like Wordpress or Drupal. These days, (if you want there to be), there can be a pretty clear separation between backend and frontend systems, and with that specialization came a bunch of startups (mentioned above) whose approach is "let us help you build it as best as we can, so you can focus on business logic instead of basic UI and infra". After 20 years of doing this, the current state of the web developer experience is actually my favorite so far. HTML and CSS suck for building apps (as opposed to documents), and although Javascript is a lot better since ECMAscript v6 (ES6), it is still inextricably tied to the DOM (and thus HTML elements) unless you use an abstraction like React.
It's the difference between writing something like:
```
-
What is the most used react UI framework ? need to visual drag and drop app
We at MUI have been working on an open-source drag-and-drop React app builder. Link to the landing page: https://mui.com/toolpad/ This week we have published an interactive demo as well. You can check out the repo here.
What are some alternatives?
hyperview - Server-driven mobile apps with React Native
appsmith - Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
turbo - The speed of a single-page web application without having to write any JavaScript
primereact - The Most Complete React UI Component Library
masilotti.com - Source for masilotti.com, built with Bridgetown and Tailwind CSS.
mantine - A fully featured React components library
applin-rails-demo - Example of how to use applin-rails.
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
plasmic - Visual builder for React. Build apps, websites, and content. Integrate with your codebase.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
material-ui-docs - ⚠️ Please don't submit PRs here as they will be closed. To edit the docs or source code, please use the main repository:
antd - An enterprise-class UI design language and React UI library