Google App Engine vs. Stackby

App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.

Incentivized

Based on my experience, I can provide specific scenarios where Stackby is well suited and others where it may be less appropriate: Project Management: Stackby is an excellent choice for project management scenarios. Its ability to create custom databases, track tasks, assign responsibilities, and collaborate in real-time makes it highly effective for managing and monitoring project progress. CRM and Sales: Stackby is well suited for managing customer relationships and sales processes. Its customizable database structure allows for organizing customer information, tracking leads, managing deals, and generating reports. The ability to integrate with other tools further enhances its usefulness in CRM and sales workflows. Content Planning: Stackby is a great fit for content planning scenarios. Users can create databases to manage editorial calendars, track content ideas, assign tasks to team members, and monitor content performance. Collaboration features facilitate seamless content collaboration and ensure timely publishing.

• Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
• Flexible. We use Java for some services and Node.js for others.
• Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.

Incentivized

• Ability to collaborate with team members on the same spreadsheet
• Ability to integrate multiple tools for centralized utilization (i.e. Facebook, Google Analytics, project management, etc.)
• Ability to send SMS and messages using integration with Twillio and Whatsapp
• All spreadsheets/databases securely saved in the cloud instead of on local hard drive(s)

• There is a slight learning curve to getting used to code on Google App Engine.
• Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
• Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)

Incentivized

• Implement the same views available on desktop into the mobile app
• Internal automations (like Airtable)
• Ability to implement and display info as a dashboard (like Airtable)
• Polish up the formatting of formulas, inputting them causes user frustration due to the formula input cursor jumping around
• Better intelligence and ease of inputting data in bulk i.e have the fields automatically identify what data is being input and format appropriately (like Airtable does)

App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.

Incentivized

I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster

Incentivized

Stackby is overall pretty easy to use, especially if you're used to something like Airtable or SmartSuite. Some of the pages seem like near exact clones (though they put their own creative spin on things). I'd prefer a slighty fresher interface (like SmartSuite), but I'm willing to sacrifice that for the better price and great customer service.

Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.

Incentivized

Extremely responsive, helpful, and friendly support (unlike many other SAAS teams out there).

We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.

Incentivized

I have also tried Ora.Pm. Infinity has better graphical interface, but nowhere near as many features and the UI isn't as effective (i.e, moving around with keys). Grist has a much more technical interface and it comes from being more of a database/interactive spreadsheet vs Stackby. Grist has much more functionality in terms of formulas, but is much harder to learn to use and less other functionalities. Ora.PM is more of a test at a task management app, and doesn't compare - Stackby is much better.

• Effective employee adoption through ease of use.
• Effective integration to other java based frameworks.
• Time to market is very quick. Build, test, deploy and use.
• The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.

Incentivized

• Positive impact on organising my marketing so I contact advertisers in an appropriate time frame and don't lose hours figuring out what's happening.
• Positive impact on organising challenges so that people feel more connected and supported, leading to future sales.
• Positive impact on understanding data so that I can use it more effectively.